TRADITIONAL SOFTWARE DEVELOPMENT PROCESSES - Software Design for Six-Sigma: A Roadmap for Excellence - page 47

TABLE 2.1 Classification Based on the Suitability of Size and Complexity of Project

Software
Process Simple and Small Moderate and Medium Complex and Large

Waterfall
Model

1. It allows for
departmentalization and
managerial control.
2. A schedule can be set with
deadlines for each stage of
development, and a product
can proceed through the
development process and,
theoretically, be delivered
on time.
3. 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.
4. For Simple, Static/Frozen
requirements and Small
Project. These methods
might prove effective and
cheaper.
5. The disadvantage of
Waterfall development is
that it does not allow for
much reflection or revision.
6. 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.
7. Classic Waterfall
methodology usually breaks
down and results in a failure
to deliver the needed
product for complex and
continuously changing
requirements.

Sashimi
Model

Chaos
Model

( Continued )