Waterfall model

The waterfall model is a software development model first proposed in 1970 by W. W. Royce, in which development is seen as flowing steadily through the phases of requirements analysis, design, implementation, testing (validation), integration, and maintenance.

In the original article, Royce advocated using the model repeatedly, in an iterative way. However, most people do not know that and some have discredited it for use as a Real World process. In practice, the process rarely proceeds in a purely linear fashion. Iterations, by going back to or adapting results of the precedent stage, are common.

Contents

1 Advantages 2 Disadvantages 3 See also 4 References 5 External links

Advantages

• Good progress tracking due to clear development stages.
• Milestones and deliverables can be clearly identified.

Disadvantages

• Inflexible partitioning of the project into distinct stages makes it difficult to respond to changing customer requirements.

See also

• Project lifecycle
• Spiral model
• Chaos model
• Agile software development

References

External links

• Discussion on c2.com