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.

Getting started with the waterfall model

To explore how the waterfall model is used in the enterprise, here are some additional resources:

Varying SDLC methodologies among development teams: Varying SDLC methodologies among development teams

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 Best practices for moving testers from waterfall to agile development Software testers moving from a waterfall environment to the agile development model don't have to be driven to the head-banging stage of frustration. Agile and waterfall neck and neck as business side fails to engage In this interview, Jon Kern discusses the disconnect between business and development leaders, why agile requires top-notch developers and why... Turning agile skeptics to believers at Blueprint Systems Blueprint's CTO was skeptical about the powers of agile, especially when it came to distributed teams, but now he's made believers of the whole...

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...