Waterfall model: Difference between revisions
Jump to navigation
Jump to search
imported>Joe Quick m (subpages) |
mNo edit summary |
||
Line 12: | Line 12: | ||
* Public Release | * Public Release | ||
* Maintenance / "bug" fixes | * Maintenance / "bug" fixes | ||
[[Category:Suggestion Bot Tag]] |
Latest revision as of 07:00, 7 November 2024
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