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 ?
Traditionally in the early 2000s, in the waterfall model, QA was always seen as a subsequent phase to development, often referred to playfully, as the dishwashing stage of the SDLC.
Developmental should be able to be delivered both by agile principles and by waterfall model.
This course of haemostatic events has been explained by developing theories to elucidate all interactions between platelets, coagulation factors via the waterfall model, cofactors without enzymatic activity, antithrombotic mechanisms, and so on.
Some of these were the Iterative model, Waterfall model, Sashimi model, Spiral model, Fish Bone or Ishikawa Diagram, and Prototyping.
Although many models have been presented at the beginning of the waterfall model [7].
For the purpose of automation of assessment of classification type answers, a classification models namely waterfall model is proposed.
The first formal description of the Waterfall model is described by Royce in 1970 [2].
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.
It has its roots in the world of software development, where the software project management community got weary with the inefficiencies and theocracy of the Waterfall Model, which presupposes a fixed, unchanging scope, monolithic development and, finally, one-shot user acceptance testing, where it's inevitable that there be rejects, negotiations, leading to a badly compromised product being shipped out into the marketplace.
The Waterfall model is the most applied model in the field because of its versatility and clarity.
Martinez says computer science is still taught using the waterfall model, a programming approach that dates to the punch-card era.
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.