The basic idea in the Prototype model is that instead of freezing the requirements before a design or coding can proceed, a throwaway prototype is built on understanding the needs.
This prototype is developed based on the currently known requirements so the client can get an “actual feel” of the system and understand the desired design requirements better.
Prototyping is an attractive idea for complicated and extensive plans for which there is no manual process or existing system to help determine the requirements. The rough idea is usually not a complete system but a system with overall functionality.
Advantages of Prototype model:
- Users are actively involved in the development.
- Since in this methodology, a working model of the system is provided, the users better understand the system being developed.
- Errors can be detected much earlier.
- Quicker user feedback is available, leading to better solutions.
- Missing functionality can be identified easily.
- Confusing or difficult functions can be identified
- Requirements validation
- Quick implementation of, incomplete, but functional, application.
When to use the Prototype model:
A prototype model should be used when the desired system needs to interact with the end-users.
Typically, online systems, web interfaces with a very high amount of interaction with end-users, are best suited for the Prototype model. It might take a while for a system to be built that allows ease of use and needs minimal training for the end-user.
Prototyping ensures that the end-users constantly work with the system and provide feedback that results in a useable system.
Find out more about Prototype Engineering