• It is a linear model and linear models are the most simple to be implemented.

• Documentation is produced at every stage of the waterfall model development.

Disadvantages of Waterfall Model

• It is often very difficult for the customer to state all requirements explicitly.
• The customers must have patience. A working product will not be available until late in
the project timespan. A major blunder, if undetected until the working program is
reviewed, can be disastrous.
• Once an application is in the testing stage, it is very difficult to go back and change
something that was not well-thought out in the previous stage.
• Limited user involvement.
• System requirements are locked in after being determined.

Prototyping Model
It is very difficult for end users to anticipate how they will use new software systems to
support their work. If the system is large and complex, it is probably impossible to make
this assessment before the system is built and put into use.
A prototype (a small version of the system) can be used to clear the vague
requirements. A prototype should be evaluated with the user participation.
The prototyping paradigm begins with communication. You meet with other
stakeholders to define overall objectives for the software, identify whatever
requirements are known. Prototype iteration is planned quickly, and modelling occurs. A
quick design focuses on a representation of those aspects of the software that will be
visible to end users.
The quick design leads to the construction of a prototype. The prototype is deployed
and evaluated by stakeholders, who provide feedback that is used to further refine
requirements. Iteration occurs as the prototype is tuned to satisfy the needs of various
stakeholders, while at the same time enabling you to better understand what needs to
be done.

Advantages of Prototyping Model

- Effort of prototype is not wasted.
- Increase in speed of delivery of the prototype.