Scribd
Upload
60 views

Waterfall Model SDLC

The Waterfall Model is a sequential software development process model where each phase must be completed before the next phase begins. It divides the software development process into 6 separate phases: requirements, design, implementation, testing, deployment, and maintenance.

Uploaded by

Kenya Levy
Copyright
© © All Rights Reserved
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
60 views

Waterfall Model SDLC

The Waterfall Model is a sequential software development process model where each phase must be completed before the next phase begins. It divides the software development process into 6 separate phases: requirements, design, implementation, testing, deployment, and maintenance.

Uploaded by

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

The Waterfall Model which is also referred to as a linear sequential life cycle is said to be the

first publicized software process model.


This process is strictly documented and predefined with features expected to every phase of
this software development life cycle.
In a waterfall model, each phase must be completed before the next phase can begin and there
is no overlapping in the phases.
Waterfall approach was first Software Development Life Cycle 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.
There are 6 phases in the Waterfall Model, they are:
1. Requirement
All possible requirements of the system to be developed are captured in this phase and
documented in a requirement specification document.
2. System and Software Design
In this phase, the Software Requirement Specification document is analysed and a design for
the entire system conceptualized. This system design helps in specifying hardware and
system requirements and helps in defining the overall system architecture.
3. Implementation
With inputs from the system design, the system is first developed in small programs called
units, which are integrated in the next phase.
4. Testing
All the units developed in the implementation phase are integrated into a system after testing
of each unit.
5. Deployment
Once the functional and non-functional testing is done; the product is deployed in the
customer environment or released into the market
6. 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.

You might also like