Please enable JavaScript.
Coggle requires JavaScript to display documents.
Types of Prototype (Throw-Away Prototyping (The objective of throw-away…
Types of Prototype
Throw-Away Prototyping
The objective of throw-away prototyping is to ensure that the system requirements are validated and that they are clearly understood.
Is NOT considered part of the final system. It is simply there to aid understanding and reduce the risk of poorly defined requirements.
The advantage of this approach is the speed with which the prototype is put together. It also focuses the user on only one aspect of the system so keeping their feedback precise.
One disadvantage with throw-away prototyping is that developers may be pressurised by the users to deliver it as a final system.
Incremental Prototyping
is a method of software development where the model is designed, implemented and tested incrementally (a little more is added each time) until the product is finished. It involves both development and maintenance.
The product is defined as finished when it satisfies all of its requirements. This model combines the elements of the waterfall model with the iterative philosophy of prototyping.
-
Disadvantages
-
Problems may arise pertaining to system architecture because not all requirements are gathered up front for the entire software life cycle.
Evolutionary Prototyping
The main goal when using evolutionary prototyping is to build a very robust prototype in a structured manner and constantly refine it. The reason for this approach is that the evolutionary prototype, when built, forms the heart of the new system, and the improvements and further requirements will then be built.
This technique allows the development team to add features, or make changes that couldn't be conceived during the requirements and design phase.
Evolutionary prototypes have an advantage over throwaway prototypes in that they are functional systems. Although they may not have all the features the users have planned, they may be used on an interim basis until the final system is delivered.
In evolutionary prototyping, developers can focus themselves to develop parts of the system that they understand instead of working on developing a whole system.