Spiral Model In Software
Engineering
Siddhi Rane
Student of Computer Engineering at Mumbai University, Mumbai,
India siddhi.rane@sakec.ac.in
Abstract – The primary
purpose of this paper is to
explore about the Spiral
Model in Software
Engineering. In the 1980s
Boehm developed a spiral
model known as the cycle
model. The spiral model
involves spiral-organized
operations, which has several
cycles. This model
incorporates the features of
the model for prototyping
and the model for waterfall
and is useful for large,
complex and costly projects.
It decides issues with the
specifications in designing
the prototypes. The spiral
model's goal is to emphasize
management in the software
project to assess and solve
risks. Project overruns,
modified specifications, loss
of key project staff, delay of
required resources, rivalry
with other software
developers and technical
breakthroughs rendering the
project redundant are
various areas of risk in the
software project.
Keywords – The Spiral
Model , Waterfall Model.
I. INTRODUCTION
The spiral model blends the
concept of iterative growth
with the waterfall model's
systematic, controllable
aspects. This Spiral model is a
mixture of the iterative process
development model with the
sequential linear development
model i.e. the waterfall model
with a very high risk analysis
focus. It allows for incremental
product launches or
incremental improvements
with any iteration around the
spiral.
A spiral model  is a
combination of sequential and
prototype models. This model
is best used for large projects
which involve continuous
enhancements. There are
specific activities that are done
in one iteration (spiral) where
the output is a small prototype
of the large software. The
same activities are then
repeated for all the spirals until
the entire software is built.
DATA STRUCTURE
DESIGN
There are four stages of the
spiral pattern. Through cycles
called Spirals a program
process repeatedly goes
through these stages.
Identification : This process
starts with the compilation of
the spiraling market
requirements. The definition of
device specifications, module
specifications, and unit
requirements are all achieved
in this step in the ensuing
spirals as the software matures.
This process also involves first run, and provides
understanding the feedback.
specifications of the system
through constant contact with
the client and the program
analyst. The commodity is
placed on the marked market
at the end of the spiral.

Design : The design process

starts with the conceptual
design in the baseline spiral
and includes the architectural
design, the logical design of
the components, the design of
the physical product and the
final design in the following
spirals.

Construct or Build : The

Construction process refers to
the actual software product
being created at each spiral. In
the baseline spiral, a POC
(Proof of Concept) is created
in this process where the
product is only being thought
about and the design is being
created to get consumer
feedback. II. APPLICATIONS

Instead a working model of the The Spiral Model is commonly

program called create with a
version number is created in
the subsequent spirals with
greater clarification about
specifications and design
information. Those builds are
sent for reviews to the
consumer.
Evaluation and Risk
Management : Risk
Assessment involves the
detection, assessment and
analysis of technical viability
and risk management, such as
slippage schedules and cost
overruns. Upon reviewing the
design, the customer reviews
the program at the end of the
used in the software industry
because it is in line with any
product's natural development
cycle, i.e. learning at maturity
which entails minimal risk to
both the customer and the
development firms.
The following pointers
illustrate the usual uses of a
Spiral Model –
 When a budget
constraint occurs and
risk assessment is
relevant.
 For projects which are
of medium to high
risk.
 Long-term project
commitment as the
criteria shift over time
due to future changes
to economic priorities.
 Consumer is not sure
what is normally the
case for their
specifications.
 Requirements are
nuanced, and
clarification requires
evaluation.
 New product line that
should be launched in
stages to get enough
input from customers.
 Throughout the
production process
major changes are
anticipated inside the
product.
III. ADVANTAGES AND risky components can
DISADVANTAGES be built earlier which
helps to improve risk
The benefit of the spiral management.
lifecycle model is that as it is
accessible or known it allows The Spiral SDLC model's
elements of the product to be drawbacks are as follows –
put in. This means the  Management is more
previous specifications and complex.
specification are not in  It may not be possible
conflict. to know the end of the
project early.
This strategy is compatible  Not suitable for
with methods that have several projects at medium or
builds and releases of software low risk, and may be
to allow for an orderly costly for small
transition to a maintenance projects.
operation. Another positive  Spiral process is
aspect of this approach is that complex, can continue
the spiral model requires an indefinitely.
early participation of users in  Excessive
the effort to improve the documentation is
program. needed for large
numbers of
On the other hand, completing intermediate stages.
such items requires very strict
management and there is a
chance of running the spiral in IV. CONCLUSION
an infinite loop. Therefore, the
discipline of change and the The purpose of this paper is
degree to which requests for to explore the Spiral Model of
change are taken is very Software Engineering. Each
necessary in order to spiral can be termed as a loop
effectively create and launch and each loop is a separate
the product. development process in a
spiral model.
The benefits of the Spiral The four tasks (planning, risk a
SDLC model are as follows – nalysis, development, and eval
uation) form a 
 It is possible to meet
spiral model's intermediate pha
evolving requirements.
ses and are repeated with each 
 Requires thorough
loop again. 
prototyping.
 More reliably This model is also useful for la
recording rger projects where smaller pro
requirements. totypes can 
 Users look early on at be created and distributed, and 
the program. can be improved to make the la
 Technology can be rger version. 
divided into smaller Implementing this model need
components and the s skilled resources because risk 
analysis is a very important par system integration in
t of  the system
this model and risk analysis re development process:
quires skills and as a result this  A new look",
model is costly. Washington, DC:
National Academy
This invariant illustrates the Press
overall system's significance,
and the long-term problems
that span the entire life cycle.
This excludes "hazardous
spiral look-alike" which
focuses too much on initial
software code creation. Such
processes may arise from
following established
approaches to an analysis and
design of object-oriented or
structured software, while
neglecting certain aspects of
the process needs of the
project.

V. REFERENCES

1.  Boehm, B, "Spiral
Development:
Experience,
Principles,and
Refinements", Special
Report CMU/SEI-
2000-SR-008, July
2000
2. ^ Boehm B, "A Spiral
Model of Software
Development and
Enhancement", ACM
SIGSOFT Software
Engineering Notes,
ACM, 11(4):14-24,
August 1986
3. ^ Jump up to:a b Boehm
B, "A Spiral Model of
Software Development
and Enhancement",
IEEE Computer,
IEEE, 21(5):61-72,
May 1988
4. ^ Pew RW, & Mavor
AS (Eds.).
(2007). "Human-