Scribd
Upload
13 views13 pages

Water Fall

The Waterfall Model is a linear and sequential approach to software development consisting of distinct phases: requirements analysis, design, implementation, testing, deployment, and maintenance. It provides a clear timeline and progression through the phases but is less adaptable to changing requirements with testing late in the process potentially leading to costly defects. The Waterfall Model is best for projects with stable requirements, short timelines, and high documentation and quality standards.

Uploaded by

Vk
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
13 views13 pages

Water Fall

The Waterfall Model is a linear and sequential approach to software development consisting of distinct phases: requirements analysis, design, implementation, testing, deployment, and maintenance. It provides a clear timeline and progression through the phases but is less adaptable to changing requirements with testing late in the process potentially leading to costly defects. The Waterfall Model is best for projects with stable requirements, short timelines, and high documentation and quality standards.

Uploaded by

Vk
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
You are on page 1/ 13

WATERFALL

MODEL
2

INTRODUCTION
• The Waterfall Model is a linear and sequential approach to
software development, where progress flows in one
direction, like a waterfall, through distinct phases, each
dependent on the deliverables of the previous one.
• The model was first introduced by Dr. Winston W. Royce in
1970 in a paper titled "Managing the Development of Large
Software Systems.
STAGES

​Deployment
Testing
​Implementation

Design

Requirement Analysis
REQUIREMENTS
ANALYSIS
This stage focuses on thoroughly understanding and documenting the
project's requirements. It involves:
• Meeting with stakeholders.
• Defining functional and non-functional requirements.
• Documenting use cases and user stories.

Importance of Clear Requirements: Clear and comprehensive


requirements are essential for the success of the project as they serve as
a foundation for design and development.
DESIGN
In this stage, the high-level architecture and detailed component design
are created. It involves:
• Defining system architecture.
• Designing modules and components.
• Specifying interfaces and data structures

Role of Design Documentation: Design documentation helps ensure


that the software is developed according to the defined architecture and
design.
IMPLEMENTATION
This stage involves writing code based on the design specifications.
Activities include:
• Writing and testing code.
• Conducting unit testing.
• Integrating components.

Importance of Adhering to Design: Developers must adhere to the


design to ensure that the final product aligns with the initial vision.
TESTING
This stage involves testing of the product created.
Different types of testing are conducted, including:
• Unit testing (testing individual components).
• Integration testing (testing interactions between components).
• System testing (testing the complete system).
• User acceptance testing (ensuring it meets user needs).

Importance of Quality Assurance: Testing is a critical phase for quality


assurance, identifying and fixing defects.
DEPLOYMENT
The software is prepared for production release, involving:
• Delivery of product
• Installation and configuration.
• Data migration if necessary.
MAINTENANCE
This is a Post-Deployment Phase. After release, maintenance becomes essential,
including:
• Corrective maintenance (bug fixes).
• Adaptive maintenance (updates for changing requirements).
• Perfective maintenance (enhancements).
• Preventive maintenance (proactive updates).

Ongoing Support: Maintenance ensures the software remains reliable and


meets evolving needs.
ADVANTAGES
• Usage: Simple and easy to understand and use
• Predictable Timeline: The Waterfall Model provides a clear
project timeline and progression.
• Documentation: Thorough documentation helps in
understanding and maintaining the software.
• Well-Suited for Stable Requirements: Ideal for projects with
stable and well-defined requirements, such as regulatory
compliance software.
DISADVANTAGES
• Inflexibility: The model is less adaptable to changing
requirements.
• Late Testing: Testing occurs late in the process, potentially
leading to costly defect discovery.
• Risk: High amounts of risk and uncertainty.
• Usability: Not a good model for complex and long projects
WHEN TO USE
Waterfall is suitable for projects with:
• Stable and well-understood requirements.
• Product definition is stable.
• High documentation and quality standards.
• There are no ambiguous requirements.
• The project is short.
THANK YOU

You might also like