A Developer Gateway To IT World...

Techie Uncle Software Testing Core Java Java Spring C Programming Operating System HTML 5 Java 8 ES6 Project

Prototype Model

Prototype Model

What is Prototype Model?

  • The Prototyping Model is one of the mostly used Software Development Life Cycle Models (SDLC models).

  • This model is used when the customers not clear about the requirements of product or what to do.

  • Here, we give the opportunity to the customer to see the product early in the life cycle by implement the application partially during the analysis phase.

  • Here, a prototype is developed, test, and then reworked when required until an satisfactory prototype is achieved and approved by customer.

  • The prototype does not always hold the exact logic used in the actual software application.

  • This Model works based on the customer requirements.

  • This Prototype Model is same as waterfall model.

  • A little difference between waterfall-model and prototype-model is we need customer interaction to develop prototype model.

  • It ensures that the customer constantly work with the system and provide a feedback.

  • It is a software model with limited functionality.

Phases for Prototype Model

  • Requirements gathering and analysis

  • Design Stage

  • Build a Prototype

  • Initial user evaluation

  • Development

  • Maintance and deliver

Advantages of Prototype Model

  • Customer satisfaction exists, because customer can feel the product at very early stage.

  • Requirement changes can be handle easily.

  • The developed prototype can be reused by developer.

  • Because of customers involvment so every difficult functioning can easily handle.

  • Missing functionality can be identified easily.

  • There will be less chance of software rejection.

  • This prototype flexible in designing.

  • Customer involvement helps to reduce the risk of failure.

Disadvantages of Prototype Model

  • It is a time taken if changes in requirements happens in prototype.

  • It can increase the system complexity.

  • This is very slow model to develop.

  • There may be far too many variations in software requirements when each time the prototype is evaluated by the customer.

  • This model can be costly.

  • Incomplete application may cause application not to be used .