waterfallmodel.docVIP

Waterfall model From Wikipedia, the free encyclopedia Jump to: navigation, search Software development process Activities and steps Requirements?· ArchitectureDesign?· ImplementationTesting?· Deployment Models Agile?· Cleanroom?· Iterative?· RADRUP?· Spiral?· Waterfall?· XP?· Scrum Supporting disciplines Configuration managementDocumentationQuality assurance (SQA)Project managementUser experience design The waterfall model is a sequential software development model (a process for the creation of software) in which development is seen as flowing steadily downwards (like a waterfall) through the phases of requirements analysis, design, implementation, testing (validation), integration, and maintenance. The origin of the term waterfall is often cited to be an article published in 1970 by Winston W. Royce (1929–1995),[1] although Royce did not use the term waterfall in this article. Ironically, Royce was presenting this model as an example of a flawed, non-working model (Royce 1970). Contents [hide] 1 History of the waterfall model 2 The model 3 Usage 4 Arguments for the Waterfall Model 5 Criticism of the Waterfall Model 6 Modified Waterfall Models 6.1 The Sashimi Model 7 See Also 8 References 9 External links [edit] History of the waterfall model In 1970 Royce proposed what is presently referred to as the waterfall model as an initial concept, a model which he argued was flawed (Royce 1970). His paper explored how the initial model could be developed into an iterative model, with feedback from each phase influencing subsequent phases. It is only the initial model that received notice; his own criticism of this initial model has been largely ignored. The phrase waterfall model quickly came to refer not to Royces final, iterative design, but rather to his purely sequentially ordered model. This article uses the popular meaning of the phrase waterfall model. For an iterative model similar to Royces final vision, see the spiral model. Despite Royce