Software process models- Agile models-SDLC(Software Development Life Cycle)
Software Engineering
Software process models- Agile models-SDLC(Software Development Life Cycle)
Sruthi Rajendran
Msc Computer Science 2nd Semester
Center For Computer Science and
Information Technology
Vatakara, India
sruthirajendran20@gmail.com
Abstract—Software engineering works on different models.
Models plays most important role while developing any
software. Models may be considered as a skeleton of the
software.. There are many development life cycle models that
have been developed in order to achieve different required
objectives. The models specify the various stages of the process
and the order in which they are carried out. Further detail
description of each model is carried out in this paper by
explaining its importance and pros and cons of the models.
There are models like waterfall model, Incremental models and
Evolutionary models. Agile methodology that utilizes iterative
development and prototyping are widely used in variety of
industry projects as a light weight development method which
can satisfy to the changes of requirements. Traditional
software development processes are not much efficient to
manage the rapid change in requirements. Despite the
advantages of Agile, criticism on agile methodology states that
it fails to pay attention to architectural and design issues and
therefore is bound to produce small design-decisions. Here, in
this paper we identify the impacts that agile methodology has
on software development processes with respect to quality
within the organizational, methodical, and cultural framework.
The software development life cycle (SDLC) is used to design,
develop and produce high quality, reliable, cost effective and
within time software products in the software industry. This is
also called software development process model. There are
different SDLC process models are available. The main
purpose of this paper is to explain some of important SDLC
models like Waterfall Model, Iterative Model, Spiral Model, V-
Model, Big Bang Model, Agile Model, Rapid Application
Development Model and Software Prototype. The main
purpose of this paper is to explain advantages and
disadvantages of these SDLC models.
Keywords— Software Models, Waterfall Model, Incremental
Models, Evolutionary models, Agile Model, RAD, Software
Prototype, Agile Alliance, Agile Methodology, Crystal Method,
Extreme Programming, Feature Driven Development, Scrum,
Test Driven Development.
I. INTRODUCTION
A system too large for one person to build is usually also
too large to build without an overall plan that coordinates
the people working on it, the tasks that need to be done, and
the artifacts that are produced. Researchers and practitioners
have identified a number of software development
formation Models for this coordination. Here are some of
the main ones. These formation Models are alternatives, but
not exclusive ones: most describe different aspects of a
formation, and it is common for a development group to be
following two or more simultaneously. For example,
• The sashimi formation is a way of organizing a
waterfall with feedback.
• Boehm's spiral Model example uses prototyping as the
Model for each cycle, and portions of a waterfall Model for
the delivered system stage of the prototyping Model
. • An incremental formation often uses a sashimi formation
for its Produce a build stage. Following is the classification
of different Software Formation Model.
1. Waterfall Model
2. Incremental Formation Model
2.1 Incremental Model
2.2 RAD Model
3. Evolutionary Formation Model
3.1 Prototyping
3.2 Spiral Model
3.3 Concurrent Model
Agile Methodologies are a group of software development
methods that are based on iterative and incremental
development. The four major characteristics that are
fundamental to all agile methodologies are: adaptive
planning, iterative & evolutionary development, rapid and
flexible response to change and promote communication
[1, 2]. Its main emphasis is in obeying the principles of
“Light but sufficient” and being people-oriented and
communication-centered. As it is named as lightweight
process, it is more suitable for the development of small
projects [3]. Agile software development takes the view
that production teams should start with simple and
predictable approximations to the final requirement and
then continue to increment the detail of these requirements
throughout the life of the development. This incremental
requirements refinement further refines the design, coding
and testing at all stages of production activity. In this way,
the requirements work product is as accurate and useful as
the final software itself [4].
All SDLC processes consist of a set of finite activities which
are used to develop a software product. A SDLC process
contains a complete plan for describing how to design,
develop, maintain and increase the efficiency of a software
product [5]. The SDLC process describes the methodologies
which improves overall software quality and development
process [6].
1.WATER FALL MODEL
The Waterfall Model was first Process Model to be
introduced. It is also referred to as a linear-sequential life
cycle model. It is very simple to understand and use. In a
waterfall model, each phase must be completed fully before
 Software process models- Agile models-SDLC(Software Development Life Cycle)
the next phase can begin. This type of model is basically
used for the for the project which is small and there are no
uncertain requirements. At the end of each phase, a review
takes place to determine if the project is on the right path
and whether or not to continue or discard the project. In this
model the testing starts only after the development is
complete. In waterfall model phases do not overlap [7].
Figure1.Waterfall-model[Adapted from Google image]
1.1 Benefit of waterfall model:
• It is simple and easy to understand and use
• It is easy to manage due to the rigidity of the
model each phase has specific deliverables
and a review process.
• In this model phases are processed and
complete done at a time. Phases do not
overlap.
• Waterfall model works well for smaller
projects where requirements are very well
understood.
1.2 Shortfalls of waterfall model:
• Once an application is in the testing stage, it is
very difficult to go back and change something
that was not well-thought out in the concept
stage.
• No working software is produced until late
during the life cycle.
• High amounts of risk and uncertainty.
• Not a good model for complex and object-
oriented projects.
• Poor model for long and ongoing projects.
• Not suitable for the projects where
requirements are at a moderate to high risk of
changing.
1.3 When to use the waterfall model:
• This model is used only when the requirements
are very well known, clear and fixed
• Product definition is stable.
• Technology is understood.
• There are no ambiguous requirements
• Ample resources with required expertise are
available freely
• The project is short.
2. INCREMENTAL FORMATION MODEL
2.1 Incremental Model:-
The model is a method of software development where the
model is designed, implemented and tested incrementally (a
little more is added each time) until the product is finished.
It involves both development and maintenance. The product
is defined as finished when it satisfies all of its
requirements. This model combines the elements of the
waterfall model with the iterative philosophy of prototyping
[10]. The product is decomposed into a number of
components, each of which are designed and built separately
(termed as builds). Each component is delivered to the client
when it is complete. This allows partial utilization of
product and avoids a long development time. It also creates
a large initial capital outlay with the subsequent long wait
avoided. This model of development also helps ease the
traumatic effect of introducing completely new system all at
once.
Figure2.Incremental-Model[Adapted from Google image]
2.1.1 Benefit of Incremental Model
• Generates working software quickly and early
during the software life cycle.
• More flexible – less costly to change scope and
requirements.
• Easier to test and debug during a smaller iteration.
• Easier to manage risk because risky pieces are
identified and handled during its iteration.
• Each iteration is an easily managed milestone
2.1.2 Shortfalls of Incremental Model
• Each phase of an iteration is rigid and do not
overlap each other.
• Problems may arise pertaining to system
architecture because not all requirements are
gathered up front for the entire software life
cycle
 Software process models- Agile models-SDLC(Software Development Life Cycle)
2.1.3 When to use Incremental Model
• Such models are used where requirements are
clear and can implement by phase wise. From
the figure it‟s clear that the requirements ® is
divided into R1, R2 to Rn and delivered
accordingly.
• Mostly such model is used in web applications
and product based companies.
2.2 RAD Model
RAD model is Rapid Application Development model. It is
a type of incremental model. In RAD model the components
or functions are developed in parallel as if they were mini
projects. The developments are time boxed, delivered and
then assembled into a working prototype. This can quickly
give the customer something to see and use and to provide
feedback regarding the delivery and their requirements.
Figure3. RAD Model[Adapted from Google image]
Business modeling: The information flow is identified
between various business functions.
Data modeling: Information gathered from business
modeling is used to define data objects that are needed for
the business.
Process modeling: Data objects defined in data modeling
are converted to achieve the business information flow to
achieve some specific business objective. Description are
identified and created for CRUD of data objects.
Application generation: Automated tools are used to
convert process models into code and the actual system.
Testing and turnover: Test new components and all the
interfaces
2.2.1 Benefit of the RAD model:
• Reduced development time.
• Increases reusability of components
• Quick initial reviews occur
• Encourages customer feedback
• Integration from very beginning solves a
lot of integration issues.
2.2.2 Shortfalls of RAD model:
• Depends on strong team and individual
performances for identifying business
requirements.
• Only system that can be modularized can
be built using RAD
• Requires highly skilled
developers/designers.
• High dependency on modeling skills
2.2.3 When to use RAD model:
• RAD should be used when there is a need
to create a system that can be modularized in
2-3 months of time.
• It should be used if there‟s high
availability of designers for modeling and
the budget is high enough to afford their cost
along with the cost of automated code
generating tools.
• RAD SDLC model should be chosen only
if resources with high business knowledge are
available and there is a need to produce the
system in a short span of time (2-3 months).
3. EVOLUTIONARY SOFTWARE FORMATION
MODEL
This approach is based on the idea of rapidly developing an
initial software implementation from very abstract
specifications and modifying this according to your
appraisal. Each program version inherits the best features
from earlier versions. Each version is refined based upon
feedback from yourself to produce a system which satisfies
your needs. At this point the system may be delivered or it
may be reimplemented using a more structured approach to
enhance robustness and maintainability. Specification,
development and validation activities are concurrent with
strong feedback between each. Evolutionary Software
Formation Model of following types of Models
3.1 Prototyping Model
The basic idea here is that instead of freezing the
requirements before a design or coding can proceed, a
throwaway prototype is built to understand the
requirements. This prototype is developed based on the
currently known requirements. By using this prototype, the
client can get an “actual feel” of the system, since the
interactions with prototype can enable the client to better
understand the requirements of the desired system.
Prototyping is an attractive idea for complicated and large
systems for which there is no manual formation or existing
system to help determining the requirements. The prototypes
are usually not complete systems and many of the details are
not built in the prototype. The goal is to provide a system
with overall functionality [8]
Figure 4.Prototype-Model[Adapted from Google image]
3.1.1 Fringe Benefit of Prototype Model:
• Users are actively involved in the development
• Since in this methodology a working Model of the
system is provided, the users get a better
understanding of the system being developed.
 Software process models- Agile models-SDLC(Software Development Life Cycle)
• Errors can be detected much earlier.
• Quicker user feedback is available leading to better
solutions.
• Missing functionality can be identified easily
• Confusing or difficult functions can be identified
Requirements validation, Quick implementation of
incomplete application.
3.1.2 Shortfalls of Prototype Model:
• Leads to implementing and then repairing way of
building systems.
• Practically, this methodology may increase the
complexity of the system as scope of the system may
expand beyond original plans.
• Incomplete application may cause application not
to be used as the full system was designed
Incomplete or inadequate problem analysis.
3.1.3 When to use Prototype Model:
• Prototype Model should be used when the
desired system needs to have a lot of
interaction with the end users.
• Typically, online systems, web interfaces
have a very high amount of interaction
with end users, are best suited for
Prototype Model. It might take a while for
a system to be built that allows ease of use
and needs minimal training for the end
user.
• Prototyping ensures that the end users
constantly work with the system and
provide a feedback which is incorporated
in the prototype to result in a useable
system. They are excellent for designing
good human computer interface systems
3.2 The Spiral Model
The Spiral Model is an evolutionary Software
Formation Model that couples the iterative
nature of prototyping with the controlled and
systematic aspects of the Linear Sequential
Model. Using the Spiral Model the software
is developed in a series of incremental
releases. Unlike the Iteration Model where in
the first product is a core product, in the
Spiral Model the early iterations could result
in a paper Model or a prototype. However,
during later iterations more complex
functionalities could be added [9].
Figure5.Spiral-Model [Adapted from Google
image]
A Spiral Model, combines the iterative nature
of prototyping with the controlled and
systematic aspects of the Waterfall Model,
therein providing the potential for rapid
development of incremental versions of the
software. A Spiral Model is divided into a
number of framework activities, also called task
regions. These task regions could vary from 3-6
in number and they are:
3.2.1 Benefit of the Spiral Model:-
• Realistic approach to the development
because the software evolves as the formation
progresses. In addition, the developer and the
client better understand and react to risks at
each evolutionary level.
• The Model uses prototyping as a risk
reduction mechanism and allows for the
development of prototypes at any stage of the
evolutionary development.
• It maintains a systematic stepwise approach,
like the classic waterfall Model, and also
incorporates into it an iterative framework
that more reflect the real world
3.2.2 Shortfalls of the Spiral Model :-
• One should possess considerable risk-
assessment expertise
• It has not been employed as much proven
Models (e.g. the Waterfall Model) and hence
may prove difficult to „sell‟ to the client.
3.3 Concurrent Development
Model The concurrent development Model - called
concurrent engineering. It provides an accurate state
of the current state of a project. Focus on concurrent
engineering activities in a software engineering
formation such as prototyping, analysis Modeling,
requirements specification and design. Represented
schematically as a series of major technical activities,
tasks and their associated states. Defined as a series
of events that trigger transitions from state to state for
each of the software engineering activities. Often
used as the paradigm for the development of
client/server applications. A client/server system is
composed of a set of functional components. When
applied to client/server, the concurrent formation
Model defines activities in two dimensions :
 Software process models- Agile models-SDLC(Software Development Life Cycle)
(i) System dimension -System level issues are
addressed using three activities: design, assembly,
and use.
(ii) The component dimension is addressed with two
activities: design and realization.
Two ways to achieve the concurrency:
System and component activities occur
simultaneously and can be modeling using the state-
oriented approach
Figure6.Concurrency-Model[Adapted from Google
image]
A typical client/server application is implemented
with many components, each can be designed and
realized concurrently. The concurrent formation
Model is applicable to all types of software
development and provides an accurate picture of the
current state of a project. Rather than confining
software engineering activities to a sequence of
events, it defines a network of activities. Each
activity on the network exists simultaneously with
other activities. Events generated within a given
activity or at some other place in the activity network
trigger transitions among the states of an activity[10].
II.AGILE MODELS
The meaning of Agile is swift or versatile."Agile process
model" refers to a software development approach based on
iterative development. Agile methods break tasks into
smaller iterations, or parts do not directly involve long term
planning. The project scope and requirements are laid down
at the beginning of the development process. Plans
regarding the number of iterations, the duration and the
scope of each iteration are clearly defined in advance.
Each iteration is considered as a short time "frame" in the
Agile process model, which typically lasts from one to four
weeks. The division of the entire project into smaller parts
helps to minimize the project risk and to reduce the overall
project delivery time requirements. Each iteration involves a
team working through a full software development life cycle
including planning, requirements analysis, design, coding,
and testing before a working product is demonstrated to the
client.[11]
Phases of Agile Model:
Following are the phases in the Agile model are as follows:
1. Requirements gathering
2. Design the requirements
3. Construction/ iteration
4. Testing/ Quality assurance
5. Deployment
6. Feedback
Figure7 Agile Model [Adapted from Google image]
1. Requirements gathering: In this phase, you must define
the requirements. You should explain business opportunities
and plan the time and effort needed to build the project.
Based on this information, you can evaluate technical and
economic feasibility.
2. Design the requirements: When you have identified the
project, work with stakeholders to define requirements. You
can use the user flow diagram or the high-level UML
diagram to show the work of new features and show how it
will apply to your existing system.
3. Construction/ iteration: When the team defines the
requirements, the work begins. Designers and developers
start working on their project, which aims to deploy a
working product. The product will undergo various stages of
improvement, so it includes simple, minimal functionality.
4. Testing: In this phase, the Quality Assurance team
examines the product's performance and looks for the bug.
5. Deployment: In this phase, the team issues a product for
the user's work environment.
6. Feedback: After releasing the product, the last step is
feedback. In this, the team receives feedback about the
product and works through the feedback.
Agile Testing Methods:
• Scrum
• Crystal
• Dynamic Software Development Method(DSDM)
• Feature Driven Development(FDD)
• Lean Software Development
 Software process models- Agile models-SDLC(Software Development Life Cycle)

• eXtreme Programming(XP) 4) Feature Driven Development(FDD):

1) Scrum This method focuses on "Designing and Building" features.
In contrast to other smart methods, FDD describes the small
SCRUM is an agile development process focused primarily
steps of the work that should be obtained separately per
on ways to manage tasks in team-based development
function.
conditions.
5) Lean Software Development:
There are three roles in it, and their responsibilities are:
Lean software development methodology follows the
• Scrum Master: The scrum can set up the master principle "just in time production." The lean method
team, arrange the meeting and remove obstacles for indicates the increasing speed of software development and
the process reducing costs. Lean development can be summarized in
seven phases.
• Product owner: The product owner makes the
product backlog, prioritizes the delay and is 1. Eliminating Waste
responsible for the distribution of functionality on 2. Amplifying learning
each repetition.
3. Defer commitment (deciding as late as possible)
• Scrum Team: The team manages its work and
organizes the work to complete the sprint or cycle. 4. Early delivery

2) Crystal: 5. Empowering the team

There are three concepts of this method- 6. Building Integrity
1. Chartering: Multi activities are involved in this 7. Optimize the whole
phase such as making a development team,
6) eXtreme Programming(XP)
performing feasibility analysis, developing plans,
etc. This type of methodology is used when customers are
constantly changing demands or requirements, or when they
2. Cyclic delivery: under this, two more cycles are not sure about the system's performance.
consist, these are:
A. Team updates the release plan. When to use the Agile Model?
B. Integrated product delivers to the users. • When frequent changes are required.

3. Wrap up: According to the user environment, this • When a highly qualified and experienced team is
phase performs deployment, post-deployment. available.
3) Dynamic Software Development Method(DSDM): • When a customer is ready to have a meeting with a
DSDM is a rapid application development strategy for software team all the time.
software development and gives an agile project distribution • When project size is small.
structure. The essential features of DSDM are that users
must be actively connected, and teams have been given the
right to make decisions. The techniques used in DSDM are: Advantage(Pros) of Agile Method:
1. Frequent Delivery
1. Time Boxing
2. Face-to-Face Communication with clients.
2. MoSCoW Rules
3. Efficient design and fulfils the business
3. Prototyping
requirement.
The DSDM project contains seven stages: 4. Anytime changes are acceptable.
1. Pre-project 5. It reduces total development time.
2. Feasibility Study
Disadvantages(Cons) of Agile Model:
3. Business Study
1. Due to the shortage of formal documents, it creates
4. Functional Model Iteration
confusion and crucial decisions taken throughout
5. Design and build Iteration
various phases can be misinterpreted at any time by
6. Implementation different team members.
7. Post-project
 Software process models- Agile models-SDLC(Software Development Life Cycle)
2. Due to the lack of proper documentation, once the
project completes and the developers allotted to
another project, maintenance of the finished project
can become a difficulty.
III.SDLC (Software Development Life Cycle)
Software Development Life Cycle (SDLC) is a process used
by the software industry to design, develop and test high
quality software. The SDLC aims to produce a high-quality
software that meets or exceeds customer expectations,
reaches completion within times and cost estimates.[12]
• SDLC is the acronym of Software Development
Life Cycle.
• It is also called as Software Development Process.
• SDLC is a framework defining tasks performed at
each step in the software development process.
• ISO/IEC 12207 is an international standard for
software life-cycle processes. It aims to be the
standard that defines all the tasks required for
developing and maintaining software.
What is SDLC?
SDLC is a process followed for a software project, within a
software organization. It consists of a detailed plan
describing how to develop, maintain, replace and alter or
enhance specific software. The life cycle defines a
methodology for improving the quality of software and the
overall development process[7].
The following figure is a graphical representation of the
various stages of a typical SDLC
Figure 8. SDLC [Adapted from Google image]
A typical Software Development Life Cycle consists of the
following stages −
Stage 1: Planning and Requirement Analysis
Requirement analysis is the most important and fundamental
stage in SDLC. It is performed by the senior members of the
team with inputs from the customer, the sales department,
market surveys and domain experts in the industry. This
information is then used to plan the basic project approach
and to conduct product feasibility study in the economical,
operational and technical areas.
Planning for the quality assurance requirements and
identification of the risks associated with the project is also
done in the planning stage. The outcome of the technical
feasibility study is to define the various technical
approaches that can be followed to implement the project
successfully with minimum risks.
Stage 2: Defining Requirements
Once the requirement analysis is done the next step is to
clearly define and document the product requirements and
get them approved from the customer or the market analysts.
This is done through an SRS (Software Requirement
Specification) document which consists of all the product
requirements to be designed and developed during the
project life cycle.
Stage 3: Designing the Product Architecture
SRS is the reference for product architects to come out with
the best architecture for the product to be developed. Based
on the requirements specified in SRS, usually more than one
design approach for the product architecture is proposed and
documented in a DDS - Design Document Specification.
This DDS is reviewed by all the important stakeholders and
based on various parameters as risk assessment, product
robustness, design modularity, budget and time constraints,
the best design approach is selected for the product.
A design approach clearly defines all the architectural
modules of the product along with its communication and
data flow representation with the external and third party
modules (if any). The internal design of all the modules of
the proposed architecture should be clearly defined with the
minutest of the details in DDS.
Stage 4: Building or Developing the Product
In this stage of SDLC the actual development starts and the
product is built. The programming code is generated as per
DDS during this stage. If the design is performed in a
detailed and organized manner, code generation can be
accomplished without much hassle.
Developers must follow the coding guidelines defined by
their organization and programming tools like compilers,
interpreters, debuggers, etc. are used to generate the code.
Different high level programming languages such as C,
C++, Pascal, Java and PHP are used for coding. The
programming language is chosen with respect to the type of
software being developed.
Stage 5: Testing the Product
This stage is usually a subset of all the stages as in the
modern SDLC models, the testing activities are mostly
involved in all the stages of SDLC. However, this stage
refers to the testing only stage of the product where product
 Software process models- Agile models-SDLC(Software Development Life Cycle)

defects are reported, tracked, fixed and retested, until the

product reaches the quality standards defined in the SRS.
Stage 6: Deployment in the Market and Maintenance
Once the product is tested and ready to be deployed it is
released formally in the appropriate market. Sometimes
product deployment happens in stages as per the business
strategy of that organization. The product may first be
released in a limited segment and tested in the real business
environment (UAT- User acceptance testing).

Then based on the feedback, the product may be released as

it is or with suggested enhancements in the targeting market
segment. After the product is released in the market, its
maintenance is done for the existing customer base.

SDLC Models

There are various software development life cycle models

defined and designed which are followed during the
software development process. These models are also
referred as Software Development Process Models". Each
process model follows a Series of steps unique to its type to
ensure success in the process of software development[4]

Following are the most important and popular SDLC

models followed in the industry −

• Waterfall Model
• Iterative Model
• Spiral Model
• V-Model
• Big Bang Model
Other related methodologies are Agile Model, RAD Model,
Rapid Application Development and Prototyping
Models.[1,2,3]

REFERENCES
[1] Pankaj Jalote, An Integrated Approach to Software
Engineering, 3rd Edition, Narosa Publishing
House, ISBN: 9788173197024..
[2] Rajib Mall, Fundamentals of Software Engineering,
3rd Edition, PHI Learning Pvt Ltd, ISBN:
9788120338197.
[3] . . Rohit Khurana, Software Engineering: Principles
and Practices, 2nd Edition, Vikas Publishing House
Pvt Ltd, ISBN: 8125939466
[4] https://aws.amazon.com/what-
is/sdlc/#:~:text=The%20software%20development
%20lifecycle%20(SDLC,expectations%20during%
20production%20and%20beyond.
[5] www.1000sourcecodes.com/2012/05/software-
engineering-incremental-model.html
[7] National Instruments Corporation, "Lifecycle
Models", 2006 , http://zone.ni.com.