Prototype Model in Software Engineering | Advantages and Disadvantages
In Prototype Model, first a Prototype is developed. Prototype can be a sample software or some Proof of Concept(POC). And then it is presented to the Customer. If customer accepts the product then the original software development starts. In this model Customer satisfaction is more because actual development starts after the customer acceptance of the Prototype and the changes suggested by the customer will be incorporated when actual product development starts. Hence the customer rejection will be very less.
This model is also a very good idea for the new Products, which are not in proposal and are proactively developed and demonstrated to customers to get more work from them.
Process involved in prototype SDLC model:
- Requirements are collected
- Feasibility Study
- Develop a prototype
- Test prototype
- Customer Review
- Customer Approval
As you see in the process above actual Design and Coding start after several steps and Customer Approval.
- Customer Satisfaction is more.
- Customer rejection is less.
- Customer can look and feel the product at an early stage.
- Customer review.
- Flexible for changes.
- Prototype can be reused.
- No parallel Deliverables.
- No requirements review.
- Time consuming if the prototype changes.
Q) When we are going to use prototype model?
Ans: When ever the customer is new to the software industry or he is not clear of the requirements then we are going to use prototype model.