Software development process: Difference between revisions

Revision as of 10:06, 11 July 2025

Revision as of 10:40, 11 July 2025

Line 162:

* Tight control is maintained over the life of the project via extensive written documentation, formal reviews, and approval/signoff by the user and [[information technology management]] occurring at the end of most phases before beginning the next phase. Written documentation is an explicit deliverable of each phase.

The waterfall model is a traditional engineering approach applied to software engineering. A strict waterfall approach discourages revisiting and revising any prior phase once it is complete, according to industry experts<ref>{{Cite web |title=CISSP and CCSP Resources |url=https://infosectests.com/}}</ref> {{says who?|date=January 2021}} This "inflexibility" in a pure waterfall model has been a source of criticism by supporters of other more "flexible" models. It has been widely blamed for several large-scale government projects running over budget, over time and sometimes failing to deliver on requirements due to the [[big design up front]] approach.{{says who?|date=January 2021}} Except when contractually required, the waterfall model has been largely superseded by more flexible and versatile methodologies developed specifically for software development.{{says who?|date=January 2021}} See [[Waterfall model#Criticism|Criticism of waterfall model]].

=== Spiral development ===