prototyping....

Prototyping allows the users to try out a working model of a system before the actual system is complete. Explain how prototyping can be counterproductive if it creates task interference during training.


A prototype typically simulates only a few aspects of the features of the final program, and may be completely different from the final implementation. The usual purpose of prototyping is to allow the users of the system to evaluate developers’ proposals for the design of the final product by essentially trying them out, rather than having to understand and assess the design based on descriptions. It can also be used by end users to describe and prove requirements that developers have not considered, so controlling the prototype can be a key factor in the commercial relationship between providers and their clients.

Prototyping can be a big help since when it is made software and implementer can obtain feedback from the user early in the project. It allows the software engineer some insight into the accuracy of initial project estimates and whether the deadlines and milestones proposed can be successfully met and if it matches the software specification.

Prototyping can improve the quality of requirements and specifications provided to developers. Because changes cost exponentially more to implement as they are detected later in development. Because the early determination of what the user really wants can result in faster and less expensive software.

But despite the fact that prototyping improves and increases user involvement it can somehow produce problems or difficulties instead of helping to achieve a goal especially when it creates task obstruction during training. It can create insufficient analysis since focusing on a limited prototype can distract developers from properly analyzing the complete project. This can lead to overlooking better solutions, preparation of incomplete specifications or the conversion of limited prototypes into poorly engineered final projects that are hard to maintain.

A key property to prototyping is the fact that it is supposed to be done quickly. If the developers lose sight of this fact, they very well may try to develop a prototype that is too complex. User can become stuck in debates over details of the prototype, holding up the development team and delaying the final project.