Scribd
Upload
117 views

Software Process Models: Waterfall Model

The document discusses software process models and the waterfall model. It provides an overview of the waterfall model, describing it as the first process model introduced and as a linear-sequential life cycle model. The key phases of the waterfall model are presented as requirements, design, implementation, testing, and maintenance. Advantages include its simplicity and structure, while disadvantages include inability to accommodate changing requirements and lack of working software until late stages. It is best suited for projects with well-defined requirements unlikely to change radically.

Uploaded by

myint phyo
Copyright
© © All Rights Reserved
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
117 views

Software Process Models: Waterfall Model

The document discusses software process models and the waterfall model. It provides an overview of the waterfall model, describing it as the first process model introduced and as a linear-sequential life cycle model. The key phases of the waterfall model are presented as requirements, design, implementation, testing, and maintenance. Advantages include its simplicity and structure, while disadvantages include inability to accommodate changing requirements and lack of working software until late stages. It is best suited for projects with well-defined requirements unlikely to change radically.

Uploaded by

myint phyo
Copyright
© © All Rights Reserved
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
You are on page 1/ 12

Software Process Models

Waterfall Model
Group 4
Software Process

A software process (also knows as software methodology) is a set of


related activities that leads to the production of the software. These
activities may involve the development of the software from the
scratch, or, modifying an existing system.

Thet Htar Swe


Software Process Models

- a simplified representation of a software process.


• Each model represents a process from a specific
perspective.
• These models are abstractions of the process that can
be used to explain different approaches to the software
development.
• They can be adapted and extended to create more
specific processes.
Thet Htar Swe
Waterfall Model
• The Waterfall Model was the first Process Model to be
introduced.
• referred to as a linear-sequential life cycle model.
• very simple to understand and use.
• In a waterfall model, any phase in the development
process begins only if the previous phase is complete and
there is no overlapping in the phases.
Khine Thazin Aung
Waterfall Model - Design

The different phases of the Waterfall Model-

Khine Thazin Aung


The Nature of Waterfall Phases
• the next phase shouldn’t be started until the previous
phase has completely been finished.
• In practice, however, these phases overlap and feed
information to each other.
• The software process therefore is not a simple linear but
involves feedback from one phase to another.

Myint Myat Phyo


Waterfall
Waterfall Model
Model -- Application
Application

Every software developed is different and requires a suitable


SDLC approach to be followed based on the internal and
external factors. Some situations where the use of Waterfall
model is most appropriate are −

• Requirements are very well documented, clear and fixed.


• Product definition is stable.
• Technology is understood and is not dynamic.
• There are no ambiguous requirements.
• The project is short.
Myint Myat Phyo
Example use of Waterfall Model
Kyaw Nyi Nyi Han

• Development of Department Of Defense (DOD), military


and aircraft programs followed Waterfall model in many
organizations.
• This is because of the strict standards and requirements
that have to be followed.
• In such industries, the requirements are known well in
advance and contracts are very specific about the
deliverable of the project.
• Waterfall model was also used in banking, healthcare,
control system for nuclear facilities, space shuttles etc
Waterfall Model - Advantages
Khine Yin Win
Some of the major advantages of the Waterfall Model are as follows −
• 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.
• Clearly defined stages.
• Well understood milestones.
• Easy to arrange tasks.
• Process and results are well documented.
Waterfall Model - Disadvantages
Khin Yadanar Aung
The major disadvantages of the Waterfall Model are as follows −
• 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.
• It is difficult to measure progress within stages.
• Cannot accommodate changing requirements.
• Adjusting scope during the life cycle can end a project.
When To Use?
The waterfall model should only be applied
• when requirements are well understood
• unlikely to change radically during development
(as this model has a relatively rigid structure which makes
it relatively hard to accommodate change when the process
in underway.)

Thi Han Zay Ya


Summary
Waterfall
• It’s useful when the requirements are clear, or following a
very structured process as in critical systems which needs
a detailed, precise, and accurate documents describes
the system to be produced.
• Not good when requirements are ambiguous, and doesn’t
support frequent interaction with the customers for
feedback and proposing changes. It’s not suitable for
large projects that might take long time to be developed
and delivered.
Thi Han Zay Ya

You might also like