Difference between revisions of "Waterfall model"
(→Related lectures) |
|||
| (5 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
| − | The [[Waterfall model]] (alternatively known as [[Waterfall methodology]] or [[Waterfall method]]; hereinafter, the ''Model'') is a sequential design process where progress is seen as flowing steadily downwards through the phases. These ''phases'' vary from one model to another:<blockquote><table class="wikitable" width=100% style="text-align:center;"><tr><th rowspan="3">[[Waterfall model]]</th><td>'''Initial''' (by Winston W. Royce)</td><td colspan="2">'''Requirements''' (system and software), captured in a product requirements document</td><td>'''Analysis''', resulting in models, schema, and business rules</td><td>'''Design''', resulting in the software architecture</td><td>'''Coding''': the development, proving, and integration of software</td><td>'''Testing''', resulting in the systematic discovery</td><td colspan="3">Debugging of defects and '''operations''': the installation, migration, support, and maintenance of complete systems</td></tr><tr><td>'''DOD'''-STD-2167A</td><td colspan="3">'''Preliminary''' Design</td><td>Detailed '''Design'''</td><td>'''Coding'''</td><td>Unit '''Testing'''</td><td colspan="3">'''Integration''' and further testing</td></tr><tr><td>'''Classic'''</td><td>'''Conception'''</td><td>'''Initiation'''</td><td>'''Analysis'''</td><td>'''Design'''</td><td>'''Construction'''</td><td>'''Testing'''</td><td colspan="3">'''Deployment''' and maintenance</td></tr><tr><td rowspan="2" style="background-color:#fff;">'''[[ | + | The [[Waterfall model]] (alternatively known as [[Waterfall methodology]] or [[Waterfall method]]; hereinafter, the ''Model'') is a sequential design process where progress is seen as flowing steadily downwards through the phases. These ''phases'' vary from one model to another:<blockquote><table class="wikitable" width=100% style="text-align:center;"><tr><th rowspan="3">[[Waterfall model]]</th><td>'''Initial''' (by Winston W. Royce)</td><td colspan="2">'''Requirements''' (system and software), captured in a product requirements document</td><td>'''Analysis''', resulting in models, schema, and business rules</td><td>'''Design''', resulting in the software architecture</td><td>'''Coding''': the development, proving, and integration of software</td><td>'''Testing''', resulting in the systematic discovery</td><td colspan="3">Debugging of defects and '''operations''': the installation, migration, support, and maintenance of complete systems</td></tr><tr><td>'''DOD'''-STD-2167A</td><td colspan="3">'''Preliminary''' Design</td><td>Detailed '''Design'''</td><td>'''Coding'''</td><td>Unit '''Testing'''</td><td colspan="3">'''Integration''' and further testing</td></tr><tr><td>'''Classic'''</td><td>'''Conception'''</td><td>'''Initiation'''</td><td>'''Analysis'''</td><td>'''Design'''</td><td>'''Construction'''</td><td>'''Testing'''</td><td colspan="3">'''Deployment''' and maintenance</td></tr><tr><td rowspan="2" style="background-color:#fff;">'''[[DREPD]]'''</td><td style="background-color:#fff;">[[Deductive DREPD|Deductive DREPD]]</td><th colspan="2">[[Enterprise discovery|'''D'''iscover]]</th><th>[[Enterprise research|'''R'''esearch]]</th><th>[[Enterprise envisioning|'''E'''nvision]]</th><th>[[Enterprise planning|'''P'''lan]]</th><td colspan="4" style="background-color:#fff;"> </td></tr><tr><td style="background-color:#fff;">[[Inductive DREPD|Inductive DREPD]]</td><td colspan="5" style="background-color:#fff;"> </td><th>[[Enterprise discovery|'''D'''iscover]]</th><th>[[Enterprise research|'''R'''research]]</th><th>[[Enterprise envisioning|'''E'''nvision]]</th><th>[[Enterprise planning|'''P'''lan]]</th></tr></table></blockquote>[[File:Waterfall.png|400px|thumb|right|[[Waterfall model]]]] |
| + | |||
| + | ==Definitions== | ||
| + | According to the [[ITIL Foundation 4e by Axelos]], | ||
| + | :'''[[Waterfall method]]'''. A development approach that is linear and sequential with distinct objectives for each phase of development. | ||
==Related lectures== | ==Related lectures== | ||
*[[Project Management Quarter]]. | *[[Project Management Quarter]]. | ||
| − | [[Category: Septem Artes Administrativi]][[Category: Articles]] | + | [[Category: Septem Artes Administrativi]][[Category: Articles]][[Category: Information Technology]] |
Latest revision as of 18:25, 11 December 2020
The Waterfall model (alternatively known as Waterfall methodology or Waterfall method; hereinafter, the Model) is a sequential design process where progress is seen as flowing steadily downwards through the phases. These phases vary from one model to another:
Waterfall model Initial (by Winston W. Royce) Requirements (system and software), captured in a product requirements document Analysis, resulting in models, schema, and business rules Design, resulting in the software architecture Coding: the development, proving, and integration of software Testing, resulting in the systematic discovery Debugging of defects and operations: the installation, migration, support, and maintenance of complete systems DOD-STD-2167A Preliminary Design Detailed Design Coding Unit Testing Integration and further testing Classic Conception Initiation Analysis Design Construction Testing Deployment and maintenance DREPD Deductive DREPD Discover Research Envision Plan Inductive DREPD Discover Rresearch Envision Plan
Definitions
According to the ITIL Foundation 4e by Axelos,
- Waterfall method. A development approach that is linear and sequential with distinct objectives for each phase of development.
