The Waterfall Model is a life-cycle model applied to
the project management ans systems engineering of a product. While
the various stages are seen as sequential steps in the
waterfall, the model does allow for iteration. However, the Waterfall
Model is most often implemented so that each phase
must be completed before the next begins For example, the
development team can go on to system design only when
all of the requirements have been elicited from the customer,
analysed for completeness and consistency, and documented in a requirements
document. The Waterfall Model is formalised in DOD-STD-2167A. The
Waterfall Model, also called the Linear Sequential Model, has
a number of well known problems: its sequential nature is
restrictive since real projects are rarely sequential; it limits user
input since the user does not see working versions of
product until late in the project (this is particularly bad
in software-based projects); the model requires well-defined, well-understood requirements that
must be completely and explicitly stated before the project begins;
progress can be deceptive; and the linear nature of the
model can cause delays since dependent tasks can not be
started until prior tasks are completed. Modern life-cycle models for
software-based projects allow more iterative of incremental development.
Other topics in our resources on Project Management related to Waterfall Model include: