Prototyping


	Prototyping
	Advantages Reduced time and costs,prototyping can improve the quality of requirements and specifications provided to the developers. Changes cost exponentially more to implement as they are detected later in development, so early clarification of what the user really wants can result in faster development and less development costs Improved and increased user involvement Prototyping requires the involvement of users. This enables them to see and interact with a prototype providing better and more complete feedback and specifications. Earlier feedback from end users can be obtained by the designer The avoidance of the expenses and difficulty of changing a finished software product	Disadvantages Confusions between the prototype and finished system End users can think that a prototype, intended to be thrown away, is actually a final system that merely needs to be finished. This can lead them to expect the prototype to accurately match the final system. Users can also become attached to features that were included in the prototype for user evaluation and then removed from the final system. The main aim of prototyping is that it is supposed to be done quickly. It is very tempting to develop a prototype that is too complex, leading to the development time being extended. This would also lead to an increase in the cost of the resources needed.
	Evaluation

Reduced time and costs,prototyping can improve the quality of requirements and specifications provided to the developers. Changes cost exponentially more to implement as they are detected later in development, so early clarification of what the user really wants can result in faster development and less development costs
Improved and increased user involvement
Prototyping requires the involvement of users. This enables them to see and interact with a prototype providing better and more complete feedback and specifications.
Earlier feedback from end users can be obtained by the designer
The avoidance of the expenses and difficulty of changing a finished software product

Confusions between the prototype and finished system
End users can think that a prototype, intended to be thrown away, is actually a final system that merely needs to be finished. This can lead them to expect the prototype to accurately match the final system. Users can also become attached to features that were included in the prototype for user evaluation and then removed from the final system.
The main aim of prototyping is that it is supposed to be done quickly. It is very tempting to develop a prototype that is too complex, leading to the development time being extended. This would also lead to an increase in the cost of the resources needed.

Get Revising