Waterfall Model

(redirected from Waterfall process)

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].
This article is provided by FOLDOC - Free Online Dictionary of Computing (foldoc.org)
References in periodicals archive ?
"Today, you would typically approach a design challenge like this with 'the waterfall process'," he explains.
It was against this background that leading software developers started looking at more simplified ways to develop software than the sequenced methodology of the 'waterfall process' which, at the time, was the dominant approach.
Waterfall also assumes that timeframes and budgets are easy to predict in the beginning; many waterfall developments fall in quarterly timeframes for progress and outputs, which is not nearly the frequency needed for reviewing progress and alignment with customer needs, and soliciting customer feedback (which is the final step in a waterfall process, after the project is completed).
Because Agile breaks down the project development into key "stories" that are then prioritized, customer communications are significantly better than in a traditional waterfall process. Agile will produce the first demonstration deliverable within two to four weeks for the customer to evaluate, along with the opportunity to look at the remaining stories and priorities in the backlog that still need to be developed.
Traditional information technology acquisition follows a sequential, stovepiped waterfall process that results in a large amount of "work in progress" throughout the development effort and delays delivery of functionality to the end user until the end of the effort.
In more recent years, I have formalized software design within the Cynefin Framework--an approach that uses the power of waterfall process for ordered or structure environments, but starts to use methods such as social network stimulation, the subject of my previous column.
At least you can recognize catastrophic failure, whereas a lot of waterfall processes don't do us the favor of failing-they just produce something mediocre and deeply entrenched.
Uniquely for any of the guided manual test execution products that we know of, Original can automatically convert a manual TestDrive-Assist test into a fully automated TestDrive test that can be repeated." "Overall this is a low risk, low cost way of progressively adopting test automation." "It fits in with classic waterfall processes, and it can also be used in agile processes more easily than other functional test automation suites."