Prototype Model

Prototype Model

Overview on Prototype Model:
It begins with requirements gathering. Developers and Customers meet and define the overall objectives of the software.

Developers prepare design documents using all available requirements then build the prototypes, prototypes are sent to Customer, and Customer evaluates Prototypes and gives feedback. Developers redefine Requirements, modify software design and produce modified Prototypes. Process will be continued like this, after getting Customer’s confirmation Developers Start Regular process; Software Design, Coding (Implementation), Testing and Release & Maintenance.

The Objective of this approach is getting clear (Complete and Correct)
Requirements from Customers in order to avoid Defects multiplication.

Prototype Model Diagram

Advantages of Prototype Model:

o    The customer doesn’t need to wait long as in the Linear Model or Waterfall Model.

o    Feedback from customer is received periodically and the changes don’t come as a last minute surprise.

o    Customer’s interaction improves the Quality as well success rate.

Disadvantages of Prototype Model:

o    It is an expensive approach and time taking process when its compare to sequential models like Waterfall model.

o    Customer could believe the prototype as the working version.

o    Developer also could make the implementation compromises.

o    Once Requirements finalized then adopting changes in Requirements and adding New Requirements are difficult.


Great efforts! I think the best part of going for prototype model is that you will be able to offer your clients with a working model before getting deeper into the project. This will help you to improve client-developer interactions. There are some more advatages of using this model.

Post a Comment