Prototype Model

Process of developing a working replication of a product or system that has to be engineered. A prototype usually turns out to be a very crude version of the actual system, possibly exhibiting limited functional capabilities, low reliability, and inefficient performance as compared to actual software. 

 

Utility:

It is mostly used in Software Development Life Cycle Models (SDLC models).This model is used when the customers do not know the exact project requirements beforehand.

Steps of Prototype Model:

1. Requirement Gathering and Analyst
2. Quick Decision
3. Build a Prototype
4. Assessment or User Evaluation
5. Prototype Refinement
6. Engineer Product

Working:

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.

It starts by interviewing the customers and developing the incomplete high-level paper model. It supports early product marketing and reduces Maintenance cost.

Used to build the initial prototype supporting only the basic functionality as desired by the customer. Once the problems are encountered by the customer, the prototype is further refined to eliminate them. The process continues until the user approves the prototype and finds the working model to be satisfactory. 

Advantages:

• In the development process of this model users are actively involved.
• The development process is the best platform to understand the system by the user.
• Errors are detected much earlier.

Disadvantages:

• An unstable implemented prototype often becomes the final product.
• The client involvement is more and it is not always considered by the developer.
• Require extensive customer collaboration
  • Costs customer money
  • Needs committed customer
  • Difficult to finish if customer withdraw
  • May be too customer specific, no broad market