This document presents an overview of software prototyping models. It defines a software prototype as a working model with limited functionality that enables understanding customer requirements early and getting feedback. There are different approaches to prototyping including rapid throwaway, evolutionary, incremental, and extreme prototyping. The prototyping process involves building prototypes, getting customer feedback, refining the prototypes, and repeating until an acceptable final prototype is achieved to form the basis for the final product. The document discusses the pros and cons of the software prototyping model.

1. SOFTWARE PROJECT
MANAGEMENT
Presentation on: Software Prototyping Model

2. Software Prototype
◦ It refers to building a working model of software with some limited
functionality.
◦ It enables to understand customer requirements at an early stage
of development. It help to get feedback from the customers and
helps software designers and developers understand about what is
expected from the product under development

3. It offers a small scale facsimile of the end product and is used for obtaining customer
feedback.

4. The Concept of Software Prototyping
Model
◦ This model is used when the customers do not know the exact
project requirements beforehand.
◦ In this model, a prototype of the end product is first developed, tested
and refined as per customer feedback repeatedly till a final
acceptable prototype is achieved which forms the basis for
developing the final product.

5. Prototyping model phases:
The process continues until the user approves the prototype and finds the working model to be
satisfactory.
In this process model, the system is partially implemented before or during the analysis phase thereby
giving the customers an opportunity to see the product early in the life cycle.

6. Various
Approaches
of this
model
1. Rapid Throwaway
Prototyping
2. Evolutionary
prototyping
3. Incremental Prototype.
4. Extreme Prototype.
Implement
Product ana
maintain
Refining
Prototype
Build
Prototype
Quick Design
Requirement
gathering
and analysis
If the Prototype
is accepted
Rapid
Throwaway
Prototype
Evolutionary
Prototype
Incremental
Prototype
Extreme
Prototype
Select the
approach

7. Rapid Throwaway Prototype
Throwaway prototyping refers to the creation of a
model that will eventually be discarded rather than
becoming part of the final delivered software. And
every time the prototype is developed from the
scratch.
The steps in this approach are:
1.Write preliminary requirements
2.Design the prototype
3.User experiences/uses the prototype, specifies new
requirements
4.Repeat if necessary
5.Write the final requirements

8. Evolutionary Prototype
Evolutionary prototype, when built, forms the heart of
the new system, and the improvements and further
requirements will then be built.
The partial system is sent to customer sites.
As users work with the system, they detect
opportunities for new features and give requests for
these features to developers.
Developers then take these enhancement requests to
change the software-requirements specification,
update the design, recode and retest

9. Incremental Prototype
In incremental Prototyping, the final product
is decimated into different small prototypes
and developed individually. Eventually, the
different prototypes are merged into a
single product.
This method is helpful to reduce the
feedback time between the user and the
application development team.
Implement
ation
Testing
Design and
Developm
ent
Requirementgatheringand
Analysis
Build 1
Implement
ation
Testing
Design and
Developm
ent
Implement
ation
Testing
Design and
Developm
ent
Build 2
Build 3
FinalProduct
P1
P2
P3

10. Extreme Prototype
Extreme prototyping method is mostly used
for web development. It is consists of three
sequential phases.
1.Basic prototype with all the existing page is
present in the HTML format.
2.You can simulate data process using a
prototype services layer.
3.The services are implemented and
integrated into the final prototype.

11. Pros of Software Prototyping Model
• Users are actively involved in development. Therefore, errors can be detected in the initial stage of
the software development process.
• Helps team member to communicate effectively
• Customer satisfaction exists because the customer can feel the product at a very early stage.
• There will be hardly any chance of software rejection.
• Quicker user feedback helps you to achieve better software development solutions.
• Allows the client to compare if the software code matches the software specification.
• It helps you to find out the missing functionality in the system.
• It also identifies the complex or difficult functions.
• Encourages innovation and flexible designing.
• It is a straightforward model, so it is easy to understand.
• No need for specialized experts to build the model

12. Cons of Software Prototyping Model
• Prototyping is a slow and time taking process.
• The cost of developing a prototype is a total waste as the prototype is ultimately thrown away.
• Prototyping may encourage excessive change requests.
• Some times customers may not be willing to participate in the iteration cycle for the longer time
duration.
• There may be far too many variations in software requirements when each time the prototype is
evaluated by the customer.
• Poor documentation because the requirements of the customers are changing.
• It is very difficult for software developers to accommodate all the changes demanded by the
clients.