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.
Prototyping is an activity during certain software development, it is the creation of prototypes, incomplete versions of the software program being developed. A prototype typically simulates only a few aspects of the features of the eventual program, and may be completely different from the eventual implementation.
The conventional purpose of a prototype is to allow users of the software to evaluate developers' proposals for the design of the eventual product by actually trying them out, rather than having to interpret and evaluate the design based on descriptions.
Prototyping has several reimbursements: The software designer and implementer can obtain response from the users early in the project. The client and the contractor can compare if the software completed matches the software specification, according to which the software program is built. It also allows the software engineer some imminent into the accuracy of preliminary project estimates and whether the deadlines and milestones proposed can be successfully met.
But even prototyping can have more advantages it is also and can produce counterproductive as you go along revising your prototypes because of some new idea that comes your way as you progresses in your project it can build counterproductive during the training task since you are editing it every now and then maybe you lack some polishing it before presenting it to others. It would be a big problem in your part since it interfere while you are there presenting it. Others may say that you make projects that are not efficient and liable. But because it was just a prototypes you can revised it anytime you want.
No comments:
Post a Comment