1) When prototype is shown to the user, he gets a proper clarity and 'feel' of the functionality of the software and he can suggest changes and modifications. 2) This type of approach of developing the software is used for non-IT-literate people. They usually are not good at specifying their requirements, nor can tell properly about what they expect from the software. 3) When client is not confident about the developer's capabilities, he asks for a small prototype to be built. Based on this model, he judges capabilities of developer. 4) Sometimes it helps to demonstrate the concept to prospective investors to get funding for project. 5) It reduces risk of failure, as potential risks can be identified early and mitigation steps can be taken. 6) Iteration between development team and client provides a very good and conductive environment during project. 7) Time required to complete the project after getting final the SRS reduces, since the developer has a better idea about how he should approach the project.
Disadvantages of Prototyping Model:
1) Prototyping is usually done at the cost of the developer. So it should be done using minimal resources. It can be done using Rapid Application Development (RAD) tools. Please note sometimes the start-up cost of building the development team, focused on making prototype, is high. 2) Once we get proper requirements from client after showing prototype model, it may be of no use. That is why, sometimes we refer to the prototype as "Throw-away" prototype. 3) It is a slow process. 4) Too much involvement of client, is not always preferred by the developer. 5) Too many changes can disturb the rhythm of the development team. http://www.ianswer4u.com/2011/11/prototype-model-advantages-and.html#axzz3JBF3b0P1
Nov 15th, 2014
Studypool's Notebank makes it easy to buy and sell old notes, study guides, reviews, etc.