The application prototyping approach to software development gives users what they want by employing principles used in other engineering disciplines, i.e. build a working model and use it. Critically discuss the arguments for and against this approach showing how the software development life cycle is consequently affected. What are the necessary conditions for it to be successful and what are the dangers/problems that could arise?

What will be an ideal response?

The arguments against prototyping tend to support the conventional approach to software
development, which maintains, for example, that all requirements can be specified, the static
model is correct, people can communicate effectively etc. Many of the arguments supporting
prototyping are the opposite, such as, people do not communicate effectively, they do not know
what they want necessarily etc. therefore it is better to build a model and show it to them, thus
obtaining feedback. The prototype effectively captures requirements specifications, therefore it
fits in to the software development lifecycle after initial requirements analysis and prior to any
system development. It relies on the use of appropriate software tools, requires a commitment to
the approach on the part of both developers and clients who must be prepared to be involved. The
application must be suitable and the prototype will go through several iterations. Problems include
the danger of sloppy work lacking any rigorous methodology, team boredom, prototype seen as
the end product.