Scribd
Upload
262 views

Waterfall Model

The document describes the waterfall model approach to software development. It is presented in phases: analysis, design, development, implementation, and testing. Each phase must be completed before moving to the next. The waterfall model is simple, easy to understand, and allows for clear documentation and oversight between stages. However, it is rigid and does not allow for adaptation to changing requirements. No working software is produced until late in the development cycle. The waterfall model works best for smaller, well-defined projects but is not suitable for complex or long-term projects with uncertain requirements.

Uploaded by

ilias ahmed
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
262 views

Waterfall Model

The document describes the waterfall model approach to software development. It is presented in phases: analysis, design, development, implementation, and testing. Each phase must be completed before moving to the next. The waterfall model is simple, easy to understand, and allows for clear documentation and oversight between stages. However, it is rigid and does not allow for adaptation to changing requirements. No working software is produced until late in the development cycle. The waterfall model works best for smaller, well-defined projects but is not suitable for complex or long-term projects with uncertain requirements.

Uploaded by

ilias ahmed
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 19

Peoples university of bangladesh

Presentation topics:
water model approach in software engineering
Waterfall Model
Group Members: all batch
Contents
Waterfall Model
Advantage
Disadvantage
Phases
Software Model Process
• This is a simplified description of a software process which is presented
from a particular viewpoint.
Waterfall Model Approach

• This approach takes the activities of the software


process and represents them as separate process phases
such ass requirements specification, software design,
implementation, testing and so on. Each stage is
depended on the completion of the previous stage.
• This model was introduced by Royce 1970.
The Waterfall Model was the first Process Model to be introduced. It is
also referred to as a linear sequential life cycle model. It is very simple to
understand and use. In a waterfall model, each phase must be completed
before the next phase can begin and there is no overlapping in the phases.
Waterfall model is the earliest System Development life cycle (SDLC)
approach that is used for software development .
Waterfall approach was the first SDLC Model to be used widely in
Software Engineering to ensure success of the project. In "The Waterfall"
approach, the whole process of software development is divided into
separate phases. In Waterfall model, typically, the outcome of one phase
acts as the input for the next phase sequentially
Advantages
• Simple and easy to understand and use
• Easy to manage due to the rigidity of the model.
• Each phase has specific deliverables and a review process.
• Phases are processed and completed one at a time.
• Works well for smaller projects where requirements are very well
understood.
Cont’d

• Clearly defined stages.


• Well understood milestones.
• Easy to arrange tasks.
• Process and results are well documented.
Disadvantages
• No working software is produced until late during the life cycle.
• High amounts of risk and uncertainty.
• Not a good model for complex and object-oriented projects.
• Poor model for long and ongoing projects.
• Not suitable for the projects where requirements are at a moderate to high
risk of changing. So risk and uncertainty is high with this process model.
• It is difficult to measure progress within stages.
• Cannot accommodate changing requirements.
• No working software is produced until late in the life cycle.
• Adjusting scope during the life cycle can end a project.
• Integration is done as a "big-bang. at the very end, which doesn't allow
identifying any technological or business bottle neck or challenges early.
Step of water model
Analysis Phase Testing Phase
Design Phase Evolution Phase
Development Phase
Implementation Phase
Analysis Phase
All possible requirements of the system to be
developed are captured in this phase and
documented in a requirement specification doc.
Design Phase
The requirement specifications from first phase are studied in
this phase and system design is prepared. System Design helps in
specifying hardware and system requirements and also helps in
defining overall system architecture
Development Phase
The process of creating software that meet the specification of the user(s). It is
the actual construction process after having a complete and illustrated design
for the requested system, the actual code is written here .
Implementation Phase

With inputs from system design, the system is first developed in small
programs called units, which are integrated in the next phase. Each unit is
developed and tested for its functionality which is referred to as Unit
Testing.
Testing Phase

All the units developed in the implementation phase are integrated into a
system after testing of each unit. Post integration the entire system is tested
for any faults and failures.
Evolution Phase
The software must evolve/change to meet changing end-user need. It must be
able to be upgraded or changed to meet some future needs. The software
system must evolve in line with the business and the prioritised requirement of
the requirements of the end-users.
Desgin by ilias ahmed

You might also like