Volume 9, Special Issue No.

2, April 2018 ISBN: 978-93-5311-643-9

International Journal of Advanced Research in Computer Science
(ISSN: 0976-5697)
CONFERENCE PAPER
Available Online at www.ijarcs.info
CRITICAL ANALYSIS ON VARIOUS SOFTWARE DEVELOPMENT MODELS
Arshi Fatima Shashvat Gupta
B. Tech CSE 3rd Year B. Tech CSE 3rd Year
Integral University, Bansal Institute of Engineering and Technology,
Lucknow, India. Lucknow, India.
e-mail: arshiifatima@gmail.com. e-mail: shashvatgupta448@gmail.com.

Abstract:Software engineering deals with development of software to achieve the user requirements under a given time and specified budget.
Thousands of software are developed every year but very few satisfy all the user expectations. A software development has certain phases under
which a software undergoes during its life cycle. The correct software development model aims to achieve a quality software in low cost. The
selection of correct software development model would become easier after this critical analysis. The aim of this paper is to minimize the
ambiguity of selection of software models at the time of development and modify the phases of the software development models according to
today’s need.

Keywords:Software; Software Development Life Cycle; Development Models; Requirements; Software Engineering.

I. INTRODUCTION Software Development Life Cycle

A software is not only a piece of code but it is a combination

of program with well-defined documentation and procedures
to operate on. Software engineering is the systematic approach
of the systematic development, designing, operation,
maintenance and retirement of a software [1]. A new software
developer faces a lot of problems in selecting a desired and
correct approach for software development. Sometimes they
often neglect such approaches and implement the ad-hoc
model which later becomes a problem duringfuture
development of the software.
Software Development Life Cycle is a series of set of different
phases under which a software evolves. Suchstages are-
1- Feasibility analysis
In this phase we check whether the project
cost and schedule assumptions are realistic or not.
2- Requirement gathering
In requirement gathering we collect all the
information provided by the customer and then
analyze it and a final document named as SRS,
Software Requirement Specification which describes
each requirement specified by client without
describing how it will be implemented by the
developer.

3- Designing
The goal this phase is to transform the document
SRS into the structure that is suitable for
implementing programming logics.

4- Coding
In this phase the design is implemented by the
developer. The implementation becomes easier due
to detailed design in earlier phase.

5- Software testing and integration

In this phase the developed product is tested
individually and later integration of each module is
done. And then the product is launched in the market
for the users.

6- Maintenance and operation

In this phaseerror correction is done based on the
feedback of end user and modules are enhanced,
altered, and deleted if needed.

Conference Paper: II International Conference on “Advancement in Computer Engineering and Information Technology” 
Organized by: Department of Computer Science and Engineering, Integral University, Lucknow, U.P. India            157 
 Arshi Fatima
F et al, Inteernational Journ
nal of Advanced Research in Computer Science,, 9 (Special Issuee II), April 2018,,157-161

It deeals with the testing

t of eachh module of th
he software inn unit
Software Devellopment Mod
dels testiing phase andd later each moodule is integ
grated and testted to
satissfy the requireements of the customer.
All these
t models give
g an abstraact view for thhe developmeent of
a sofftware. 7- Mainten
nance-

Water fall mod

1-W del In thhis phase insstallation of tthe software is provided tot the
2-Prrototype mod del cliennt and augmeented based oon end users feedback andd any
3-Iteerative/Increm
mental modeel main ntenance of sooftware is donne if required and again soft
ftware
4-Sppiral model is haanded to the end
e user.
5-V model
6-RA AD model
7-Aggile model
Userr Needs

II. WATE
ERFALL MODE
EL

This model is also called traditional and simplest softtware System Reequirementss
deveelopment moddel it was oriiginally propoosed by Roycce. It
servees as the basee model for thhe other modeels. Generally used
in goovernment proojects or for those
t projects which are haaving
no sttrict time limittation. UI Design
D

It is a linear sequeencing model all the phasess are interlinkked to

eachh other output of one phase works as the input for anoother.
Eachh phase deals with distinctt and separatee set of conccerns. UX Design
D
The complex taskk of software building
b is divided into sm maller
phasses and simpleer modules.
Softwarre Coading
Phases of waaterfall modell

1- User Neeeds-
Softwarre Testing
It deals with
w the speciification that are needed byy the
cliennt from the deesired softwaree that the devveloper must fulfill
f
durinng the producttion of softwaare.
Main
ntinance
ment Analysiis-
2- Requirem

It deals with
w the establishment of components foor the Watterfall Modell [7]
buildding system including haardware requirement, softtware
toolss and other necessary components
c for the softtware
buildding.
III. PROT
TO-TYPE MOD
DEL

3- UI Desiggn- A prototype is made

m using thee requirementt gathered iniitially
It deeals with thee designing and a the lookk and feel off the and given to the client and fuurther updation ns are made based
b
softwware. It is beinng done on thhe basis of SR
RS document made
m on thet feedback and then a real softwaree developed. This
in reequirement phase. apprroach is used in heavy andd complex proj ojects with no prior
know wledge.
4- UX Design- A prototype is giiven to client to use it and d check that all
a his
need ds and works are being perrformed easily y and efficiently or
w the desiggning of logics for development
It deals with not. If any updaation is givenn by the clieent then deveeloper
of diifferent functionalities of a software to enhance the user updaate all those requirementts and again provide a newer n
expeerience. verssion of the proototype.
Devvelopment of prototypes uundergoes deesign, coding,, and
5- Coding- testiing but each of
o these phase is not done veery formally.
Posssibility of faillure of softwaare decreases since in it riisk is
It is the phase
p in whicch the logics defined
d in dettailed alreaady considereed. Prototypee model has limited functtional
desiggn are being immplemented using
u programmming languagges. w reliability and untested
capaabilities, low d performancce is
usuaally low. Prottotype may bee useable form m but it is noot the
6- Softwaree Testing- final product.

Conferen
nce Paper: II In
nternational Connference on “Advancement in Computer Eng gineering and Innformation Tecchnology” 
Organized by: Department of Comp puter Science a
and Engineeringg, Integral Univ
versity, Lucknow
w, U.P. India            158 
 Arshi Fatima et al, International Journal of Advanced Research in Computer Science, 9 (Special Issue II), April 2018,157-161

Spiral Model [7]

V. INCREMENTAL MODEL

Incremental model is also called iterative model. Incremental

Prototype Model[6] model consists of benefits of both waterfall as well as prototype
model.
Unlike prototype model, the model is not discarded but it is
extended based on the customer’s feedback. This model uses
IV. SPIRAL MODEL
divide and conquer methodology hence the software is divided
into smaller module. The modules are assigned priority-based
Many projects have failed due to no consideration of risk
clients preference. Modules with higher priority are developed
factor this model is focuses completely on the risk factor.Barry
followed by the modules having lower priority.
Bohem recognized this problem and incorporated the “Project
The delivery of software is done in patches hence initial
Risk” factor into life cycle model. It is favored by developers.
delivery of software is faster. Updations are done later based
The radial dimension of the model represents the cumulative
on the further requirements.
costs. Each path around the spiral is indicative of increased
costs [3]. The angular dimension represents the progress made
in completing each cycle. Each loop of the spiral from X-axis
clockwise through 360 degree represents one phase. One phase
is split roughly into four sectors of major activities-

1- Planning:
Determination of objectives, alternatives and
constraints.

2- Risk Analysis:
Analyze alternatives and attempts to identify and
resolve the risk involved in it.

3- Development:
Product development and testing of product.

4- Evaluation:
Customer evolution.

Incremental Model [8]

Conference Paper: II International Conference on “Advancement in Computer Engineering and Information Technology” 
Organized by: Department of Computer Science and Engineering, Integral University, Lucknow, U.P. India            159 
 Arshi Fatima et al, International Journal of Advanced Research in Computer Science, 9 (Special Issue II), April 2018,157-161

SOFTWARE FAILURE costs. 

• 41% failed to deliver the expected business value 
FACTORS AFFECTING SOFTWARE FAILURE and ROI. 
• 33% file to perform against expectations. 
1- Lesser user involvement  
Avanade Research Report (2007) 
2- Ambiguous requirements
 
3- Changing requirements • 66% of failure due to system specification. 
• 51% due requirement understanding. 
4- Time bounday • 49% due to technology selection. 
 
5- Team management ESSU  (European  Service  Strategy  Unit)  Research 
Report 
FAILURE ANALYSIS 2007 
 
TCS (Tata Consultancy Services) 2007  • 57% of contracts experienced cost overruns. 
  • 33% of contracts suffered major delays. 
• 62% of organizations experienced IT projects that  • 30% of contracts were terminated. 
failed to meet their schedules.[5]  • 12.5% of Strategic Service Delivery Partnerships 
• 49% suffered from budget overruns.  have failed.
• 47% had higher‐than‐expected maintenance 

CRITICAL COMPARISON OF SDLC MODELS [5]

Features Waterfall Model Iterative Model Prototyping Spiral Model Agile Model
Model

Changes
User Needs Beginning Beginning Frequently Beginning Incrementally
Changed

Software Cost Low Low High Expensive Much Expensive

Simplicity Simple Intermediate Simple Intermediate Hard

Expertise Required High High Medium High High

Risk Identification High Easily Manage Low Low High

Overlapping No No Yes Yes Yes

Phases

Flexibility Rigid Less Flexible Highly Flexible Flexible Highly Flexible

Maintenance Least Glamorous Promoted Routine Typical Routine

Maintainability Maintenance Maintenance

Conference Paper: II International Conference on “Advancement in Computer Engineering and Information Technology” 
Organized by: Department of Computer Science and Engineering, Integral University, Lucknow, U.P. India            160 
 Arshi Fatima et al, International Journal of Advanced Research in Computer Science, 9 (Special Issue II), April 2018,157-161

Speed to change Low High Medium High High

Documentation Vital Yes Weak Yes Yes

Required

User Control Only at Beginning Intermediate High High High

Customer Priority Nil Nil Intermediate Intermediate High

Resource Control Yes Yes No Yes No

Guarantee of Less High Good High Good

Success

VI. CONCLUSION
According to our critical analysis we conclude that none of the
models aresuperior to other the only difference is each model [1]
has its own advantages and disadvantages like waterfall model
is good for small project and spiral model and prototype [2]
model is good for large and complicated projects. Traditional [3]
software development models are too old fashioned for the
development of newer software’s. The biggest disadvantage of [4]
waterfall model is that the requirement gathering freezes
before designing starts. A lot of software’s are developed
every year hence all those software’s need to have better user
experience in order to attract more users.
Projects run over budget or are terminated prematurelyand
those that reach completion often fall far short ofmeeting user [5]
expectations and business functionalities.
In this paper we analyze SDLC models and modify them
according to today’s need.
VII. ACKNOWLEDGMENT [6]
The success of our research is never limited to an individual. It [7]
is the cooperative effort of individuals surrounding us. This
would have not been completed without the guidance and
support of ‘Mr. Shish Ahmed’, Associate Professor in
Department of Computer Science and Engineering at Integral
University Lucknow. [8]
VIII. REFERENCES
‘Software Engineeering - A precise Approach’ By
Pankaj Jalote
www.engpapers.com
‘Software Engineeering’ – By KK Agarwal and
Yogesh Singh.
Mr. Ashish Kumar Gupta: ‘A COMPARISON
BETWEEN DIFFERENT TYPES OFSOFTWARE
DEVELOPMENT LIFE CYCLE MODELSIN
SOFTWARE ENGINEERING’, International Journal
of Advanced Technology in Engineering and Science,
ISSN (online): 2348 – 7550, Volume No 03, Special
Issue No. 01, March 2015
Rupinder Kaur, Dr. Jyotsna Sengupta: ‘Software
Process Models and Analysis onFailure of Software
Development Projects’, International Journal of
Scientific & Engineering Research Volume 2, Issue
2, February-2011ISSN 2229-5518
http://istqbexamcertification.com/what-is-prototype-
model-advantages-disadvantages-and-when-to-use-it/
Navita: ‘A Study on Software Development Life
Cycle &its Model’, International Journal of
Engineering Research in Computer Science and
Engineering(IJERCSE)Vol 4, Issue 9, September
2017
Ratnmala R. Raval:Haresh M. Rathod ,'Comparative
Study of Various Process Model in Software
Development',International Journal of Computer
Applications (0975 – 8887) Volume 82 – No 18,
November 2013

Conference Paper: II International Conference on “Advancement in Computer Engineering and Information Technology” 
Organized by: Department of Computer Science and Engineering, Integral University, Lucknow, U.P. India            161