Throwaway Prototyping model refers to the creation of a model that will eventually be discarded rather than reusing the same one for the final delivered software. After understanding of preliminary requirements, a simple working model of the system is constructed to visually show the customer or the end-users what the end-product may look like when they are implemented into a finished system.
The objective is to understand the system requirements clearly. Starts with poorly understood requirements. Once the requirements are cleared, the system will be developed from the beginning again. This model is suitable if the requirements are vague but stable.
Throwaway Prototyping can be done quickly
Higher probability of satisfying all the requirements when the final product is built through this model
Able to refine them early in the development of the software, if they get the quick feedbacks
Making changes early in the development lifecycle is extremely cost effective
Disadvantages of throw away prototyping model
Important features may have been left out of the prototype to simplify rapid implementation
It may not be possible to prototype some of the most important parts of the system such as safety-critical functions within short span of time
An implementation has no legal standing as a contract between customer and vendor
Non-functional requirements such as those concerning reliability, robustness and safety cannot be adequately tested in a prototype implementation.
Speed is crucial in implementing a throwaway prototype, since with a limited budget of time and money little can be expended on a prototype that will be discarded.