Modified waterfall models

From Wikipedia, the free encyclopedia
Jump to: navigation, search

In response to the perceived problems with the "pure" waterfall model, many modified waterfall models have been introduced. These models may address some or all of the criticisms of the "pure" waterfall model.

These include the Rapid Development models that Steve McConnell calls "modified waterfalls" [1] (see especially p. 143-147): Peter DeGrace's "sashimi model" (waterfall with overlapping phases), waterfall with subprojects, and waterfall with risk reduction. Other software development model combinations such as "incremental waterfall model" also exist [2]

Royce's Final Model[edit]

Winston W. Royce's final model, his intended improvement upon his initial "waterfall model", illustrated that feedback could (should, and often would) lead from code testing to design (as testing of code uncovered flaws in the design) and from design back to requirements specification (as design problems may necessitate the removal of conflicting or otherwise unsatisfiable / undesignable requirements). In the same paper Royce also advocated large quantities of documentation, doing the job "twice if possible" (a sentiment similar to that of Fred Brooks, famous for writing the Mythical Man Month, an influential book in software project management, who advocated planning to "throw one away"), and involving the customer as much as possible (a sentiment similar to that of Extreme Programming).

See also[edit]

References[edit]

  • Boehm, Barry W., 1988, "A Spiral Model of Software Development and Enhancement". Computer, May: p. 61-72.
  • DeGrace, Peter, and Stahl, Leslie Hulet, 1990, Wicked Problems, Righteous Solutions: A Catalogue of Modern Software Engineering Paradigms, Prentice-Hall, 244 pages. ISBN 0-13-590126-X
  • Humphrey, Watts S., 1989, Managing the Software Process, Addison-Wesley, 494 pages. ISBN 0-201-18095-2
  • McConnell, Steve, 1996, Rapid Development: Taming Wild Software Schedules, Microsoft Press, 660 pages. ISBN 1-55615-900-5
  1. ^ McConnell, Steve (1996). Rapid Development: Taming Wild Software Schedules. Microsoft Press. ISBN 1556159005. 
  2. ^ Methodology "Methodology:design methods".