Happy Design aka. Rapid Prototyping for the Web Why building backwards is faster, cheaper and delivers a better web product.

Slides:



Advertisements
Similar presentations
User Experience Krista Van Laan. Agenda What is User Experience? How does a User Experience team support the rest of the organization? What processes.
Advertisements

Ch.1 Introduction to Software Engineering The Evolution 1.1 The Evolving Role of Software 1/15 In the early days: User Computer Software = Place a sequence.
Kyle Hartmann. RAD was created in response to long lead times and low flexibility Focuses on communication Quicker and better requirements interpretation.
1 The Process of Usability Engineering laura leventhal and julie barnes.
Systems Analysis & IT Project Management Pepper. System Life Cycle BirthDeathDevelopmentProduction.
E. Wainright Martin Carol V. Brown Daniel W. DeHayes Jeffrey A. Hoffer William C. Perkins MANAGINGINFORMATIONTECHNOLOGY FIFTH EDITION CHAPTER 10 M ETHODOLOGIES.
No Silver Bullet - Essence and Accident in Software Engineering By: R. Adam Mead.
CS 5150 Software Engineering
Message Design and Content Creation 23 January 2007 Kathy E. Gill.
Computer Engineering 203 R Smith Requirements Management 6/ Requirements IEEE Standard Glossary A condition or capability needed by a user to solve.
Chapter 8 Prototyping and Rapid Application Development
CS147 - Terry Winograd - 1 Lecture 9 – Prototyping Terry Winograd CS147 - Introduction to Human-Computer Interaction Design Computer Science Department.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 17 Slide 1 Rapid software development.
Collaborative Business Intelligence Kevin Burrus Brainspire Solutions
Rapid Prototyping Model
Essence and Accident in Software Engineering By: Mike Hastings.
Mantova 18/10/2002 "A Roadmap to New Product Development" Supporting Innovation Through The NPD Process and the Creation of Spin-off Companies.
Crystal Yellow Agile Software Methodology For ParaView Development Sandia is a multiprogram laboratory operated by Sandia Corporation, a Lockheed Martin.
SOFTWARE ENGINEERING MCS-2 LECTURE # 5. RAD (RAPID APPLICATION DEVELOPMENT) MODEL  In RAD model the components or functions are developed in parallel.
6-January-2003cse Introduction © 2003 University of Washington1 Introduction CSE 403, Winter 2003 Software Engineering
11.1 © 2007 by Prentice Hall 11 Chapter Building Information Systems.
Computer –the machine the program runs on –often split between clients & servers Human-Computer Interaction (HCI) Human –the end-user of a program –the.
Systems Development AIMS 2710 R. Nakatsu. Overview Why do IT projects succeed and fail? Two philosophies of systems development –Systems Development Life.
Designing Goods and Services Chapter 3, Part 1. Operations and Operations Strategy Designing an Operations System Managing an Operations System Done We.
Lecture 31 Introduction to System Development Life Cycle - Part 2.
Prototyping CSCI 4800 Spring 2007 Kraemer. Learning Goals Understand the uses of different types of prototypes for different kinds of designs and be able.
SOFTWARE ENGINEERING MCS-2 LECTURE # 3. SOFTWARE PROCESS  A software development process, also known as a software development life- cycle (SDLC), is.
1 CSE 403 Software Requirements Reading: Pragmatic Programmer Ch. 7: Before the Project These lecture slides are copyright (C) Marty Stepp, 2007, with.
13-January-2003cse LifeCycle © 2003 University of Washington1 Lifecycle CSE 403, Winter 2003 Software Engineering
Introduction to Systems Analysis and Design
Human Factors in Information Seeking and Use Wooseob Jeong.
Chapter 7 Interactive Design and Prototyping Human Performance Engineering Robert W. Bailey, Ph.D. Third Edition.
© Bennett, McRobb and Farmer Avoiding the Problems Based on Chapter 3 of Bennett, McRobb and Farmer: Object Oriented Systems Analysis and Design.
Agile Software Development By Kshitij Limaye CSC 532.
1 DELIVER MEDIA THAT RESONATES HOW TO BUILD BUYER PERSONAS AXIOM ADVISING.
Software Engineering Jon Walker. What is Software Engineering? Why do we call it Software Engineering? Why not just call it programming or software development?
Systems Development AIMS 2710 R. Nakatsu. Overview Two philosophies of systems development –Systems Development Life Cycle (SDLC) –Prototyping Alternative.
Prototyping life cycle Important steps 1. Does prototyping suit the system 2. Abbreviated representation of requirements 3. Abbreviated design specification.
Software Engineering REQUIREMENT ENGINEERING. Software Engineering Phases.
© Bennett, McRobb and Farmer 2005
Lecture 4: Requirements Engineering COSI 120b, Principles of Software Engineering.
Teaching slides Chapter 3
Chapter 2 – Software Processes Lecture 2 1Chapter 2 Software Processes.
WATERFALL LIFE CYCLE SOFTWARE ENGINEERING. THE WATERFALL MODEL IS A SEQUENTIAL DESIGN PROCESS, USED IN SOFTWARE DEVELOPMENT PROCESSES, IN WHICH PROGRESS.
10 key principles of agile software development
It’s Agile …. like! A Corkman’s introduction to Agile software delivery.
Defining Technology's Great Expectations Organizations all over the world struggle with the choice between fully integrated systems or best-of-breed software.
1 Requirements Engineering for Agile Methods Lecture # 41.
Chapter 8: Maintenance and Software Evolution Ronald J. Leach Copyright Ronald J. Leach, 1997, 2009, 2014,
© 2005 Prentice Hall, Decision Support Systems and Intelligent Systems, 7th Edition, Turban, Aronson, and Liang 6-1 Chapter 6 Decision Support System Development.
Intro to design1 Intro To Design Systematic Design Process.
FINAL PROJECT 01: SKETCHING AND EARLY PROTOTYPING March 30, 2015 SDS136: Communicating with Data.
Lesson Objectives 1) Review the steps involved in problem solving 2) Review the stages of the System Life Cycle 3) Describe what prototyping is and the.
Building Information Systems
Definition CASE tools are software systems that are intended to provide automated support for routine activities in the software process such as editing.
Scope, Structure, Skeleton
Client Management Managing Client Expectations
Building Information Systems
Software Engineering: A Practitioner’s Approach, 7/e Chapter 2 Prescriptive Process Models copyright © 1996, 2001, 2005 R.S. Pressman & Associates, Inc.
Software Engineering: A Practitioner’s Approach, 7/e Chapter 2 Prescriptive Process Models copyright © 1996, 2001, 2005 R.S. Pressman & Associates, Inc.
CEN 4010 Intro to Software Engineering Professor Alex Roque
Adaptive Change Our Digital Journey ERION SERTI Head of IT Division.
Week 14 – Information System Development
DOCUMENTAL SOLUTIONS Market Analysis Intelligence & Tools
CHAPTER 10 METHODOLOGIES FOR CUSTOM SOFTWARE DEVELOPMENT
Rapid software development
Chapter 8 Prototyping and Rapid Application Development
Data Visualizer for CommCare
UNIT 6 RECENT TRENDS.
Presentation transcript:

Happy Design aka. Rapid Prototyping for the Web Why building backwards is faster, cheaper and delivers a better web product

So, here it is… Web design is undergoing a BIG change. Why?

1908 Hurley Machine Company Vacuum Cleaner

1993 Dyson Vacuum Cleaner

2003 iRobot’s Roomba

1896 Henry Ford’s First Car

1990 Ferrari

2001 Toyota Prius

2007 BMW Hydrogen 7

A big leap forward

Old Design Path The Aesthetics The System The Parts

Web Design: Old Way User Interface Application Layer Database

An Upside Down World

“It is not the strongest of the species that survives, nor the most intelligent that survives. It is the one that is the most adaptable to change.” - Charles Darwin

Web Design: New Way User Interface Application Layer Database

What is Rapid Prototyping? It’s is about actually building the product research user matrix graphs site maps schematics wireframes

Go back to kindergarten

The Alternative

Less Less mass Less software Less features Less documentation Less money Less support Less politics

Small Stay small Small teams are agile Small decisions Small changes Small problems

Interface Start with the interface Real screens that people are going to use Start with the experience Start with the hard stuff

Iterative Lower the cost of change Smoother project flow Frequent launches Allows tweaking Reduce fatigue

People Focused Users are human beings with emotions and anxieties Engineers are people too Not everyone can ‘see’ your ideas Speak to senses not concepts

“…But that’s the way it’s always been done.” Deals with the cause and not the symptoms Eliminates problems before it’s too late

Requirements Gathering “No other part of the work so cripples the resulting system if done wrong. No other part is more difficult to rectify later”. - Frederick Brooks, The Mythical Man-Month

The Spec

Real Examples

Show Functionality

Front and Back

Link to Real Examples

States Ideal Error Sample

Error 

Error

Sample 

Sample

Project Plans

Real Life ? ? ?

Budget ? Traditional Design Iterative Design

80:20 Revenue/ Activity Features

80:20 TimeFeatures

Advantages Faster Cheaper Visual Spec Marketing Tool User Testing Money Raising Tool And…

…No Waste

Questions?