Prototyping Model: Presented by Anip Shah

Download as pptx, pdf, or txt
Download as pptx, pdf, or txt
You are on page 1of 8

Prototyping Model

Presented by
Anip Shah

Prototyping Model
The prototyping model requires that before carrying out
the development of the actual software , a working
prototype of the system should be built.
A prototype usually turns out to be a very crude version
of the actual system, possibly exhibiting limited
functional capabilities as compared to the actual
software.
The prototyping approach is used in the requirement
gathering and in the analysis phase to capture the exact
requirement of the proposed system. After the
requirements are frozen, the remaining phases of the
development process needs to be executed
Prototype model should be used when the desired system
needs to have a lot of interaction with the end users.

Steps in Prototyping Model


1.
2.
3.
4.

Basic Requirement Identification


Developing the initial Prototype
Review of the Prototype
Revise and enhance the Prototype

Code

Prototyping Model Diagram


Requirement
Gathering

Quick Design
Refine
requirements
incorporating
customer
suggestions

Build Prototype

Customer
evaluation of
Prototype

Code
Design

Impleme
nt

Impleme
nt

Impleme
nt

Types of Prototyping Models


Throwaway/Rapid Prototyping
This type of prototyping uses very little efforts with minimum
requirement analysis to build a prototype. Once the actual
requirements are understood, the prototype is discarded and the
actual system is developed with a much clear understanding of
user requirements.
Examples of throwaway prototypes include screen mock-ups and
story boards.
Evolutionary Prototyping
Evolutionary prototyping is based on building actual functional
prototypes with minimal functionality in the beginning. The
prototype developed forms the heart of the future prototypes on
top of which the entire system is built. Using evolutionary
prototyping only well understood requirements are included in
the prototype

Advantages of Prototyping Model


Increases user involvement in the product even before
implementation
Since working model of the system is displayed, the
users get a better understanding of the system being
developed
Reduces time and cost as the defects can be detected
much earlier
Missing functionality can be identified easily
Confusing or difficult functions can be identified
Helps in reducing risk associated with the project
The developer gains experience and insight by
developing a prototype
Code

Disadvantages of Prototyping Model


May increase the complexity of the system as scope of
the system may expand beyond original plans
Risk of insufficient requirement analysis owing to too
much dependency on prototype
User confusion of prototype and finished system
Developer attachment to prototype
The effort invested in building prototype may be too
much if not monitored properly
It may comprise on the overall quality of the software in
the rush to develop the prototype

Code

Thank You

You might also like