COEN/ELEC 390 1.  What is prototyping  Why prototyping  Types of prototyping  Advantages of each  Recommendations  Incremental Development? 2.

Slides:



Advertisements
Similar presentations
Software Processes.
Advertisements

SWEN 5130 Requirements EngineeringSlide 1 Software Prototyping u Animating and demonstrating system requirements.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 4 Slide 1 Software Processes.
1 Software Processes A Software process is a set of activities and associated results which lead to the production of a software product. Activities Common.
Multimedia Specification Design and Production 2013 / Semester 1 / week 7 Lecturer: Dr. Nikos Gazepidis
Unit 2. Software Lifecycle
©Ian Sommerville 2006Software Engineering, 8th edition. Chapter 4 Slide 1 Software Processes.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 1 Slide 1 المحاضرة الثانية.
Prescriptive Process Models Developed to bring order and structure to the software development process. To get away from the chaos of most development.
 2004 by SEC Chapter 2 Software Development Process Models.
Soft. Eng. II, Spring 2002Dr Driss Kettani, from I. Sommerville1 CSC-3325: Chapter II Chap1: Software Engineering Models (Review) Mandatory reading: chapter.
The Software Life Cycle Revisited CSCU 411 Software Engineering Chapman University College San Diego.
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.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 4 Slide 1 Software Processes.
7M701 1 Software Prototyping Sommerville, Ian (2001) Software Engineering, 6 th edition: Chapter 8
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 17 Slide 1 Rapid software development.
Rapid software development
Alternate Software Development Methodologies
Software Engineering Software quality. Software quality characteristics:  External: user is aware of. User cares about.  Internal: programmer is aware.
Software Engineering 6/e, Chapter 8
©Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 8 Slide 1 Software Prototyping l Rapid software development.
CS 425/625 Software Engineering Software Processes
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 4 Slide 1 Software Process Models.
Software Engineering Incorporating Interface Design Into Software Engineering.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 4 Slide 1 Software Processes.
© 2005 Prentice Hall, Decision Support Systems and Intelligent Systems, 7th Edition, Turban, Aronson, and Liang 6-1 Chapter 6 Decision Support System Development.
CMSC 345, Version 1/03 An Overview of Software Processes Reference: Software Engineering, by Ian Sommerville, 6 th edition, Chapter 3.
Chapter 3 Software Processes.
©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.
CSI315 Web Technology and Applications
Petter Nielsen Information Systems/IFI/UiO 1 Software Prototyping.
Chapter 2 The process Process, Methods, and Tools
 Software Models.  A software life-cycle model is a descriptive and diagrammatic representation of the software life-cycle. This includes a series of.
What is the Spiral Development Model? Lifted From
©Ian Sommerville 1995/2000 (Modified by Spiros Mancoridis 1999) Software Engineering, 6th edition. Chapter 8 Slide 1 Software Prototyping l Animating and.
Software Processes.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 4 Slide 1 Software Processes.
CS 360 Lecture 3.  The software process is a structured set of activities required to develop a software system.  Fundamental Assumption:  Good software.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 4 Slide 1 Software Processes.
SOFTWARE PROTOTYPING Anil Kumar.Arikepudi.
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.
Rapid software development 1. Topics covered Agile methods Extreme programming Rapid application development Software prototyping 2.
소프트웨어공학 강좌 1 Chap 7. Software Prototyping - Rapid software development to validate requirements -
Decision Support System Development By Dr.S.Sridhar,Ph.D., RACI(Paris),RZFM(Germany),RMR(USA),RIEEEProc. web-site :
1 SWE Introduction to Software Engineering Lecture 4.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 4 Slide 1 Software Processes.
Methodologies. Contents Waterfall Model Evolutionary Models Incremental Development.
Prototyping Software Development Approaches. A prototype is a working model Prototyping uses an evolutionary design model Listen to customer Listen to.
CS205 Software Engineering_Overview Specifications: The Ariane 6 must be able to deliver both satellite hardware and crew into geostationary orbit. (Ariane.
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.
Chapter 13: Software Life Cycle Models Omar Meqdadi SE 273 Lecture 13 Department of Computer Science and Software Engineering University of Wisconsin-Platteville.
Software Prototyping Rapid software development to validate requirements.
CS223: Software Engineering Lecture 4: Software Development Models.
©Ian Sommerville 2006Software Engineering, 8th edition. Chapter 4 Slide 1 Software Processes.
CC20O7N Software Engineering 1 CC2007N Software Engineering 1 Part 1 Introduction to Software Engineering.
©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.
Software Engineering, 8th edition. Chapter 4 1 Courtesy: ©Ian Sommerville 2006 FEB 13 th, 2009 Lecture # 5 Software Processes.
Software Development Process CS 360 Lecture 3. Software Process The software process is a structured set of activities required to develop a software.
Lectures 2 & 3: Software Process Models Neelam Gupta.
A framework that describes the activities performed at each stage of a software development project. A life-cycle or a software process is the organisational.
1 Chapter 2 SW Process Models. 2 Objectives  Understand various process models  Understand the pros and cons of each model  Evaluate the applicability.
Laurea Triennale in Informatica – Corso di Ingegneria del Software I – A.A. 2006/2007 Andrea Polini II. Software Life Cycle.
Prototype Model Lecture-4.
Life Cycle Models PPT By :Dr. R. Mall.
The V Model The V Model Damian Gordon Damian Gordon.
Software life cycle models
Software Processes.
Requirements Analysis Techniques
Presentation transcript:

COEN/ELEC 390 1

 What is prototyping  Why prototyping  Types of prototyping  Advantages of each  Recommendations  Incremental Development? 2

 Waterfall model..  Does not really work Design / Coding / Integration Test / Acceptance Test Design 49.2 / 34.1 / 10.3 / 6.4  Hence, prototyping is used to clarify requirements  The first push-button phone had 2000 prototypes built! 3

4

 ~ 0 cost of fabricating different versions  Most cost associated with developing the first fully working version  Hence, software prototyping used for: ◦ Rapid development of a basic & inefficient executable version ◦ Rapid development of the user interface  This assumes throw-away prototyping 5

6

 Throw-away prototyping actually saves money by eliminating the need for expensive late-cycle re- engineering  To ensure it is thrown away, a very high-level language is used  This contrasts with evolutionary prototyping, where the prototype grows into the final product 7

8

 Resulting system easier to use  User needs better accommodated  Resulting system has fewer features  Problems detected earlier  Design is of higher quality  Resulting system easier to maintain  Development incurs less effort 9

 Resulting systems has more features  Worse performance  Lesser quality design  Resulting systems harder to maintain  Prototyping approach requires experienced engineers 10

11

1. Good for situations where user requirements are unclear 2. Good where there is emphasis on user interface 3. User must be made aware of the costs of changes/additions and that proto’s are not products 4. Prototyping must be controlled, with explicit procedures and documentation 12

13