Scribd
Upload
493 views2 pages

Spiral Model

The spiral model is a risk-driven software development process that consists of four phases - planning, risk analysis, development and evaluation - that are repeated in iterations or spirals. It emphasizes risk analysis at each phase of the project through prototyping to allow for revisions based on stakeholder feedback and reduces risks. The spiral model is suited for medium to high risk projects where requirements are uncertain.

Uploaded by

MNaveedsdk
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
493 views2 pages

Spiral Model

The spiral model is a risk-driven software development process that consists of four phases - planning, risk analysis, development and evaluation - that are repeated in iterations or spirals. It emphasizes risk analysis at each phase of the project through prototyping to allow for revisions based on stakeholder feedback and reduces risks. The spiral model is suited for medium to high risk projects where requirements are uncertain.

Uploaded by

MNaveedsdk
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/ 2

Spiral Model

A risk-driven software process framework (the spiral model) was proposed by Barry Boehm in
1988. It integrates risk management and incremental development. The software process is
represented as a spiral rather than a sequence of activities with some backtracking from one
activity to another. Each loop in the spiral represents a phase of the software process. Thus, the
innermost loop might be concerned with system feasibility, the next loop with requirements
definition, the next loop with system design and so on. The spiral model combines change
avoidance with change tolerance. It assumes that changes are a result of project risks and
includes explicit risk management activities to reduce these risks.

The spiral model has four phases. A software project repeatedly passes through these phases in
iterations called Spirals.

The Radius of the spiral at any point represents the expenses (cost) of the project, and the angular
dimension represents the progress made so far in the current phase.

1. Objectives determination and identify alternative constraints: Requirements are


gathered from the customers and the objectives are identified, elaborated and analyzed at
the start of every phase. Project risks are identified. Alternative strategies, depending on
these risks, may be planned.
2. Identify and resolve Risks: For each of the identified project risks, a detailed analysis is
carried out. Steps are taken to reduce the risk. For example, if there is a risk that the
requirements are inappropriate, a prototype system may be developed.
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.

Advantages

 Provides early indication of the risks, without involving much cost.


 Users can view the system early because of the rapid prototyping tools.
 Critical high-risk functions are developed first.
 The design does not have to be perfect.
 Users can be closely involved in all lifecycle steps.
 Early and frequent feedback from users.
 Cumulative costs assessed frequently.

Disadvantages

 Management is more complex.

 End of the project may not be known early.

 Not suitable for small or low risk projects and could be expensive for small projects.

 Spiral model is complex to understand for new team members.

 Risk assessment expertise is required.

 Spiral may continue indefinitely.

 Developers must be reassigned during non-development phase activities.

When to Use Spiral Model?

 Creation of a prototype is appropriate.


 When there is a budget constraint and risk evaluation is important.
 A project is of medium to high-risk.
 Users are unsure of their needs.
 Requirements are complex.
 Product-line is new.
 Significant changes are expected during exploration.
 Long-term project commitment unwise because of potential business changes.

You might also like