0% found this document useful (0 votes)
17 views9 pages

Waterfall Model

The Waterfall Model is a linear sequential software development process where each phase must be completed before the next begins. It is best suited for projects with well-known and stable requirements, but has limitations such as being only suitable for small projects and difficulty in handling changing requirements. While it offers advantages like ease of implementation and early error detection, it also presents risks and uncertainties in time and cost estimation.

Uploaded by

saumyan26
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
17 views9 pages

Waterfall Model

The Waterfall Model is a linear sequential software development process where each phase must be completed before the next begins. It is best suited for projects with well-known and stable requirements, but has limitations such as being only suitable for small projects and difficulty in handling changing requirements. While it offers advantages like ease of implementation and early error detection, it also presents risks and uncertainties in time and cost estimation.

Uploaded by

saumyan26
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 9

eopics

=
v"What is Waterfall Model.
v History
v"Where to use
v Diagram
v Advantages
v Disadvantages
Waterfall Model
» It is also called as linear sequential model.
» It was the first Process Model.
»In this model whole application is developed in a
sequential approach.
»It is very simple to understand and use.
»In this model each phase must be completed fully
before the next phase begin.
»Provides structure to inexperienced staff.
History
> The first formal description of the waterfall
model is often cited as a 1970 article by Winston
W .Royee.
»Royee presented this model as an example of a
flawed, none-working model.
»It has been widely used for software projects
ever since.
Where to use
» This SDLC model is used where requirements are
very well known.
> Where definition is stable.
» This SDLC model is used where the technology
are understood for the project.
» And where new version of an existing product.
~Waterfall Model Diagram
=1
Requirements i

Coding

Testing

Acceptance
"In this phase business analyst will collect the |
' Requirement
' requirements with an interaction of client and
¢ Gathering
collected requirements will be documented.
; E In this phase system analyst will study the client
' Requirement : .
: requirements and prepare the system requirement
.L~ Analysis e s
specification.
In this phase design architecture is the responsible
to decide architecture of an application in order to
full-fill the client requirements.
In this phase developers will write the program
using programming languages or scripting languages
in order to develop the application.

L Initially developers will perform unit testing &


g integration testing using of white box testing.

BRelcase &8 After the testing the client satisfied on work


product the n we del ive r app lic ati on to the cus tom er
S intenant
to use at live environment..
Advantages
» A waterfall model is easy to implement.
» It helps to find errors earlier.
» Easy to understand, and easy to use.
» Testing is done at every stage.
»Works well when quality is more important than
cost or schedule.
» Documentation is produced at every stage of a
waterfall model allowing people to understand
what has been doen.
Disadvantages
»TIt is only suitable for the small size projects.
» Constant testing of the design is needed.
»If requirements may change the waterfall model
may not work.
»Adjust scope during the life cycle can kill a
project.
» Difficult to estimate time and cost for each stage
of the development process.
»High amount risk and uncertainty.
» This is not suitable to handle dynamic changes in
the requirements.
e
P

Thank Youl

You might also like