Spiral Software Developmental

Developmental Methodologies
 Spiral Model
• The spiral model is a software development process combining elements of
both design and prototyping-in-stages, in an effort to combine advantages of
top-down and button up concepts. Also known as the spiral lifecycle model
(or spiral development), it is a systems development method (SDM) used in
information technology (IT). This model of development combines the
features of the prototyping and the waterfall model. The spiral model is
intended for large, expensive and complicated projects.
 Spiral Model
• History
• This model was defined by Barry Boehm in his 1986 article "A Spiral Model
of Software Development and Enhancement".
• As originally envisioned, the iterations were typically 6 months to 2 years
long. Each phase starts with a design goal and ends with the client (who may
be internal) reviewing the progress thus far. Analysis and engineering efforts
are applied at each phase of the project, with an eye toward the end goal of
the project.
 Steps:

• Determine the objectives, alternatives, and constraints on the new iteration.

• Evaluate alternatives and identify and resolve risk issues.
• Develop and verify the product for this iteration.
• Plan the next iteration.
 Spiral Model
• The Spiral model is most often implemented in large projects with high risk and
needs constant review to stay on target. For smaller projects, the concept of agile
software development is becoming a viable alternative.
• Estimates (i.e. budget, schedule, etc.) get more realistic as work progresses, because
important issues are discovered earlier.
• It is more able to cope with the (nearly inevitable) changes that software
development generally entails.
• Software engineers (who can get restless with protracted design processes) can get
their hands in and start working on a project earlier.
Now let’s discuss the advantages and disadvantages
of Spiral Model in detail.
 Advantages of Spiral Model

• 1) Spiral Life Cycle Model is one of the most flexible SDLC models in place. Development
phases can be determined by the project manager, according to the complexity of the project.
2) Project monitoring is very easy and effective. Each phase, as well as each loop, requires a
review from concerned people. This makes the model more transparent.
3) Risk management is one of the in-built features of the model, which makes it extra attractive
compared to other models.
4) Changes can be introduced later in the life cycle as well. And coping with these changes isn’t a
very big headache for the project manager.
5) Project estimates in terms of schedule, cost etc become more and more realistic as the project
moves forward and loops in spiral get completed.
6) It is suitable for high risk projects, where business needs may be unstable.
7) A highly customized product can be developed using this.
 Disadvantages of Spiral Model

• 1) Cost involved in this model is usually high.

2) It is a complicated approach especially for projects with a clear SRS.
3) Skills required, to evaluate and review project from time to time, need expertise.
4) Rules and protocols should be followed properly to effectively implement this model.
Doing so, through-out the span of project is tough.
5) Due to various customizations allowed from the client, using the same prototype in other
projects, in future, is difficult.
6) It is not suitable for low risk projects.
7) Meeting budgetary and scheduling requirements is tough if this development process is
followed.
8) Amount of documentation required in intermediate stages makes management of
project very complex affair.
 Spiral Model Diagram 2

• The radical dimension in figure 2 represents the cumulative costs incurred in

accomplishing the steps to date ; the angular dimension represents the
progress made in completing each cycle of the spiral model. the spiral
model reflects the underlying concept that each cycle involves the
progression that addresses the same sequence of steps .For each portion of
the product and for each of each individual the level of elaboration from an
overall concept of operation document down to the coding of each
individual program.
• A typical cycle of the spiral. Each cycle of the spiral begins with the
identification of:
• the objectives of the portion of the product being being elaborated
(performance, functionality, ability to accommodate change)
• The alternative means of implementing this portion of the product (design
A, design, Reuse).
• The constrains imposed on the application of the alternative (cost, schedule,
interface).