5. Strengths of Waterfall Model
Easy to understand, easy to use
Systematic for inexperienced staff
Milestones are well understood
6. Strengths of Waterfall Model
Sets requirements stability
Good for management control
(plan, staff, monitor, control)
Works well when quality is more
important than cost or schedule
7. Limitations-Waterfall Model
Every phase is considered as a distinct
phase
All requirements must be known before
hand
Deliverables created for each phase are
considered frozen – reduces flexibility
8. Limitations-Waterfall Model
Can give a false impression of progress
Little opportunity for customer to
preview the system (until it may be too
late)
9. Limitations-Waterfall Model
For a new system determining requirements is
a difficult job
So freezing requirements before design is not
practical
Might be desirable to built only a part of it
Later enhance as and when needed
11. Limitations-Waterfall Model
Difficulty of accommodating change
after the process is underway
One phase has to be complete before
moving onto the next phase
Integration is one big bang at the end
12. Limitations-Waterfall Model
Inflexible partitioning of the project into
distinct stages makes it difficult to change as
per customer requirements.
Requirements should be well-understood so
that changes are fairly limited during the
design process