Copyright Protected

copyright © 1996, 2001, 2005

R.S. Pressman & Associates, Inc.

For University Use Only

May be reproduced ONLY for student use at the university level
when used in conjunction with Software Engineering: A Practitioner's Approach.
Any other reproduction or use is expressly prohibited.

These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 6/e and are provided with
permission by R.S. Pressman & Associates, Inc., copyright © 1996, 2001, 2005
1
 Supplementary Slides for
Software Engineering:
A Practitioner's Approach, 7/e

Chapter 2
Spiral Process Model
Muhammad Imran Saeed
Assistant Professor,
Department of Computer Science and Software Engineering,
International Islamic University, Islamabad

These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 6/e and are provided
with permission by R.S. Pressman & Associates, Inc., copyright © 1996, 2001, 2005 2
 Objectives
 The Spiral Model
 When to use Spiral?
 How it Works
 Spiral Model Phases
 When to Use Spiral Model
 Example of Spiral Model
 Advantages of RAD Model
 Disadvantages of RAD Model

3
 The Spiral Model
• Spiral Model is a combination of a waterfall
model and iterative model.
• Each phase in spiral model begins with a
design goal and ends with the client reviewing
the progress.
• The development team in Spiral-SDLC model
starts with a small set of requirement and goes
through each development phase for those set
of requirements.

4
 The Spiral Model
• The software engineering team adds
functionality for the additional requirement in
every-increasing spirals until the application is
ready for the production phase.

5
 How it Works
planning
estimation
scheduling
risk analysis

communication

modeling
analysis
design
start

deployment
construction
delivery
code
feedback test

6
How it Works

7
 Spiral Model Phases

Planning:
• It includes estimating the cost, schedule and
resources for the iteration.
• It also involves understanding the system
requirements for continuous communication
between the system analyst and the customer

8
 Spiral Model Phases (Cont..)
Risk Analysis:
• Identification of potential risk is done while risk
mitigation strategy is planned and finalized
Engineering:
• It includes testing, coding and deploying software
at the customer site
Evaluation:
Evaluation of software by the customer. Also, includes
identifying and monitoring risks such as schedule
slippage and cost overrun
9
 When to Use Spiral Model?

• When project is large

• When releases are required to be frequent
• When creation of a prototype is applicable
• When risk and costs evaluation is important
• For medium to high-risk projects
• When requirements are unclear and complex
• When changes may require at any time

10
Example of Prototype process

Microsoft Windows

11
 Advantages of Prototype Model
• Additional functionality or changes can be
done at a later stage
• Development is fast and features are added
in a systematic way
• There is always a space for customer
feedback
• Cost estimation becomes easy as the
prototype building is done in small fragments

12
 Disadvantages of Prototype Model
• Risk of not meeting the schedule or budget
• It works best for large projects only also
demands risk assessment expertise
• For its smooth operation spiral model protocol
needs to be followed strictly
• It is not advisable for smaller project, it might
cost them a lot

13
 Advice

• Study these Lecture along with prescribed

Book for a better understanding as well as
preparation for Exam.

THANK YOU

14