EVOLUTIONARY PROCESS MODEL

Review Exercise -2
 EVOLUTIONARY PROCESS MODEL
The Spiral Model

Originally proposed by Berry Boehm in 1988

⚫ Process is represented as a spiral rather than as a

sequence of activities with backtracking

⚫ Each loop in the spiral represents a phase in the

process.
✓ the innermost loop might be concerned with
system feasibility,
✓ the next loop with system requirements
definition,
✓ the next loop with system design and so on
 Spiral model of the software process
Commulative Cost
Progress
Determine Objectives, through Evaluate alternatives,
steps
alternatives, Identify, resolve risks
Risk
analys is
constraints Risk
analys is
Risk
analys is Opera-
Prototyp e tional

Risk
Prototyp e 3 protoyp e

Commitment REVIEW analysis Proto-

ty pe 2
1 Sim
Ratio Requi rements pl an
Life-cycle plan Concept o f
ul ati ons, m odels, b en ch marks

Operation S/W
requi rements Prod uct
design Detailed
Requi rement desi gn
Develop ment
pl an valid ati on Code
Desi gn Uni t t es t
Integrati on
and test p lan V&V Integr ation
Plan next phases Accep tance test
test
Serv ice Develop, verify next-
level product
 Spiral Model
⚫ Spiral Model is cyclic in nature
⚫ Each cycle of the spiral consists of four stages, and each
stage is represented by one quadrant
⚫ The radius of the spiral represents the cost accumulated
so far in the process and the angular dimension
represents the progress in the process
⚫ The focus is the identification of problems and the
classification of these into different levels of risks -
aim eliminate high-risk problems before they threaten
Spiral Model
⚫ Each phase is completed with a review of all
products developed up to that point and includes the
plans for the next cycle
⚫ These plans may include partition of the product in
smaller portions for development that are
implemented by individual groups or persons
⚫ Spiral Model may be viewed as Metamodel because it
becomes equivalent to another life cycle model in
appropriate situations
PLANNING RISK

Planning based on Risk Analysis Based

customer commitment on Initial
Initial Requirements Requirements Risk Analysis Based
Gathering and Project on customer reaction
Planning

Go/No Go
Decision

Initial Software Prototype

Next Level Prototype

Customer
Evaluation Engineered System

CUSTOMER ENGINEERING
SIMPLIFIED
VIEW
SIMPLIFIED VIEW OF SPIRAL MODEL
 Spiral Model
Quadrant 1 : Determine Objectives, alternatives and
constraints
⚫ Objectives such as performance, functionality, ability to
accommodate change, hardware/software interface, and
critical success factors are identified.
⚫ Alternative means of implementing this portion of the
product are determined constraints imposed on the
application of the alternatives (cost, schedule, interface,
environmental limitations, etc.) are determined
⚫ Risks associated with lack of experience, new technology,
tight schedules, poor processes and so on are
documented
Spiral Model
Quadrant 2 : Evaluate alternatives, and identify and resolve
risks
⚫ Alternatives relative to the objectives and constraints are
evaluated
⚫ The identification and resolution of risks (risk management,
cost-effective strategy for resolving sources, evaluation of
remaining risks where money could be lost by continuing
system development[go/no go decisions,] etc. ) occurs
 Spiral Model
Quadrant 3 : Develop Next Level Product
Typical activities in this quadrant could be
• Creation of a design,
• Review of Design
• Development of code
• Inspection of Code
• Testing and packaging of the product.

⚫ The first build is the customer’s first look at the system.

⚫ With each subsequent build, a better idea of customer
requirements is developed.
⚫ The degree of change form one build to the next diminishes
with each build, eventually resulting in an operational system
Spiral Model
Quadrant 4 : Plan Next Phase
Typical activities in this quadrant could be
• Development of the Project Plan
• Development of the Configuration Management plan
• Development of the Test Plan
• Development of the Installation Plan
 Spiral Model : Strengths
⚫ The spiral model allows users to see the system early, through
the use of rapid prototyping in the development life cycle
⚫ It provides early indications of insurmountable risks, without
much cost
⚫ It allows users to be closely tied to all planning, risk analysis,
development and evaluation activities
⚫ It splits a potentially large development effort into small
chunks in which critical, high-risk functions are implemented
first, allowing the continuation of the project to be optional i.e.
Advantage of Incremental release
 Spiral Model : Strengths
⚫ It provides early and frequent feedback from users to
developers, ensuring a correct product with high quality
⚫ Management control of quality, correctness, cost schedule, and
staffing is improved through review at the conclusion of each
iteration
⚫ It provides productivity improvement through reuse capabilities
⚫ All money needed for the project need not be allocated up-front
⚫ Commutative costs may be assessed frequently and a decrease
in risk is associated with the cost
Spiral Model : Weaknesses
⚫ If the project is low-risk or small, this model can be an
expensive one. The time spent evaluating the risk after each
spiral is costly
⚫ The model is complex and developers, managers and
customers may find it too complicated to use
⚫ Considerable risk assessment expertise is required
⚫ The spiral may continue indefinitely, generated by each of the
customer’s responses to the build initiating a new cycle -
closure may be difficult to achieve
⚫ It can be hard to define objective, verifiable milestones that
indicate readiness to proceed through the next iteration
 When to use Spiral Model
⚫ For projects that represent a medium to high risk
⚫ When it is unwise to commit to a long-term project due to
potential changes in economic priorities and when these
uncertainties may limit the available time frame
⚫ When it is important to focus on stable or known parts while
gathering knowledge about changing parts.
⚫ When new technologies are being employed, such as first-time
object oriented approaches
Some Examples of Spiral Model
⚫ Microsoft used it to develop early versions of
Windows.
⚫ The Gantt Chart Software was also made using
spiral model.
⚫ Game development is another industry that uses
spiral model to develop the games.
• As the gaming industry highly depend upon
the early versions, at such time spiral model
is a solid option.
• With Spiral Model, the game development
industries can get the feedback from their
customers at fast and can develop the game
as per their convenient.
Some Examples of Spiral Model
⚫ The development of an Air Traffic Control
System.
✓ Such a system is vital for the safety of
thousands of flights daily. Any malfunction
or failure can have catastrophic
consequences.
✓ The Spiral Model, with its focus on risk
assessment and iterative testing, ensures
that the system is robust and reliable