Scribd
Upload
48 views3 pages

Overview of the Waterfall Model

The Waterfall Model is a structured software development approach that involves distinct phases: Requirements, Design, Implementation. Its strengths include ease of understanding, clear milestones, and stability in requirements, making it suitable for projects where quality is prioritized. However, it has significant deficiencies such as the need for all requirements to be known upfront, lack of flexibility, and limited customer involvement until the end of the process.

Uploaded by

gaurav.shramaji
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
48 views3 pages

Overview of the Waterfall Model

The Waterfall Model is a structured software development approach that involves distinct phases: Requirements, Design, Implementation. Its strengths include ease of understanding, clear milestones, and stability in requirements, making it suitable for projects where quality is prioritized. However, it has significant deficiencies such as the need for all requirements to be known upfront, lack of flexibility, and limited customer involvement until the end of the process.

Uploaded by

gaurav.shramaji
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd

WATERFALL MODEL

• Requirements – defines needed


information, function, behavior,
performance and interfaces.
• Design – data structures, software
architecture, interface
representations, algorithmic
details.
• Implementation – source code,
database, user documentation,
testing.
WATERFALL STRENGTHS
• Easy to understand, easy to use
• Provides structure to inexperienced staff
• Milestones are well understood
• Sets requirements stability
• Good for management control (plan, staff, track)
• Works well when quality is more important than cost or schedule
WATERFALL DEFICIENCIES

• All requirements must be known upfront


• Deliverables created for each phase are considered frozen – inhibits flexibility
• Can give a false impression of progress
• Does not reflect problem-solving nature of software development – iterations of
phases
• Integration is one big bang at the end
• Little opportunity for customer to preview the system (until it may be too late)

You might also like