G063 – Prototyping. Learning Objective: At the end of this topic you should be able to: describe prototyping as a software development methodology.

Slides:



Advertisements
Similar presentations
Chapter 5 Development and Evolution of User Interface
Advertisements

Database Planning, Design, and Administration
Software Development Life Cycle. Why Do We need Software Development Models Helps to make sure that we cover all bases during planning and implementation.
Chapter 12 Prototyping and Testing Design of Biomedical Devices and Systems By Paul H. King Richard C. Fries.
References Prof. Saul Greenberg, University of Calgary, notes and articles INUSE 6.2 and RESPECT 5.3 Handbook Prof. , University of , Notes and articles.
Lecture # 2 : Process Models
The software process A software process is a set of activities and associated results which lead to the production of a software product. This may involve.
7M701 1 Software Prototyping Sommerville, Ian (2001) Software Engineering, 6 th edition: Chapter 8
Alternative Software Life Cycle Models By Edward R. Corner vol. 2, chapter 8, pp Presented by: Gleyner Garden EEL6883 Software Engineering II.
WHAT IS INTERACTION DESIGN?
1 Modeling System and Prototyping. 2 Introduction  Techniques for gathering users’ requirements  should be used in early stage(s) of SDLC  Information.
Chapter 8 Prototyping and Rapid Application Development
Saul Greenberg Evaluating Interfaces With Users Why evaluation is crucial to interface design General approaches and tradeoffs in evaluation The role of.
SE 555 Software Requirements & Specification 1 SE 555 Software Requirements & Specification Prototyping.
John Kelleher (IT Sligo) Cognitive Walkthrough. 1 Background Authors – Lewis & Polson (1991) Based on theory L&P CE+ Theory of Exploratory Learning Assesses.
ISE554 The WWW 3.4 Evaluation Methods. Evaluating Interfaces with Users Why evaluation is crucial to interface design General approaches and tradeoffs.
James Tam Evaluating Interfaces With Users Why evaluation is crucial to interface design General approaches and tradeoffs in evaluation The role of ethics.
Problem with Software Requirements are complex The client does not know the functional requirements in advance Requirements may be changing Technology.
Database System Development Lifecycle Transparencies
Damian Gordon.  Summary and Relevance of topic paper  Definition of Usability Testing ◦ Formal vs. Informal methods of testing  Testing Basics ◦ Five.
3.3.1 apid pplication evelopment. What Rapid Application Design is including: – Joint Development Application Workshops (JAD). – Timeboxing The benefits.
류 현 정류 현 정 Human Computer Interaction Introducing evaluation.
Chapter 8: Systems analysis and design
Principles of User Centred Design Howell Istance.
CS 360 Lecture 3.  The software process is a structured set of activities required to develop a software system.  Fundamental Assumption:  Good software.
Object-Oriented Software Engineering Practical Software Development using UML and Java Chapter 7: Focusing on Users and Their Tasks.
Software Engineering Management Lecture 1 The Software Process.
BTEC Unit 06 – Lesson 08 Principals of Software Design Mr C Johnston ICT Teacher
Introducing Evaluation: why, what, when, where Text p Text p 317 – 323;
Interaction Design CMU. Today’s objectives Continue Design approaches (UCD, ACD)  User-Centered Design  Activity-Centered Design.
Level 2 Prepared by: RHR First Prepared on: Nov 23, 2006 Last Modified on: Quality checked by: MOH Copyright 2004 Asia Pacific Institute of Information.
Systems Life Cycle. Know why it is necessary to evaluate a new system Understand the need to evaluate in terms of ease-of- use, appropriateness and efficiency.
Prototyping Software Development Approaches. A prototype is a working model Prototyping uses an evolutionary design model Listen to customer Listen to.
Prototyping What prototyping is The benefits of prototyping Low-fidelity and high-fidelity prototypes, and the advantages of each How to build paper prototypes.
Chapter 6 Prototyping, RAD, and Extreme Programming Systems Analysis and Design Kendall & Kendall Sixth Edition.
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.
System Construction System Construction is the development, installation and testing of system components.
Introduction to Software Development (Software Engineering - I)
PROJECT WORK System Development Cycle. OVERVIEW Project work for the HSC course follows five stages of the traditional system development cycle. The SDC.
Prototyping life cycle Important steps 1. Does prototyping suit the system 2. Abbreviated representation of requirements 3. Abbreviated design specification.
Teaching slides Chapter 3
Software Project Management
Software Development Process CS 360 Lecture 3. Software Process The software process is a structured set of activities required to develop a software.
Topic:- At the end we will be able to explain:- Why it is called Meta Model ?? Spiral Model Its Advantages & Disadvantages… Phases of Spiral Model...
Software Design and Development Development Methodoligies Computing Science.
Chapter 9 Database Planning, Design, and Administration Transparencies © Pearson Education Limited 1995, 2005.
Chapter 7: Designing solutions to problems OCR Computing for A Level © Hodder Education 2009.
HCC 831 User Interface Design and Evaluation. What is Usability?
IL Marking Get out your CPU / Memory answers Swap with someone else
Software Engineering Management
Monitoring Implementation and Sustainability
Approaches to Information Systems Development
Prototype Model Lecture-4.
Software Development Life Cycle
Object oriented system development life cycle
Life Cycle Models PPT By :Dr. R. Mall.
Software Prototyping.
FORMAL SYSTEM DEVELOPMENT METHODOLOGIES
Object Oriented Analysis and Design
Computer Science Life Cycle Models.
Chapter 2 Software Processes
Thursday’s Lecture Chemistry Building Musspratt Lecture Theatre,
Fundamentals of Human Computer Interaction (HCI)
User Interface Design and Evaluation
CS310 Software Engineering Lecturer Dr.Doaa Sami
Part 1 Q1 to Q5 of National 5 Prelim
Design Space of Software Development Methodologies
Chapter 8 Prototyping and Rapid Application Development
PRESENTED BY P.SANDEEP MSc,MTech
Presentation transcript:

G063 – Prototyping

Learning Objective: At the end of this topic you should be able to: describe prototyping as a software development methodology

Prototyping

normal design process involves producing a requirements specification –in consultation with the end users

Prototyping normal design process involves producing a requirements specification –in consultation with the end users prototyping involves producing a working system early in the design process –possibly without consultation with the end users

Prototyping normal design process involves producing a requirements specification –in consultation with the end users prototyping involves producing a working system early in the design process –possibly without consultation with the end users prototype system will not necessarily be efficient –because a full analysis has not been done. –will not have all the functionality end user requires.

Prototyping normal design process involves producing a requirements specification –in consultation with the end users prototyping involves producing a working system early in the design process –possibly without consultation with the end users prototype system will not necessarily be efficient –because a full analysis has not been done. –will not have all the functionality end user requires. –will be a step towards what the end user wants.

Steps in Prototyping

1.basic requirements identified

Steps in Prototyping 1.basic requirements identified 2.prototype developed

Steps in Prototyping 1.basic requirements identified 2.prototype developed 3.prototype tested by end user –shortcomings in the prototype are identified

Steps in Prototyping 1.basic requirements identified 2.prototype developed 3.prototype tested by end user –shortcomings in the prototype are identified 4.prototype is improved –production of a further prototype

Steps in Prototyping 1.basic requirements identified 2.prototype developed 3.prototype tested by end user –shortcomings in the prototype are identified 4.prototype is improved –production of a further prototype repeat steps 3&4 –until end user satisfied

Steps in Prototyping 1.basic requirements identified 2.prototype developed 3.prototype tested by end user –shortcomings in the prototype are identified 4.prototype is improved –production of a further prototype repeat steps 3&4 –until end user satisfied this process is called Iteration

Steps in Prototyping Initial Investigation Basic requirements for the new system identified. Prototype Developed This stage is repeated with each prototype being closer to meeting the end user's needs. Use the prototype Prototype is tested. Input from end user. End User's needs met? Working system The prototype has developed into a working system. Feedback from End User used to evaluate the effectiveness of the prototype No Yes

Advantages of Prototyping

a usable system produced early in the process, –allows the end users to evaluate it

Advantages of Prototyping a usable system produced early in the process, –allows the end users to evaluate it gives end users the opportunity to provide input –to the next stage of development

Advantages of Prototyping a usable system produced early in the process, –allows the end users to evaluate it gives end users the opportunity to provide input –to the next stage of development constant feedback should ensure that the resulting system really does match their needs

Advantages of Prototyping a usable system produced early in the process, –allows the end users to evaluate it gives end users the opportunity to provide input –to the next stage of development constant feedback should ensure that the resulting system really does match their needs user becomes comfortable with the HCI –has been part of the on-going development

Disadvantages of Prototyping once prototype is working, it may not be modified –management see early prototype to be working implement partially complete system too early –inefficient systems may never be tidied up early prototypes used instead of fully functional systems –may cause problems later if data usage increases if the system is to be adapted to meet new processing needs.

Examination Question A firm is going to introduce on-line ordering of its products. The user interface for the on-line ordering system will be developed using prototyping. (a) Describe the process of prototyping. [2] (b) Explain the process of iteration and why it is used. [4] January 2007 Q2

Iteration

“repeated design and refine”.

Iteration “repeated design and refine”. design is reviewed repeatedly –by the users

Iteration “repeated design and refine”. design is reviewed repeatedly –by the users users suggestions lead to changes

Why use Iteration?

users feel more confident about the outcome and so are more likely to use it.

Why use Iteration? users feel more confident about the outcome and so are more likely to use it. system correctly matches the needs & expectations of the users –because they have had an input in the design.

Why use Iteration? users feel more confident about the outcome and so are more likely to use it. system correctly matches the needs & expectations of the users –because they have had an input in the design. no waste of waste time & money producing something that’s not right.