ISSN 2278-3091

VolumeTrends
Sajid Ahmed Ghanghro et al., International Journal of Advanced 10, No.3, May -Science
in Computer June 2021
and Engineering, 10(3), May - June 2021, 2593– 2599
International Journal of Advanced Trends in Computer Science and Engineering
Available Online at http://www.warse.org/IJATCSE/static/pdf/file/ijatcse1511032021.pdf
https://doi.org/10.30534/ijatcse/2021/1521032021

Comparative Analysis of Software Process Models in

Software Development
Sajid Ahmed Ghanghro1, Dr. Muhammad Ajmal Sawand2 Wajid Ahmed Channa3, Ubaidulla alias
Kashif4, Muhammad Hanif Tunio5, Kishor Kumar6, Nooruddin7
1
Shah Abdul Latif University Khairpur, Pakistan, [email protected]
2
Sukkur IBA University Sukkur, Pakistan, [email protected]
3
Sukkur IBA University Sukkur, Pakistan, [email protected]
4
The Shaikh Ayaz University Shikarpur, Pakistan, [email protected]
5
Shah Abdul Latif University Khairpur, Pakistan, [email protected]
6
Sukkur IBA University Sukkur, Pakistan, [email protected]
7
Tianjin University, China, [email protected]

 Software Development
ABSTRACT  Testing
The success and failure of software development  Implementation
depends on the software process models. These models  Documentation and Training
are the key factors in complete development process. It
is comprises of various stages i.e., requirement  Software Maintenance
gathering, designing, development, testing and
implementation. The contribution of this paper is a Software development team considers the aims and goals of a
comprehensive survey of widely used process models. particular project for choosing the software process model to
Moreover, it would definitely play as a guiding path for carry out the whole project. There are different types of
the researchers to explore future directions for possible software development process models and organizations
research. Extensive analysis of all these five process accept the best-suited model which simplifies the “software
models is also discussed. Each software process model
possesses different factors and parameters which are development process” and increases the throughput of its
concisely included so that researchers could easily team members. This research discusses the comparison
choose a process model based on the need, resources, between five “process models.”
and expertise.  Waterfall Model
 Iterative Model
Key words: Software Process Models; Development,  Spiral Model
Software Development Life Cycle (SDLC)  Prototype Model
 Agile Model
1. INTRODUCTION
This research starts with methodology of each listed models.
Quality of software development leads to the efficient Moreover, it starts with necessary steps in software
software process model, also known as “Software development life cycle. The comparative analysis of these
Development Life Cycle (SDLC).” In this research paper, we software process models is also carried out in this research
present the comparative analysis of different software process paper.
models. Different models are available for different software
processes. Each model describes the variety of actions that are 2. SOFTWARE DEVELOPMENT LIFE CYCLE
performed during the process. “Software process models” are
In this paper, we have examine and compare the main
used for the development of projects depending on the nature
characteristics of OS e.g architecture, scheduling, algorithm,
of the project. We have developed software process models in
memory protection and management, protocols, real-time and
the decades to improve the quality of “software development.”
non-real time applications, resource allocation for WSN [5].
A “software development process model” is a skeleton
In this paper design approaches taken by OS and their
proposed for the elaboration of a software product. “Software
weaknesses and supports are also discussed comparatively. In
development processes” consist of different activities, which
this paper we have compared only OS that have been designed
are the following.
for nodes that have limited resources. Powerful motes can run
more powerful OS and they act as cluster heads/sinks in a
 Requirement Gathering and Analysis
WSN [6]. In this paper we will be discussing WSN major
 Software Architecture design concerns for OS. Then in next section we will be
 Software Design
2593
Sajid Ahmed Ghanghro et al., International Journal of Advanced Trends in Computer Science and Engineering, 10(3), May - June 2021, 2593– 2599

talking about the importance and need of OS in WSN. Then carry the whole project, and it ensures designing flaws we
in the preceding sections you will find the review of popular start to develop software. The model begins with collecting
and trending OS for WSN such as TinyOS, MANSTIS OS, the requirement of the system and continues to system and
Nano-RK and liteOS [7]. Later in next section comparative architecture design, coding, testing, deployment, and
analysis and advanced research expected to be done in future maintenance. Figure 2 describes the general view of the
is discussed and finally conclusion of this paper. waterfall model

Basic Principle of Waterfall Model

 Project is divided in sequential phases
 Importance should be given to planning of the
complete project
 Time schedules for the entire project are defined
 Deadlines should be clearly defined, meeting them is
equally important
 Approval of user and management is required at the
completion of phase before going to start a new
phase.

Advantages of Waterfall Model

 Easy to use and understand
 Each step has well-defined milestones
 Work well on mature products and week team
 It acts as like a template in which methods for analysis
Figure 1: Software Development Life Cycle design, coding and maintenance can place [1]

SDLC Phases Disadvantages of Waterfall Model

 Requirement gathering and analysis  Requirements are not changeable once designing
 Design of System phase has been completed
 Implementation or coding  High amount risk and uncertainty
 Integration and Testing  If the client is not clear at the time of requirement
 Deployment of system phase, it is tough to accept any change at any stage
 Another significant disadvantage of waterfall model
 Maintenance
is that a client cannot have any useful product till the
final stage of development is not complete.
3. SOFTWARE PROCESS MODELS
A “software process model” is abstract representation of the
process which are used to develop the software, it only follows
the SDLC which includes Design, Implementation, Testing,
and Maintenance.

A. Waterfall Model
Waterfall model is a traditional model also known as an
initial or classical model for software development. Waterfall
model describes the development methodology that is linear
and consecutive. Due to the subsequent flow of phases in a
waterfall model, it cannot go back to its previous stage. After
completing a development phase, the process moves to the
next step, and cannot turn back to its previous stage. Waterfall
model has different aims and goals for each level of its
models. It is widely used by Government projects and mature
organizations and mostly applicable in case of small projects
where there is no chance of changing requirements. In the
waterfall model planning is the early stage which helps to Figure 2: Waterfall Model
2594
Sajid Ahmed Ghanghro et al., International Journal of Advanced Trends in Computer Science and Engineering, 10(3), May - June 2021, 2593– 2599

A. Iterative Model  Testing and debugging is easy due to smaller

Iterative design is a method in software development life cycle iterations
which focuses on breaking down the software development  It allows feedback to precede iterations
into small chunks. In the iterative design, features are
developed with repeated cycles. The process is started with Disadvantages of Iterative Model
iterations and goes through with a simple execution of small  No clear goal is for the iterations
activities of “software requirements” and incrementally  More resources may be required
produces the versions of software till the final version is  Complex management in the team to manage the
developed. Unlike waterfall model, in the beginning, iterations
requirements do not need to be complete. Since development  System and design issue may be rise due to incomplete
starts with implementing a small part of the software and requirements
continues until end or completion of the software to be
B. Spiral Model
deployed. While working with the iterative model, we create a
rough product or product piece in a single monotony. We then Spiral model acts as iterative model with more importance on
check the product and improve it in next iteration and the risk inquiry factor in software development. This model is
same process continues until the completion of the product. more suitable for large-scale projects. There are specific
The purpose to work iteratively is to allow greater flexibility activities/phases in a single iteration (Spiral) where output is
for changes. While working iteratively, the team goes through the small prototype of comprehensive software [3]. The
a cycle in which iteration is completely evaluated and the activities of the spiral model are “Planning, Analyzing,
changes needed to deliver the required product to the Engineering, and Evaluation”. A software project frequently
customer are determined. passes through these phases in iterations called “Spirals” for
the entire duration of software development.

Figure 3: Iterative Model

Basic Principle
 The product is divided into small iterations
 User requirements are managed instead of the tasks.
User requirements are based on use cases and
nonfunctional requirements [2] Figure 4: Spiral Model
 Manage business goals, due to deadlines and budget
 Start with a simple execution of the subsection of Basic Principle of Spiral Model
requirements that demonstrates the key aspect of the  Focus is on risk assessment and minimization of
system [2]. project risks. Project is divided into smaller parts
while giving greater flexibility to change during the
development process allowing for risk assessment
Advantages of Iterative Model and measuring consideration of the project's
 Progress can be measured continuation throughout its life cycle development
 Some working functionality can be developed quickly [3].
 Easy to accept changes and are less costly  Each interval around the spiral travels through the
 Parallel development of different iterations can be activities of spiral model.
plane

2595
Sajid Ahmed Ghanghro et al., International Journal of Advanced Trends in Computer Science and Engineering, 10(3), May - June 2021, 2593– 2599

Advantages of Spiral Model The prototype is given to the client and the client uses it.
 High amount of risk analysis Moreover, they provide feedback on the prototype of
 Estimation of Budget, cost, and Scheduling developers: "What's correct, what needs to be changed, what's
 Provide working product at the early stage of SDLC missing, what's not needed, etc. Based on the feedback,
 Requirements are readily acceptable for changes at prototypes are changed to accommodate some of the proposed
any stage changes. Users and customers can again therefore be allowed
to use the system [4]. This cycle is repeated for prototype
Disadvantages of Spiral Model assessment. Based on the feedback, basic requirements are
 Experts are the need for risk factor analysis changed to produce a final specification, which is then used to
 This model can be costly develop a quality system.
 Risk of not meeting the schedule or budget
 Project success depends on the risk factor

Activity Activities Output

Name Achieved
Planning Requirements are List of finalized
Gathered requirements
Risk Analysis Requirements are Documents which
considered and highlight all the
stakeholders do risks and its change
the procedures
brainstorming to
recognize the
possible risks
Engineering Authentic - Coding.
development and - Test cases and test
testing of results
software is - Test Summary.
performed - Report.
during this phase
Evaluation Client assess the Features that have Figure 5: Prototype Model
software and been fulfilled are Basic Principle of Prototype Model
deliver their documented  Project risk is reduced by breaking the project into
response for smaller sections and providing flexibility to change
endorsement or during the development process [5]
rejection  The user is involved in the complete development of
Table 1: Activities od Spiral Model software, which gives feedback after prototype for
the acceptance or any other change in the project
C. Prototype Model  Small scale mockups are prepared until the user
The prototype model refers to developing a prototype of a accepts the desired prototype
software application which shows the features of the software  While most prototypes are drawn up with some
which is underdeveloped. In prototype model the expectations that they will be discarded, it is possible
requirements are not frozen before going to start the design, in some cases to evolve from prototype to working
development and testing phases of the software. The system [5].
development of the software starts with current known
conditions. By this model, the client can get the idea of the Advantages of Prototype Model
system which will be delivered at the end. It helps in  Prototype gives an idea to the user that how the system
obtaining valuable feedback from the customer and helps the will look like finally
software development team to clarify whether the system is  Increases system development speed [6]
accurately acknowledged by the client. The prototype is a  Users have involved actively
working model of software with some limited functions [4].  Errors can be detected at early stage
The prototype does not always keep the exact logic that will be  Missing functionality can be determined easily at first
used in the delivered software. It also helps to understand stage [7]
requirements that are unique to the user and may not be taken  Helps in reducing the risk factor from the failure of the
into account by the developer during the product design. system

2596
Sajid Ahmed Ghanghro et al., International Journal of Advanced Trends in Computer Science and Engineering, 10(3), May - June 2021, 2593– 2599

Disadvantages of Prototype Model Advantages of Agile Model

 This model is time-consuming and expensive in the  Promote team works and cross functional team and
case until the user accepts the prototype [7] training
 The prototype can lead false expectation  Functionality can be developed rapidly
 The primary objective of prototypes is rapid  Welcome changing requirements, even late in
development. Thus, system design may seem like it development
has been developed in series without considering the  People and interactions are given preferences rather
integration of all other components than processes and tools. Developers, customers, and
 The possibility of causing systems to be left testers regularly interact with each other [10][11]
unfinished
 Not suitable for the large type of projects. Disadvantages of Agile Model
 It does not focus on the necessary designing and
D. Agile Methodology
documentation
Agile development is an incremental model. This method  Estimating the large projects at the beginning is
focuses on process flexibility and customer satisfaction by difficult
rapid delivery of working “software product.” In Agile, the  Not suitable for handling complex dependencies
tasks are broken down into small time boxes which are easy to  Change in technology may be quite difficult and
measure and bring specific features for a release. An iterative challenging task due to lack of documentation
approach is carried out, and working features are provided at
the end of the each iteration. Iteration is typically of two to
four weeks and involves cross-functional team to work
simultaneously on the project. In each iteration of an agile
process, all activities like planning, designing, and
development and testing [11] are performed. In agile
methodology, communication is preferable regardless of
documentation. User requirements and desired features of the
system can be converted to successful deliverables.
There are different frameworks under the umbrella of agile
development life cycle. Like, Scrum, Feature Driven
Development (FDD), Extreme Programming (XP), and
Dynamic System Development Method (DSDM).

Figure 6: Agile Methodology

Basic Principle of Agile Methodology

 Highest priority of the agile model is to satisfy the
customer through the early delivery of valuable
working software [8]
 The working product is the primary measure of
progress
 The most efficient and effective way of
communicating information is face to face
communication [9]
 Cross-functional teams work together.

2597
Sajid Ahmed Ghanghro et al., International Journal of Advanced Trends in Computer Science and Engineering, 10(3), May - June 2021, 2593– 2599

Table 2: A COMPREHENSIVE ANALYSIS OF SOFWTWARE PROCESS MODELS

Waterfall Iterative Prototype
Agile
Parameters Spiral Model
Model Model Model
Methodology
Requirement Change
Beginning level Beginning level Beginning level Beginning level
Specification incrementally
Requirement Well Not-Well Not-Well Not-Well Well
Understanding understood understood understood understood understood
Feedback from
No No No Yes Yes
user
Cost Low Low High High Medium
Risk At beginning
No No No No
identification level
Complexity of
No No Yes Yes No
system
User
Beginning level Medium High High High
coordination
Priority on
Identification Priority on customer
Flow of
Linear flow Iterative flow of risk at each customer feedback and
activities
stage feedback incremental
flow
Core
Complete
requirements
Precondition requirements Clear idea of
of product No No
Or Prerequisite should be quick design
should be well
clearly defined
understood
Widely used
Usability Low Low Medium High
currently
Customer
Priority for No No Intermediate Intermediate High
Implementation
Industry
Basic Basic Medium Medium High
approach
Organization
Yes Yes Yes Yes No
resources
Implementation Depends on Depends on
Long Short Short
time project project

2598
Sajid Ahmed Ghanghro et al., International Journal of Advanced Trends in Computer Science and Engineering, 10(3), May - June 2021, 2593– 2599

[9] Kaur, Rupinder, and Jyotsna Sengupta. ”Software

4. CONCLUSION process models and analysis on failure of software
This study is focused on comparative analysis of different development projects.” arXiv preprint arXiv:1306.1068
software process models. Moreover, it explained five (2013).
different process models considering various factors. It’s [10] Kautz, Karlheinz, Henrik Westergaard Hansen, and Kim
concluded that Waterfall model provides the foundation for a Thaysen. ”Applying and adjusting a software process
growth of model and the development team is familiar improvement model in practice: the use of the IDEAL
regarding complete requirements and environment to adopt model in a small software enterprise.” Proceedings of the
this model. Iterative design is the enhanced model of the 22nd international conference on Software engineering.
waterfall. Iterative design gives feedback on the previous ACM, 2000.
stage. The spiral model deals with the risk of the total value of [11] Chemsripong, Sujinda, and Chutchonook Charutwinyo.
the development project and is used for the development of "Competency Model of software Developer in
complex and expensive projects. The prototype model is used Thailand." European Journal of Molecular & Clinical
for when the desired system needs to have more interaction Medicine 7.3 (2020): 714-722.
with end user. The agile methodology welcomes changes at
every phase. In agile methodology, it is easy to make shifts in
any feature and its focus on delivering working software
frequently. The Comparative analysis includes the
advantages and disadvantages of different software process
models which help out to select specific model at particular
situation depending on customer demand and need [10]. The
feasibility of the project for development can be judged by
keeping in mind the factors like cost, time and efficiency.

REFERENCES

[1] SVITS, Indore MP. ”A Comparative Analysis of

Different types of Models in Software Development Life
Cycle.” International Journal 2.5 (2012).
[2] Raval, Ratnmala R., and Haresh M. Rathod.
”Comparative Study of Various Process Model in
Software Development.” International Journal of
Computer Applications 82.18 (2013)..
[3] Munassar, Nabil Mohammed Ali, and A. Govardhan. ”A
comparison between five models of software
engineering.” IJCSI 5 (2010): 95-101.
[4] Pino, Francisco J., Flix Garcia, and Mario Piattini. ”Key
processes to start software process improvement in small
companies.” Proceedings of the 2009 ACM symposium
on Applied Computing. ACM, 2009.
[5] Sarker, Iqbal H., et al. ”A Survey of Software
Development Process Models in Software Engineering.”
International Journal of Software Engineering and Its
Applications 9.11 (2015): 55-70.
[6] Dholakia, Mr Preyash, and Mr Dishek Mankad. ”The
Comparative Research on Various Software
Development Process Model.” International Journal of
Scientific and Research Publications 3.3 (2013).
[7] Ashrafi, Noushin. ”The impact of software process
improvement on quality: in theory and practice.”
Information Management 40.7 (2003): 677-690.
[8] Acua, Silvia Teresita, and Xavier Ferr. ”Software
Process Modelling.” ISAS-SCI (1). 2001.

2599