Scribd
Upload
87 views

The Waterfall Model:: All Possible Requirements of The System To Be

The Waterfall model is a sequential software development process where progress flows in one direction like a waterfall from one phase to the next. It was the first process model introduced and involves requirement specification, design, implementation, testing, and maintenance phases. Each phase must be completed before moving to the next and changes are difficult to incorporate.

Uploaded by

SandeepGupta
Copyright
© Attribution Non-Commercial (BY-NC)
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
87 views

The Waterfall Model:: All Possible Requirements of The System To Be

The Waterfall model is a sequential software development process where progress flows in one direction like a waterfall from one phase to the next. It was the first process model introduced and involves requirement specification, design, implementation, testing, and maintenance phases. Each phase must be completed before moving to the next and changes are difficult to incorporate.

Uploaded by

SandeepGupta
Copyright
© Attribution Non-Commercial (BY-NC)
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 3

The Waterfall model

The waterfall model is a sequential software development process, in which


progress is seen like waterfall. Waterfall approach was first Process Model to be
introduced and followed widely in Software Engineering to ensure success of the
project. In "The Waterfall" approach, the whole process of software development
is divided into separate process phases. The phases in Waterfall model are:
1. Requirement Specification phase
2. Software Design
3. Implementation
4. Testing
5. Maintenance.

All these phases are cascaded to each other so that second phase is started as
defined set of goals are achieved for first phase and it is signed off, so the name
"Waterfall Model". All the methods and processes undertaken in Waterfall Model
are more visible.
The stages of "The Waterfall Model" can be explained as:
 Requirement Specification: All possible requirements of the system to be
developed are captured in this phase. Requirements are set of functionalities
and constraints that the end-user expects from the system. The requirements
are gathered from the end-user by consultation, these requirements are
analyzed for their validity and the possibility. Finally, a Requirement
Specification document is created for the next phase of the model.

 System & Software Design: Before a starting for actual coding, it is highly
important to understand what we are going to create and what it should look
like? The requirement specifications from first phase are studied in this phase
and system design is prepared. System Design helps in specifying hardware
and in defining overall system architecture. The system design specifications
serve as input for the next phase of the model.

 Implementation & Unit Testing: On receiving system design documents, the


work is divided in modules/units and actual coding is started. 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; this is referred as
Unit Testing. Unit testing mainly verifies if the modules/units meet their
specifications.

 Integration & System Testing: As specified above, the system is first divided in
units which are developed and tested for their functionalities. These units are
integrated into a complete system during Integration phase and tested to
check if all modules/units coordinate between each other and the system as a
whole behaves as per the specifications. After successfully testing the
software, it is delivered to the customer.

 Operations & Maintenance: This phase of "The Waterfall Model" is virtually


never ending phase (Very long). Generally, problems with the system
developed (which are not found during the development life cycle) come up
after its practical use starts, so the issues related to the system are solved
after deployment of the system. Not all the problems come in picture directly
but they arise time to time and needs to be solved; hence this process is
referred as Maintenance.
Advantages of Waterfall model:
1. Clear project objectives.
2. Stable project requirements.
3. Progress of system is measurable.
4. Stages and activities are well defined.
5. Helps to plan and schedule the project.
6. Risk reduction mechanisms are in place.
7. Confirming at every step ensures early detection.

Disadvantages of Waterfall model:


1. The waterfall model requires all requirements explicitly, but it is often
difficult for the customer to state all requirements explicitly.
2. Time consuming.
3. Can’t go backward.
4. Difficult in responding to changes.
5. Difficult in iteration.

You might also like