Examine the case for the waterfall lifecycle.

Does
waterfall life cycle play an important role in
modern system development, and if so at which
stages
Name:
1 Department One, Institution One, City One, Country One

E-mail: xxx@xxx.xx

Abstract
Every company in software industry domain has to follow a well structured or defined
methodology for the development of the end product . SDLC model helps the companies to
produce a product with good quality and budget.There are two widely used SDLC models in
the industry waterfall and agile. This paper focuses more on the waterfall lifecycle model , its
advantages and use case where this can be applied.

It is considered the most basic software development life cycle

1. Introduction model which is a sequential approach to developing software.
The progress in waterfall model can never be reverted i.e. we
Waterfall or lifecycle model is the process consisting of a
cannot turn back from one phase to the previous . All these
series of defined ,structured and well planned activities to
phases are connected to each other in which progress is seen
develop or maintain the software products. This model
as flowing steadily downwards (similar to a waterfall where
contains a series of steps that provide a robust model for the
water flows downward from hill) through the phases. Once the
development and management.This model aims at improving
water flow down from the hill top it cannot go back . With this
the quality of the software product and also of the code quality
model there is only one option and that is to move forward.
of the development method. It helps to produce a software that
This model is also called the classic or tradiitonal life cycle
is cost effective, highly competent and of high quality. Once
model as it suggests a systematic ,linear and structured
an application is created, the SDLC maps the proper delivery
approach to software development. In a waterfall process,
and retirement of the product .The model usually contain the
normally a defined set of documents derived from the output
following stages: requirements analysis, design,
of each phase serves as the input to the next phase. Once the
implementation (construction), testing, release and
previous document has been signed off team members do not
maintenance. There are two types of SDLC models widely in
have the flexibility to change the outputs that are certified.
use today waterfall or traditional approach and agile or
However, as there is a saying requirements are subject to
iterative approach. The waterfall model requires a well
change. Thus there is a need for a model which ensures that
chalked out plan and defined set of requirements that should
the modifications are done in a controlled manner without
be more or less fixed upfront in contrast to the agile SDLC
affecting the product and its progress.
which has less guidelines and makes adjustments to the design
as needed until a robust design is prepared.

1.1 Waterfall lifecycle model


1.1.1 Phases in waterfall lifecycle model
1. Requirements: The first phase involves
understanding the “what” of the product . Here, the
specifications of the input and output or the final
product are studied and documented.
2. System Design: The SRS document from the first
phase is studied and system design is prepared.
System Design helps in specifying hardware and
system requirements and also helps in defining
overall system architecture. This stage defines the
“how” of the product .
3. Implementation: The inputs from system design are
used to first develop small programs called units,
which are then integrated into the next phase. Each
unit is developed and tested individually for its
functionality.
4. Integration and Testing: All the units developed in
the implementation phase are integrated into a
system after testing of each independent unit. The
software designed, needs to go through constant
software testing to find out if there are any bugs or
defects. Testing is done so that the customer does
not face any problem during the installation of the
software.
5. Deployment of System: Once the functional and
non-functional testing is done, the product is
deployed in the live environment or released into
the market.
6. Maintenance: This step occurs after installation, and
involves making modifications to the deployed
system or an individual component to improve
performance or alter any existing features. These
modifications arise either due to change requested
by the customer, or defects ideintified during the
live use of the system. The customer is provided
with regular maintenance and support for the
developed product.
1.1.2 Advantages
1. Waterfall model provides a well defined structure for
organizing and controlling a software development project.
2. Design details are captured and fixed by the model before
any code is written hence saving time during the
development.
3. A proper technical document is prepared that makes it
easy for customers to know what and how of the product . The
documentation also help in the process of maintenance post
implementation.
4. Cost and time estimation can be accurately done if all the
procedures are followed.
5. Because of its sequential and linear nature gaps or issues
in one phase can be detected before moving on to the other.
6. A lot of emphasis is done on documentation. Any one
joining the development team may find it easy to catch up with
the help of these documents.
7. For smaller projects it is the best model to use and it also
requires less resource capacity .
8.It allows for departmentalization and managerial control.
This allows the product to be completed on time by setting a
defined schedule for every phase.
9. A project plan can be utilized for indistinguishable or
similar projects in the future.
1.1.3 When to use waterfall lifecycyle model
1. The requirements are well defined and fixed. The goal
is on the end product and not on the individual features.
2. There is no time limit or a reasonable amount of time is
available to develop the software.
3. There is a need to document everything.
4. You need a software that is highly reliable.
5. You want to use the end product.
6. Resources are not colocated.
The waterfall model works pretty well where the product
development mainly consists of adding limited functionalities
to an existing set of functionality. It also scales well for
projects where changes in design can be introduced in a
controlled way and the development can still be continued
without the requirement of customers or competitors. The
legal and regulatory bodies for e.g., the U.S. Department of
Defense, IT providers require the need to follow, as there is a
need to document their procedures right from requirement
analysis to maintenance.
Acknowledgements
I would like to take this opportunity to thank and express
my deep respect and regard for Supervisor(Name) and
Professor(Name) for this subject for their exemplary
guidance, constant encouragement and valuable feedback
throughout the preperation of this paper.Their valuable
suggestions were immensly helpful and working under them
was a knowledgeable experience.
References
[1] http://www.tutorialspoint.com/sdlc/
[2]http://www.codeproject.com/Articles/6144203/Agil e-software-
development-methodologies-and-how-t
[3] Youssef Bassil ” A Simulation Model for the Waterfall Software
Development Life Cycle” International Journal of Engineering &
Technology (IJET), ISSN: 2049-3444