Scribd
Upload
91 views

Spiral Model Is A Risk-Driven Software Development Process

The Spiral Model is a risk-driven software development process that combines elements of the waterfall model and iterative development. It consists of four phases - objectives/alternatives determination, risk identification/resolution, development, and review/planning - completed in iterative spirals. Each spiral adds more functionality to the software until it is ready for production. The model helps adopt processes based on a project's unique risk patterns to ensure efficient development.

Uploaded by

gulzar ahmad
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
91 views

Spiral Model Is A Risk-Driven Software Development Process

The Spiral Model is a risk-driven software development process that combines elements of the waterfall model and iterative development. It consists of four phases - objectives/alternatives determination, risk identification/resolution, development, and review/planning - completed in iterative spirals. Each spiral adds more functionality to the software until it is ready for production. The model helps adopt processes based on a project's unique risk patterns to ensure efficient development.

Uploaded by

gulzar ahmad
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 4

Spiral Model 

is a risk-driven software development process


model. It is a combination of waterfall model and iterative
model. Spiral Model helps to adopt software development
elements of multiple process models for the software project
based on unique risk patterns ensuring efficient development
process.
Each phase of spiral model in software engineering begins
with a design goal and ends with the client reviewing the
progress. The spiral model in software engineering was first
mentioned by Barry Boehm in his 1986 paper.
The development process in Spiral model in SDLC, starts with
a small set of requirement and goes through each
development phase for those set of requirements. The
software engineering team adds functionality for the additional
requirement in every-increasing spirals until the application is
ready for the production phase. The below figure very well
explain Spiral Model:

Each phase of Spiral Model is divided into four quadrants as


shown in the above figure. The functions of these four quadrants
are discussed below-
1. Objectives determination and identify alternative
solutions: Requirements are gathered from the customers
and the objectives are identified, elaborated and analyzed at
the start of every phase. Then alternative solutions possible
for the phase are proposed in this quadrant.
2. Identify and resolve Risks: During the second quadrant
all the possible solutions are evaluated to select the best
possible solution. Then the risks associated with that solution
is identified and the risks are resolved using the best possible
strategy. At the end of this quadrant, Prototype is built for the
best possible solution.
3. Develop next version of the Product: During the third
quadrant, the identified features are developed and verified
through testing. At the end of the third quadrant, the next
version of the software is available.
4. Review and plan for the next Phase: In the fourth
quadrant, the Customers evaluate the so far developed
version of the software. In the end, planning for the next
phase is started.

Example of the Spiral model


Let us see one example for a better understanding of the spiral model:

In the spiral model, the software is developed in the small modules.


Suppose we have the application A and this A application is created
with the help of different models as P, Q, R.
RP: the requirement analysis of module P, similarly with RQ, RR.

DP: Design of module P, and similarly with DQ, DR.

CP: Coding of module P, and similarly CQ, CR.

TP: Testing of module P, and similarly TQ, TR.

o In the P module, we get the requirement first, and then only we


design the module. And the coding part of module A is done
when it is tested for bugs.

o The next module is Q, and it has been created when the module
P has been built. We follow the same process as we did in
module P, but when we start testing the module Q, and we check
the following condition such as:

o Test the Q module

o The test integration of module Q with P

o Test module P
o After creating the module P, Q, we will proceed to the module R,
where we will then follow the same process as module P and Q,
and then test the following conditions:

o First, check the module as R, Q, and P

o Then, check the integration of module in the below order:


R → Q, R and P → P and Q

You might also like