waterfall model

The waterfall model is a popular version of the systems development life cycle model for software engineering. Often considered the classic approach to the systems development life cycle, the waterfall model describes a development method that is linear and sequential. Waterfall development has distinct goals for each phase of development. Imagine a waterfall on the cliff of a steep mountain. Once the water has flowed over the edge of the cliff and has begun its journey down the side of the mountain, it cannot turn back. It is the same with waterfall development. Once a phase of development is completed, the development proceeds to the next phase and there is no turning back.

The advantage of waterfall development is that it allows for departmentalization and managerial control. A schedule can be set with deadlines for each stage of development and a product can proceed through the development process like a car in a carwash, and theoretically, be delivered on time. Development moves from concept, through design, implementation, testing, installation, troubleshooting, and ends up at operation and maintenance. Each phase of development proceeds in strict order, without any overlapping or iterative steps.

The disadvantage of waterfall development is that it does not allow for much reflection or revision. Once an application is in the testing stage, it is very difficult to go back and change something that was not well-thought out in the concept stage. Alternatives to the waterfall model include joint application development (JAD), rapid application development (RAD), synch and stabilize, build and fix, and the spiral model.

Do you have something to add to this definition? Let us know. Send your comments to techterms@whatis.com

Digg This!     StumbleUpon     Del.icio.us

RELATED CONTENT Software development groups take many routes to Agile More software development groups are implementing Agile methodologies, but their routes to adoption are far from straight and narrow and vary from... Survey: Agile interest high, but waterfall still used by many While there's a strong interest in new software development techniques, SearchSoftwareQuality.com's recent survey found that many still follow... Ivar Jacobson: Useful app dev practices trump full-blown processes Ivar Jacobson, the father of use cases and a founder of UML, advocates adopting useful software development practices over full-blown processes such...

RELATED GLOSSARY TERMS Terms from Whatis.com − the technology online dictionary Capability Maturity Model  (SearchSoftwareQuality.com) collaboration diagram  (SearchSoftwareQuality.com) A collaboration diagram, also called a communication diagram or interaction diagram, is an illustration of the relationships and interactions among...