© 2007 Pearson Education, Inc. Publishing as Pearson Addison-Wesley 1 Prototyping.

Slides:



Advertisements
Similar presentations
Chapter 11 Design, prototyping and construction 1.
Advertisements

Design, prototyping and construction
SWEN 5130 Requirements EngineeringSlide 1 Software Prototyping u Animating and demonstrating system requirements.
©Ian Sommerville 2006Software Engineering, 8th edition. Chapter 4 Slide 1 Software Processes.
What is Software Design?. Systems Development Life- Cycle Planning Analysis Design Implementation Design.
7M701 1 Software Prototyping Sommerville, Ian (2001) Software Engineering, 6 th edition: Chapter 8
AN OVERVIEW BY JAMIE STARKE The Role of Prototyping.
ACTIVELY ENGAGING THE STAKEHOLDER IN DEFINING REQUIREMENTS FOR THE BUSINESS, THE STAKEHOLDER, SOLUTION OR TRANSITION Requirements Elicitation.
Human Computer Interaction
DESIGN, PROTOTYPING and CONSTRUCTION
Prototyping Techniques
Prototyping. Introduction Low-fidelity prototyping High-fidelity prototyping Compromises in prototyping From design to implementation.
Requirements Analysis CS 414 – Software Engineering I Donald J. Bagert Rose-Hulman Institute of Technology January 7, 2003.
Part 2d: Requirements Chapter 2: How to Gather Requirements: Some Techniques to Use Chapter 3: Finding Out about the Users and the Domain Chapter 4: Finding.
Copyright 2002 Prentice-Hall, Inc. Modern Systems Analysis and Design Third Edition Jeffrey A. Hoffer Joey F. George Joseph S. Valacich Chapter 15 Finalizing.
SE 555 Software Requirements & Specification 1 SE 555 Software Requirements & Specification Prototyping.
What is a prototype? A prototype is a small scale model of your larger product. Can be a physical object, or a simple software program. Many physical.
Software Life Cycle Model
CMSE323 HUMAN COMPUTER INTERACTION CHAPTER IV on LOW FIDELITY PROTOTYPING HUMAN FACTORS IN INTERFACE DESIGN DR. ADNAN ACAN.
Sofia Carlander Kinoshita Laboratory 2004/2005
©Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 8 Slide 1 Software Prototyping l Rapid software development to validate requirements l.
©Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 8 Slide 1 Software Prototyping l Rapid software development to validate requirements.
© 2007 Pearson Education, Inc. Publishing as Pearson Addison-Wesley 1 Context of Software Product Design.
© 2007 Pearson Education, Inc. Publishing as Pearson Addison-Wesley 1 Software Design Processes and Management.
Human Computer Interaction & Usability Prototyping Design & Prototyping HCI Prototyping.
S/W Project Management
Petter Nielsen Information Systems/IFI/UiO 1 Software Prototyping.
Tietojärjestelmien peruskurssi Systeemisuunnittelu ja prototyyppimenetelmä Malin Brännback.
© 2007 Pearson Education, Inc. Publishing as Pearson Addison-Wesley 1 A Discipline of Software Design.
Overview Prototyping and construction Conceptual design
HCI Prototyping Chapter 6 Prototyping. Learning Outcomes At the end of this lecture, you should be able to: –Define the term “prototyping” –Explain the.
Design, prototyping and construction CSSE371 Steve Chenoweth and Chandan Rupakheti (Chapter 11- Interaction Design Text)
Copyright © 2008 Pearson Education, Inc. Publishing as Pearson Addison-Wesley The Resonant Interface HCI Foundations for Interaction Design First Edition.
Merja & Pauli Rapid prototyping & other stuff.
Chapter 11: Software Prototyping Omar Meqdadi SE 273 Lecture 11 Department of Computer Science and Software Engineering University of Wisconsin-Platteville.
©Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 8 Slide 1 Software Prototyping l Rapid software development to validate requirements.
AVI/Psych 358/IE 340: Human Factors Prototyping October 10-13, 2008.
© 2007 Pearson Education, Inc. Publishing as Pearson Addison-Wesley 1 Product Design Finalization; Inspections.
소프트웨어공학 강좌 1 Chap 7. Software Prototyping - Rapid software development to validate requirements -
Copyright © 2008 Pearson Education, Inc. Publishing as Pearson Addison-Wesley The Resonant Interface HCI Foundations for Interaction Design First Edition.
Review of Software Process Models Review Class 1 Software Process Models CEN 4021 Class 2 – 01/12.
Chapter 9 Prototyping. Objectives  Describe the basic terminology of prototyping  Describe the role and techniques of prototyping  Enable you to produce.
© 2006 ITT Educational Services Inc. SE350 System Analysis for Software Engineers: Unit 10 Slide 1 Chapter 13 Finalizing Design Specifications.
Prototyping What prototyping is The benefits of prototyping Low-fidelity and high-fidelity prototypes, and the advantages of each How to build paper prototypes.
1 Human Computer Interaction Week 7 Prototyping. 2 Introduction Prototyping is a design technique where users can be involved in testing design ideas.
Chapter 6: Thinking about requirements and describing them.
Inception Chapter 4 Applying UML and Patterns -Craig Larman.
Prototyping By: Michael McBee & Shere Stewart. Prototyping What is Prototyping? It is an iterative process involving analysts and users where a model.
Prototyping. A software requirements prototype is a mock-up or partial implementation of a software system – Helps developers, users, and customers better.
SOFTWARE ENGINEERING MCS-2 LECTURE # 4. PROTOTYPING PROCESS MODEL  A prototype is an early sample, model or release of a product built to test a concept.
Software Prototyping Rapid software development to validate requirements.
Requirements Validation
Design, Prototyping and Construction In “ pure ” waterfall, design begins after requirements development has finished However, in the real world there.
Prototyping life cycle Important steps 1. Does prototyping suit the system 2. Abbreviated representation of requirements 3. Abbreviated design specification.
Concept Mapping: A Graphical System for Understanding the Relationship between Concepts. ERIC Digest.
Prototyping. Objectives By the end of class, you will be able to… Explain why prototyping is an important phase of design. Create and test paper prototypes.
©Ian Sommerville 2000, Tom Dietterich 2001 Slide 1 System prototyping l Prototyping is the rapid development of a system l In the past, the developed system.
© 2007 Pearson Education, Inc. Publishing as Pearson Addison-Wesley 1 Product Design Alternative Generation, Evaluation, and Selection.
Overview Prototyping Construction Conceptual design Physical design Generating prototypes Tool support.
What is a sketch? 1 Concepts (and selected visuals) from this slide deck are based on: -Buxton, B. (2007) Sketching User Experiences: Getting the Design.
Design, prototyping and construction(Chapter 11).
CEN3722 Human Computer Interaction Prototyping Dr. Ron Eaglin.
INF385G: Topic Discussion Huang, S. C.
Design, prototyping and construction
Chapter 11 Design, prototyping and construction 1.
The Role of Prototyping
Usability Techniques Lecture 13.
Computer Science Department
Design, prototyping and construction
COMP444 Human Computer Interaction Prototyping
Presentation transcript:

© 2007 Pearson Education, Inc. Publishing as Pearson Addison-Wesley 1 Prototyping

2 Objectives  To survey the use of modeling in product design  To explain different kinds of prototypes  To list the uses of prototypes  To present prototyping risks and mitigation strategies

© 2007 Pearson Education, Inc. Publishing as Pearson Addison-Wesley 3 Topics  Modeling in product design  Prototypes Horizontal and vertical Throwaway and evolutionary Low- and high-fidelity  Prototype uses  Prototyping risks

© 2007 Pearson Education, Inc. Publishing as Pearson Addison-Wesley 4 Modeling in Product Design Modeling is useful throughout product design. Document problem domains Explore stakeholder needs and desires Test design constraints Detect misunderstandings, and incomplete or inconsistent specifications Generate design alternatives Evaluate and select design alternatives Record product designs

© 2007 Pearson Education, Inc. Publishing as Pearson Addison-Wesley 5 Prototypes A prototype is a special kind of model. Represent a target (the product) Must work in some way A prototype is a working model of part or all of a final product.

© 2007 Pearson Education, Inc. Publishing as Pearson Addison-Wesley 6 Horizontal & Vertical Prototypes  A horizontal prototype realizes part or all of a product’s user interface. One program layer Mock-ups  A vertical prototype does processing apart from that required to present a user interface. Cuts across program layers Proof of concept prototype

© 2007 Pearson Education, Inc. Publishing as Pearson Addison-Wesley 7 Throwaway and Evolutionary Prototypes  A throwaway prototype is developed as a design aid and then discarded. Exploratory prototype Quick to build Risky to use in the final product  An evolutionary prototype is a prototype that becomes (part of) the final product. Iterative development More expensive to build Difficult to build to handle change

© 2007 Pearson Education, Inc. Publishing as Pearson Addison-Wesley 8 Low- and High-Fidelity Prototypes  Fidelity is how closely a prototype represents the final product it models. There is a continuum of fidelity  Low-fidelity prototypes Paper or rough electronic prototypes “Executed” by walking through interactions Very quick and easy  High-fidelity prototypes Usually electronic Take longer to build (good tools help)

© 2007 Pearson Education, Inc. Publishing as Pearson Addison-Wesley 9 Prototype Uses 1  Needs elicitation Basis for discussion, jogs memory, inspires ideas Usually throwaway horizontal paper prototypes  Needs analysis Captures developers understanding of needs Usually throwaway horizontal prototypes at various levels of fidelity  Requirements generation and refinement Design alternatives Explore new ideas Often horizontal throwaway paper prototypes

© 2007 Pearson Education, Inc. Publishing as Pearson Addison-Wesley 10 Prototype Uses 2  Requirements evaluation and selection Usability studies Requirements feasibility Usually higher fidelity; sometimes vertical prototypes  Design finalization Better for review than an SRS Advisable to make high-fidelity evolutionary horizontal prototypes

© 2007 Pearson Education, Inc. Publishing as Pearson Addison-Wesley 11 Prototyping Risks  Using a throwaway prototype as the basis for development Avoid making high-fidelity throwaway prototypes Make it very clear to stakeholders that the prototype only appears to work  Fixation on appearance rather than function Don’t use prototypes for functional needs elicitation Use low-fidelity prototypes for needs elicitation  Prototype is “better” than the final product Use low-fidelity prototypes Ensure that high-fidelity prototypes are accurate representations

© 2007 Pearson Education, Inc. Publishing as Pearson Addison-Wesley 12 Summary  A variety of models are used for several tasks in product design.  A prototype is a working model of (part of) a final product.  Prototypes can be throwaway or evolutionary, horizontal or vertical, and have varying degrees of fidelity.  Prototypes are useful for needs elicitation, for alternative generation, evaluation, and selection, and for design finalization.  Risks attendant on the use of prototypes can usually be mitigated.