Waterfall model

From Citizendium
Jump to navigation Jump to search
The printable version is no longer supported and may have rendering errors. Please update your browser bookmarks and please use the default browser print function instead.
This article is a stub and thus not approved.
Main Article
Discussion
Related Articles  [?]
Bibliography  [?]
External Links  [?]
Citable Version  [?]
 
This editable Main Article is under development and subject to a disclaimer.

The Waterfall model is classical approach to solving engineering problems (most commonly known as an approach to software engineering). It employs a sequential series of activity phases culminating in a single release milestone.

In a typical software life cycle, following the waterfall model produces the following phases and activities:

  • Requirements collection and analysis
  • Software Architecture - design analysis and development
  • Preliminary code development and in-house unit testing
  • Release candidate code development (culminating in a "feature complete" internal release)
  • Alpha Phase: System level and integration testing
  • Beta phase: Qualified external users test the pre-release software
  • Public Release
  • Maintenance / "bug" fixes