Waterfall Model

Also found in: Wikipedia.

Waterfall Model

A software life-cycle or product life-cycle model, described by W. W. Royce in 1970, in which development is supposed to proceed linearly through the phases of requirements analysis, design, implementation, testing (validation), integration and maintenance. The Waterfall Model is considered old-fashioned or simplistic by proponents of object-oriented design which often uses the spiral model instead.

Earlier phases are sometimes called "upstream" and later ones "downstream".

Compare: iterative model.

[W. W. Royce, "Managing the Development of Large Software Systems", Proceedings of IEEE WESCON, August 1970].
References in periodicals archive ?
Whether it is a system admin learning to build new tools, or developers using a model other than the Waterfall model, DevOps firmly places your organisation in the growth zone.
These must be concluded agreements within the waterfall model or a more agile development form - depending on what suits the tasks.
In a traditional waterfall model, development is closely watched and follows a very well-defined set of documentation (business analysis creates requirements, which begets design documentation from development and test plans from quality assurance), and the model runs for the most part sequentially.
Even though based on the total sample, waterfall model emerged as most used, the successful projects under this situation more resorted to the iterative-incremental model.
A major challenge with the waterfall model is the assumption that you truly know all the requirements and all the points of dissatisfaction with the current state.
obtained a better letter grade for the course, compared to the students who did not do so, but instead used the traditional waterfall model.
30 and described the Waterfall Model (Figure 2) as a tool to illustrate the design control process.
The Spiral model has elements of both the waterfall model and the prototyping model, generally for large projects.
Unlike the waterfall model, the agile approach promotes iterative cycles of development.
It's faster and more responsive than the traditional waterfall model, which takes a purely sequential approach to creating software.
This guide describes the application of Six Sigma concepts to various aspects of the system development process, including the waterfall model, legacy systems, and recent innovations like rapid application development, packaged software implementation, and outsourcing.
Critics say the traditional waterfall model is often too slow and therefore obsolete for the high-paced Internet era.