7.3 Prototyping

We begin by modeling parts of the system and if the prototyping process is successful, then we develop the rest of the system. They do the prototype until users satisfied with the system and it will be ready to release. The prototype can be served as a basis or reference for the system production itself. Because of that, normally it starts with those parts of the system that are the most difficult. If the difficult part can be solved, then there is the rest of the system can be developed. But if the most difficult part cannot be solved, the project may be cancelled. Although it is good since the users participate during the prototyping process but sometimes comes with several disadvantages. More time spends in the prototyping. But on the other way, the system developed is the best suit with the user requirement. If the prototype are going to be used as an actual system, so we need to follow the entire requirement that have been defined such as languages and tools selected.

7.3.1 Throwaway prototyping

Throwaway prototyping is a prototyping approach where the prototype will be discarded after the design. Like with its name, throwaway prototyping does not keep the prototype that has been developed. It's different with evolutionary, there is never any intention to convert the prototype into working system. Prototype is developed quickly in order to demonstrate some aspect of the system which is not clear or to help users. Different with evolutionary prototyping, throwaway prototyping need to consider a simple and easy to use programming language. Then, the prototype can be act as a basis for the production a new system or discarded.