Prototyping Model

Prototyping Model
Before starting actual development,
◦ a working prototype of the system should
first be built.
A prototype is a toy implementation of a
system:
◦ limited functional capabilities,
◦ low reliability,
◦ inefficient performance.
2
Prototyping Model (CONT.)

In many instances the client only has a general view of what

is to be expected from the software product. In such a
scenario where there is an absence of detailed information
regarding the input to the system, the processing needs and
the output requirements, the prototyping model may be
employed.
Question
When we should choose Prototyping model?
A) When complete requirement is given
B) When requirements are not properly cleared.
C) When client understand the development process.
D) None of the mentioned.
Prototyping Model (CONT.)

The developed prototype is submitted to the

customer for his evaluation:
◦ Based on the user feedback, requirements
are refined.
◦ This cycle continues until the user approves
the prototype.
The actual system is developed using the
iterative waterfall approach.

5
Prototyping Model (CONT.)

Build Prototype

Requirements Customer Customer

Gathering Quick Design Evaluation of satisfied
Design
Prototype

Implement
Refine
Requirements
Test

Maintenance

6
Prototyping Model (CONT.)

REQUIREMENTS AND GATHERING ANALYSIS:

◦ The user is interviewed to gather information regarding the requirement of the
software.
DESIGN:
◦  Preliminary design or quick design involving only the important aspects is
created.
BUILD PROTOTYPE:
◦ Information from the quick design is modified to form a prototype.
Prototyping Model (CONT.)

CUSTOMER EVALUATION OF PROTOTYPE:

◦ The proposed system is now presented to the user for consideration.
PROTOTYPE REFINEMENT:
◦ Once the user evaluates the prototype the required changes are made and the
final prototype is used to make the final system.
ENGINEER PRODUCT: 
◦ The final thoroughly tested and undergoes routine maintenance in order to
avoid any future system failures.
Types of Prototyping
1. Throwaway prototypes
2. Evolutionary prototypes
3. Incremental prototypes
4. Extreme prototypes
Throwaway Prototypes
•The prototype is developed rapidly based on the initial
requirements and given to the client for review.
•Once the client provides feedback, final requirements
are updated and work on the final product begins. As
the name suggests, the developed prototype is
discarded, and it will not be part of the final product.
•It is also known as close-ended prototyping.
Evolutionary Prototypes
•A prototype is made, and the client feedback is received. Based
on the feedback, the prototype is refined until the client
considers it the final product.
•It follows an incremental development approach and saves
time compared to the rapid throwaway prototyping method as
in evolutionary prototyping old prototype is reworked rather
than developing a new prototype from scratch.
•It is also known as breadboard prototyping.
Incremental Prototypes
•In this type of prototype model, final product requirements are
break into smaller parts and each part is developed as a
separate prototype.
•All the parts (prototypes) are merged which becomes a final
product.
Extreme Prototypes
•This type of prototyping model is mainly used for web
applications. It is divided into three phases
oFirst, a basic prototype with static pages is created, it consists
of HTML pages.
oNext, using a services layer, data processing is simulated.
oIn the last phase, services are implemented.
Advantages of Prototype Model
•Quick client feedback is received which speeds up the development
process. Also, it helps the development team to understand the
client’s needs.
•Developed prototypes can be used later for any similar projects.
•Any missing functionality and any error can be detected early.
•It is useful when requirements are not clear from the client’s end,
even with limited requirements, the development team can start the
development process.
Disadvantages of Prototype Model
•It is a time-consuming process or method as multiple prototypes might
be needed until the client reaches the final requirements. The Client may
not have an explicit idea about what they want.
•This method involves too much client interaction and involvement, which
can be done only with a committed client.
•In the beginning, it is a bit difficult to predict the exact amount of time
needed to reach the final product.
•While coding, developers do not have a broad perspective of what is
coming, because of which they might use an underlying architecture that
is not suitable for a final product.
Difference Between Prototype and
waterfall model.
In Waterfall Model:
•The waterfall model directly delivers the final product to the user
and his feedback is only taken in, before the design phase.
In prototype Model:
•The prototype model creates several rough working applications and
involves constant user interaction, until the developers come up with
the final application
Difference Between Prototype and
waterfall model.(Cont.)
In Waterfall Model:
The waterfall model is better suited for a more conventional
software projects, where user requirements are clear, right from the
start.
In prototype Model:
The prototype model is well suited for online applications where user
interfaces are the most important component.
Question
Which of the following are advantages of iterative model?
A. To iterate the phases to find the missing necessity
B. Simpler to manage
C. Early feedback
D. All of the mentioned above
Next Lecture: Spiral
Model