Scribd
Upload
46 views

Waterfall Model Used in Software Development Reference: Software Requirements Engineering Waterfall Model

Uploaded by

Arfa Latif
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
46 views

Waterfall Model Used in Software Development Reference: Software Requirements Engineering Waterfall Model

Uploaded by

Arfa Latif
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/ 4

See discussions, stats, and author profiles for this publication at: https://www.researchgate.

net/publication/371902449

Waterfall Model Used in Software Development Reference: Software


Requirements Engineering Waterfall Model

Technical Report · June 2023


DOI: 10.13140/RG.2.2.29580.69764

CITATIONS READS

2 5,524

1 author:

Sardar Mudassar Ali Khan


Contour Software
154 PUBLICATIONS 5 CITATIONS

SEE PROFILE

All content following this page was uploaded by Sardar Mudassar Ali Khan on 27 June 2023.

The user has requested enhancement of the downloaded file.


Waterfall Model Used in Software
Development
Reference: Software Requirements Engineering by Sardar Mudassar Ali Khan

Waterfall Model
The waterfall model is the first model in software development history. It is also referred to as
the (Linear sequential life cycle model) this model is simple to understand and use. In the
waterfall model, each phase is completed before moving to the next phase. The waterfall model
is the first and earliest approach used in SDLC for the development of software products in this
model that do not overlap.

Waterfall Model Design


The waterfall approach was the first approach in the software development life cycle and was
widely used in the development of software products and for the success of the project.

Requirement Analysis

System Design

Implementation

Testing

Deployment

Maintenance

The sequential phases of waterfall models are.

▪ Requirement Analysis.
All the key requirements of the system development and captured in this phase and we
document them in the software requirement specification document.
▪ System Design.
The requirement specification from the first phase is studied in this phase and these
requirements help us to define the overall system design and architecture of the system.
▪ Implementation.
After defining the clear and rich requirements the fourth step is building and developing
the software product according to the defined standards. Software organizations start
coding and designing products this step involves the implementation of all the pre-and
post-condition of a project like the development of complete functionalities of the
software product according to the requirement verified by senior members of teams and
all the stakeholders of the project.
▪ Integration and testing
In this step of the software development life cycle, we define the testing strategies in
which we do the testing of different modules, and we check that either every module
is behaving and functioning according to the standard definition or according to the
requirements define in the first phase of the SDLC process.
▪ Deployment
After the complete testing of the product and the product is formally ready for
deployment then the of time product is released in the stages according to the
deployment plains of the organization. And some time product deployment is
dependent on the feedback of the customers.
▪ Maintenance
This activity is involving the modification of software to meet the customer and market
new trends. Modification means that improve the system to such standards that can
support today's technologies and meets the customer requirement efficiently.

Applications
The waterfall model is widely and extensively used in the software industry some given
below point explains the usage of the Waterfall model.
• The requirement is very well clear and fixed
• Product Definition is stable and well defined
• No ambiguity in the requirements
• Due to the rigidity of the model projects are short
Advantages of Waterfall models
• Simple and Easy to understand.
• Clearly and defined stages
• Easy to arrange tasks.
• Process and results are well documented.
• Works well when the project is small.
• Easy to manage due to the rigidity of the model.
Dis-Advantages of Waterfall models.
• The high number of risks and uncertainty
• Poor model for long and ongoing projects
• Not suitable for life-critical systems because of the rigidity
• Difficult to manage projects progress within stages.
• Not suitable for the project that they are following an Object-oriented approach.
• Cannot accommodate the requirement change process.

View publication stats

You might also like