6. Problems with prototyping
|Excessive development time
|When the end user is asked to evaluate a prototype and provide feedback there is a risk that they will be forever wanting to tweak the system, thus leading to delays in development
|Sometimes features appear in a prototype which are then removed from the final system. Users can become confused or disappointed with the final system if it differs greatly from the prototype.
|Increased development time
|The end user might start to ask for features to be included which were never in the original user requirements specification. This can lead to increased development time and costs.
|Too much focus on one part of the system
|When a lot of time is spent on a prototype of one specific part of the system, other parts of the system might end up being neglected
|Expense of prototyping
|Building a prototype costs money in terms of development time and possibly hardware. While the prototype is being worked on, the real system is on hold.
challenge see if you can find out one extra fact on this topic that we haven't already told you
Click on this link: disadvantages of prototypes