WATER FALL MODEL
Introduction:
A software development process or life cycle is a structure imposed
on the software product.
There are several models for such processes, each describing
approaches to a variety of taks or activities that take place during
the process.
They are: waterfall model,spiral model,iterative model, v model etc
7 models.
What is waterfall model?
Waterfall model is the popular model of the sytem development life
cycle.
It is also called as linear sequential model.
It was the first process model.
In this model whole application is developed in a sequential model.
It is very simple to understand and use.
In this model each phase must be completed fully before the phase
starts.
Provides structure to inexperienced staff.
History:
The Waterfall approach to systems analysis and design was the
first established modern approach to building a system. This
method was originally defined by Winston W. Royce in 1970,
("The Waterfall Development Methodology", 2006).
Royce presented this model as an example of a flawed, none-
working model.
Phases:
Requirements Design
Requirements is an initial step in This is the second step in
waterfall model. All possible waterfall [Link] system
requirements of te system to be design helps in specifying
developed are are captured in hardware and system
this phase and documented in a requirements and helps in
requirement specification defining the overall system
[Link] this steps user architecture.
demands the entire requirement
for the software development.
Implementation Verification
It is very important part of waterfall In these steps the entire
model. After requirements and systems will be tested for any
design the next step in faults and [Link]
implementation. With inputs from functional and non-functional
the system design, the system is
testing is done the product is
first developed in small programs
deployed in the customer
called units, which are integrated in
the next phase. Each unit is environment or released into
developed and tested for its the market.
functionality, which is referred to as
Unit Testing. The main purpose of
these steps is to execute the
Maintenance
In these last steps there are
some issues which come up in
the client environment. In this
steps the issue will be fixed,
patches are released.
Maintenance is done to
deliver these changes in the
customer environment.
Where to use?
When requirements are stable and unlikely to change.
For small, straightforward projects with clear goals.
In projects requiring extensive documentation or regulatory
compliance.
For environments with predictable development cycles.
Advantages Disadvantages
This model is simple and easy to Once an application is in the testing stage, it
understand and use. is very difficult to go back and change
It is easy to manage due to the something that was not well-thought out in
rigidity of te model each phase has the concept stage.
specific deliverables and a review No working software is produced until late
process. during the life cycle.
In this model phase are processed High amounts of risk and uncertainty.
and completed one at a time. Not a good model for complex and object-
Phases do not overlap. oriented projects.
Waterfall model works well for Poor model for long and ongoing projects.
smaller projects where requirements
are very well understood. Not suitable for the projects where
requirements are at a moderate to high risk of
THANK YOU
T . Bindhu Priya
23031A0548
