WATERFALL MODEL
Key Characteristics:
1. Linear Sequential Process : The Waterfall Model follows
a step-by-step, sequential approach where each phase
must be completed before the next begins.
2. Phases : It consists of specific phases: Requirements,
Design, Implementation, Testing, Deployment, and
Maintenance.
3. No Overlap : Phases do not overlap; each phase is
distinct and must be fully completed before moving on to
the next.
Pros:
4. Easy to Understand : Simple to implement, making it
ideal for teams with limited experience in software
development methodologies.
5. Well-Defined Milestones : Clear milestones and
deliverables for each phase help in tracking progress.
6. Structured Approach : Offers a rigid structure, beneficial
for projects where requirements are clear from the
beginning.
7. Ideal for Documentation : Heavy reliance on
documentation makes it easier to onboard new team
members and provides a reference for future
maintenance.
8. Quality Assurance : Testing is done at the end of the
development, ensuring a fully integrated system before
release.
9. Predictable : Provides clear project timelines and cost
estimates, which is advantageous for fixed-budget
projects.
Cons:
10. Inflexible to Changes : Difficult to accommodate
changes once a phase is completed, making it unsuitable
for projects with evolving requirements.
11. Late Testing : Testing only after development can
result in discovering critical issues late, leading to
expensive fixes.
12. Higher Risk of Failure : Incorrect requirements
gathered early on can lead to project failure since changes
are costly to implement.
13. Limited Client Interaction : Minimal client
involvement throughout the process, which may result in a
final product that doesn’t fully meet client expectations.
14. Not Suitable for Complex Projects : Struggles
with complex or long-term projects where requirements
might change over time.
15. Resource-Intensive : Requires experienced resources
for each phase, and managing the phases independently
can increase project overhead
