ISSN (Online) 2394-2320

International Journal of Engineering Research in Computer Science and Engineering

(IJERCSE)
Vol 4, Issue 9, September 2017

A Study on Software Development Life Cycle &

its Model
Navita
Department of Computer Science,
Vaish College, Rohtak, Haryana, India

Abstract— Software development life cycle (SDLC) is a well defined and systematic approach. It practiced for the development of
a reliable high quality software system. There are many SDLC models available. This paper describes five SDLC model , namely
;waterfall model ,iterative model, v shaped model ,spiral model, prototype model. Each development model has their advantages
and disadvantages. The aim of this paper is to present a study on software development life cycle (SDLC) and SDLC models with
their advantages and disadvantages.

Index Terms— Advantages, Software Development, SDLC, V Model, Waterfall Model.

I. INTRODUCTION Software development life cycle starts with preliminary

investigation. This phase verifies the problem in present
Today every work is done through technology. So, there system and understands the need for the required system.
is a need to develop more big and complex software The output of preliminary investigation decides whether
system which meet the user's changing and growing the new system should be developed or not. After
requirements. So, SDLC provides planned and systematic preliminary investigation, the output delivers to software
arrangement of activities to be carried out to deliver high analysis. In software analysis phase, studies the problem
quality products within time and budget. SDLC is a or requirements of software in detail. The main objective
methodology for designing, building and maintaining of this phase is to identify exactly "what type of features"
information and industrial systems. A software the software to be developed must provide. Software
development process has different phases. These phases analysis includes two distinct activities:
follow a top-to-bottom approach. Each phase takes input
from the previous phase, add features and then produce  Requirement analysis -: In requirement analysis,
outputs. The various phase of systematic development of all related data and information of customer
software are shown in figure 1[1]. requirements are collect and analyze.
 Software requirement specification -: After
analyzing requirements of the user, software
requirement specification (SRS) is developed. In
SRS, plans for project is develop which describe
the activities to be performed during the project.

After software analysis, software design takes place, in

this phase; the requirements are given a 'defined' form.
After designing phase comes the coding. Coding is
translating the design structure into a programming
language [2].
Output of coding phase deliver to system testing, in this
phase, ensures that the software is free from errors. After
testing the whole software, software maintenance is
required. The objective of software maintenance is to
Fig. 1: Software Development Life Cycle. make the software operational as per user requirements

All Rights Reserved © 2017 IJERCSE 1

 ISSN (Online) 2394-2320

International Journal of Engineering Research in Computer Science and Engineering

(IJERCSE)
Vol 4, Issue 9, September 2017

and to provide continuity of services. Using the SDLC steps are performed one after the other and fall like water
phases the user can develop the software according to falling from the sky that's why it is called waterfall model.
their requirements. This section has provided the phases
of SDLC. In section 2, SDLC models are discussed. In  Advantages
section 3, the conclusion is presented. o This model is easy to understand.
o It is easy to explain.
II. SOFTWARE DEVELOPMENT PROCESS o Testing is inherent to every phase.
MODEL o It is less costly.

A process model can be defined as a method, tool or steps  Disadvantages

for developing software. Some of the models are:- o In this model user training is less important.
o Before system testing, problems are not
 Waterfall Model discovered.
o It is not useful for big projects.
Waterfall model is the simplest and traditional software
process model. Waterfall model is mostly used for small
projects. This model works in a linear order. In this  Iterative Model
model, the output of one phase used as the input to the
next phase. So it is also called linear sequential model [3]. This model includes the features of both waterfall model
and prototype model. In this model the process start from
the requirements and iteratively enhance the requirements
until the final software implemented. In this iteration
process, the delivery of the increments to the user
continues until the software is completely developed [4].

Fig.3: Iterative Model.

This model works on four phases -:

 Requirement phase -: In this phase, a list of
Fig.2: Waterfall Model requirements is prepared.
 Design phase -: In this phase, software is
In this model, the first stage is system study. In this stage, designed according to the requirements.
studies the problem or requirements of software. After  Implementation phase -: in this phase, the
that in analysis phase , analyze the problem and software is implemented.
requirements and in designing phase, design is made for  Evaluation phase -: in this phase, the software is
requirements then in coding stage design structure is evaluated. The software is observed for further
translate into programming language . Output of coding is requirement.
delivering to testing phase. In this phase errors are
removing from the software. After testing the whole  Advantages
software, Maintenance phase is required. Since these o In this model better testing is possible at each
iteration.

All Rights Reserved © 2017 IJERCSE 2

 ISSN (Online) 2394-2320

International Journal of Engineering Research in Computer Science and Engineering

(IJERCSE)
Vol 4, Issue 9, September 2017

o This model does not require high complexity main activities represented by four sector- planning, risk
rate. analysis, development, and customer evaluation [6].
o In this model feedback is generated quickly.

 Disadvantages
o It requires planning of technical level.
o It is not easily understandable.

 V Model

The v model is useful in every phase of the software

Fig.5: Spiral Model.
development life cycle [5].
 Planning -: in this phase, objectives are
determined and alternatives are identified.
 Risk analysis -: in this, alternative is evaluated,
identify and resolve the risks.
 Development -: develop, verify next level
product.
 Customer evaluation -: in this, customer evaluate
the prototype.
Fig.4: V Model.

The v model is divided into two branches, where the left Each cycle of this model is built the software
branch analyses the requirement of the software to be progressively. In
developed. The right branch includes the testing activities. this all the risks are resolved and the software is ready for
The left and right branches of this model work development.
concurrently.
 Advantages
 Advantages o It is more realistic model.
o It is simple and easy to use. o Each cycle of the spiral is completed by a
o It works well for where requirement are customer evaluation.
easily understood. o It is good for large projects.
o V model covers all functional areas
 Disadvantages
 Disadvantages o It takes more cost for development.
o It is very inflexible. o It is not good for smaller projects.
o It is costly and required more time. o The success of project depends on the risk
o This model doesn't provide a clear path for analysis phase.
problem found during testing phases. o It is time consuming.

 Spiral Model III. CONCLUSION

The spiral model is good for large, expensive and In this paper, software development life cycle and SDLC
complicated projects. This model uses many of the same models are defined. SDLC is helpful for user for getting a
phases as the waterfall model. In this model, a spiral is high quality product within time and budget. In this paper,
used which has many cycles. Each cycle contains four five SDLC models are defined. Every model has its
advantages and some disadvantage, like waterfall model

All Rights Reserved © 2017 IJERCSE 3

 ISSN (Online) 2394-2320

International Journal of Engineering Research in Computer Science and Engineering

(IJERCSE)
Vol 4, Issue 9, September 2017

is good for small project and spiral model and prototype

model is good for large and complicated projects. So that
user can select the best suited model as per his
requirement.

REFERENCES

[1] S. Maheshwari and D. C. Jain, “Comperative analysis

of different type of models in software development life
cycle,” International Journal of Advanced Research in
Computer Science and Software Engineering, Vol.2,
Issue.5, pp. 285-290, 2012.

[2] M. Dahiya, “An Analysis of Life Cycle Models for

CBSD,” International Journal of Engineering and
Technology, Vol.9, Issue.2, pp. 1044-1048, April-May
2017.

[3] Msritse 2012 Dr. W. https: // msritse2012 .wordpress

.com /2012 /11 /27 /managing –the development- of –
large –software -systems/.

[4] N. M. A. Munassar and A. Govardhan, “A

Comparison Between Five Models Of Software
Engineering,” International Journal of Computer Science
Issues, Vol.7, Issue.5, pp. 94-101, 2010.

[5] R. R. Raval and H. M. Rathod, “Comparative Study of

Various Process Model in Software Development,”
International Journal of Computer Applications, Vol. 82,
Issue. 18, pp. 16-19, November 2013.

[6] M. Batra and A. Bhatnagar, “A Comparative Study of

Requirements Engineering Process Model,” International
Journal of Advanced Research in Computer Science,
Vol.8, Issue.3, pp. 740-745, March-April 2017.

All Rights Reserved © 2017 IJERCSE 4