Difference between revisions of "Waterfall model"
From Wiki @ Karl Jones dot com
Karl Jones (Talk | contribs) |
Karl Jones (Talk | contribs) (→External Links) |
||
| Line 32: | Line 32: | ||
* [http://en.wikipedia.org/wiki/Waterfall_model Waterfall model] @ Wikipedia | * [http://en.wikipedia.org/wiki/Waterfall_model Waterfall model] @ Wikipedia | ||
| + | |||
| + | |||
| + | [[Category:Computer programming]] | ||
| + | [[Category:Computing]] | ||
| + | [[Category:Software]] | ||
| + | [[Category:Software development]] | ||
| + | [[Category:Web design and development]] | ||
Latest revision as of 06:45, 26 April 2016
The waterfall model is a sequential design process, used in software development processes, in which progress is seen as flowing steadily downwards (like a waterfall) through a series of phases (stages).
Phases
Phases of the waterfall mode:
- Conception
- Initiation
- Analysis
- Design
- Construction
- Testing
- Production/implementation
- Maintenance.
Origin
The waterfall development model originates in the manufacturing and construction industries: highly structured physical environments in which after-the-fact changes are prohibitively costly, if not impossible.
Since no formal software development methodologies existed at the time, this hardware-oriented model was simply adapted for software development.
Agile software development
Agile software development is intended to improve upon the Waterfall model.
See also
External Links
- Waterfall model @ Wikipedia
