Scribd
Upload
19 views

SDLC - Waterfall Model

The Waterfall Model was the earliest software development life cycle (SDLC) approach. It divides a project into sequential phases including requirements, design, implementation, testing, deployment, and maintenance. Each phase must be completed fully before the next phase can begin, resulting in a linear sequential flow with no overlap between phases. While simple to understand, the Waterfall Model has disadvantages such as inability to accommodate changing requirements or measure progress within phases.

Uploaded by

pradeepkumar116803
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
19 views

SDLC - Waterfall Model

The Waterfall Model was the earliest software development life cycle (SDLC) approach. It divides a project into sequential phases including requirements, design, implementation, testing, deployment, and maintenance. Each phase must be completed fully before the next phase can begin, resulting in a linear sequential flow with no overlap between phases. While simple to understand, the Waterfall Model has disadvantages such as inability to accommodate changing requirements or measure progress within phases.

Uploaded by

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

SDLC - Waterfall Model

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.

The Waterfall model is the earliest SDLC approach that was used for software development.

The waterfall Model illustrates the software development process in a linear sequential flow. This
means that any phase in the development process begins only if the previous phase is complete. In
this waterfall model, the phases do not overlap.

Waterfall Model - Design


Waterfall approach was 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 this Waterfall model, typically, the outcome of one phase acts as the
input for the next phase sequentially.

The following illustration is a representation of the different phases of the Waterfall Model.

Sign in to tutorialspoint.com with Google

Pradeep Bathula
[email protected]

Pradeep Kumar Cs
[email protected]
The sequential phases in Waterfall model are −

Requirement Gathering and analysis − All possible requirements of the system to be


developed are captured in this phase and documented in a requirement specification
document.
System Design − The requirement specifications from first phase are studied in this phase
and the system design is prepared. This system design helps in specifying hardware and
system requirements and helps in defining the overall system architecture.

Implementation − With inputs from the 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.

Integration and Testing − 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.
Deployment of system − Once the functional and non-functional testing is done; the product
is deployed in the customer environment or released into the market.

Maintenance − There are some issues which come up in the client environment. To fix those
issues, patches are released. Also to enhance the product some better versions are
released. Maintenance is done to deliver these changes in the customer environment.
All these phases are cascaded to each other in which progress is seen as flowing steadily
downwards (like a waterfall) through the phases. The next phase is started only after the defined set
of goals are achieved for previous phase and it is signed off, so the name "Waterfall Model". In this
model, phases do not overlap.

Waterfall Model - 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.

Ample resources with required expertise are available to support the product.
The project is short.

Waterfall Model - Advantages


The advantages of waterfall development are that it allows for departmentalization and control. A
schedule can be set with deadlines for each stage of development and a product can proceed
through the development process model phases one by one.
Development moves from concept, through design, implementation, testing, installation,
troubleshooting, and ends up at operation and maintenance. Each phase of development proceeds
in strict order.

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


The disadvantage of waterfall development is that it does not allow much reflection or revision.
Once an application is in the testing stage, it is very difficult to go back and change something that
was not well-documented or thought upon in the concept stage.

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.
So, risk and uncertainty is high with this process model.

It is difficult to measure progress within stages.


Cannot accommodate changing requirements.
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 bottleneck or challenges early.

You might also like