Waterfall model: Difference between revisions
Jump to navigation
Jump to search
imported>Mark Jones (Stub created from content moved from the "Software Engineering" article. Please modify, add, improve!) |
imported>Joe Quick m (subpages) |
||
| (One intermediate revision by one other user not shown) | |||
| Line 1: | Line 1: | ||
{{subpages}} | |||
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. | 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 life cycle following the waterfall model | In a typical software life cycle, following the waterfall model produces the following phases and activities: | ||
* Requirements collection and analysis | * Requirements collection and analysis | ||
Latest revision as of 18:28, 20 December 2007
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