spiral model
TRANSCRIPT
SPIRAL MODEL(SDLC)
Inam Ul-Haq
Lecturer in Computer Science
University of Education, Okara Campus
Submitted by:
Hira Mehar
Roll No. 3006
BS-IT-Eve
IV Semester
Un
ive
rsity
of
Ed
uca
tion
Oka
ra
Ca
mp
us
1
Introduction
In this system development method, we combine the features of both, prototype model and waterfall model.
Un
ive
rsity
of
Ed
uca
tion
Oka
ra
Ca
mp
us
2
Introduction• In spiral model we can arrange all the
activities in the form of a spiral
• A spiral model is divided into number of framework activities, called task regions
• Typically, there are between three and six task regions
Un
ive
rsity
of
Ed
uca
tion
Oka
ra
Ca
mp
us
3
Why Spiral Model ???
4
Un
ive
rsity
of
Ed
uca
tion
Oka
ra
Ca
mp
us
Why Spiral Model ???
5
Un
ive
rsity
of
Ed
uca
tion
Oka
ra
Ca
mp
us
Why Spiral Model ???
6
Un
ive
rsity
of
Ed
uca
tion
Oka
ra
Ca
mp
us
History• The spiral model was
defined by Barry Boehm in his 1988 article.
• This model was not the first model to discuss iterative development, but it was the first model to explain why the iteration matters.
7
Un
ive
rsity
of
Ed
uca
tion
Oka
ra
Ca
mp
us
Spiral Model
8
Un
ive
rsity
of
Ed
uca
tion
Oka
ra
Ca
mp
us
Phases•Customer Communication•Planning•Risk Analysis•Engineering•Customer Evaluation
9
Un
ive
rsity
of
Ed
uca
tion
Oka
ra
Ca
mp
us
Customer Communication
• Includes understanding the system requirements by continuous communication between the customer and the system analyst.
10
Un
ive
rsity
of
Ed
uca
tion
Oka
ra
Ca
mp
us
Planning• Task required to define resources, timelines and other project related
information
11
Un
ive
rsity
of
Ed
uca
tion
Oka
ra
Ca
mp
us
Risk Analysis
• In the risk analysis phase, a process is undertaken to identify risk and alternate solutions. A prototype is produced at the end of the risk analysis phase. If any risk is found during the risk analysis then alternate solutions are suggested and implemented. 12
Un
ive
rsity
of
Ed
uca
tion
Oka
ra
Ca
mp
us
Engineering
• In this phase software is developed, along with testing at the end of the phase.
Hence in this phase the development and
testing is done13
Un
ive
rsity
of
Ed
uca
tion
Oka
ra
Ca
mp
us
Customer Evaluation• This phase allows the customer to
evaluate the output of the project to date before the project continues to the next
spiral
14
Un
ive
rsity
of
Ed
uca
tion
Oka
ra
Ca
mp
us
AdvantagesHigh amount of risk analysis hence,
avoidance of risk is enhanced.
Un
ive
rsity
of
Ed
uca
tion
Oka
ra
Ca
mp
us
15
AdvantagesGood for mission critical projects.
Un
ive
rsity
of
Ed
uca
tion
Oka
ra
Ca
mp
us
16
AdvantagesStrong approval and documentation control.
Un
ive
rsity
of
Ed
uca
tion
Oka
ra
Ca
mp
us
17
Advantages
Additional functionality can be added at a later date.
Un
ive
rsity
of
Ed
uca
tion
Oka
ra
Ca
mp
us
18
DisadvantagesCan be costly model to use.
Un
ive
rsity
of
Ed
uca
tion
Oka
ra
Ca
mp
us
19
DisadvantagesRisk analysis requires highly specific expertise.
Un
ive
rsity
of
Ed
uca
tion
Oka
ra
Ca
mp
us
20
DisadvantagesProject`s success is highly dependent on the
risk analysis phase.
Un
ive
rsity
of
Ed
uca
tion
Oka
ra
Ca
mp
us
21
Strengths • Provides early indication of
insurmountable risks, without much cost
• Users see the system early because of rapid prototyping tools
• Critical high-risk functions are developed first
• The design does not have to be perfect
• Users can be closely tied to all lifecycle steps
• Early and frequent feedback from users
22
Un
ive
rsity
of
Ed
uca
tion
Oka
ra
Ca
mp
us
Conclusions• The risk-driven nature provides adaptability for a full range of
software projects.• The model has been successful in a large application, the
TRW-SPS.• The model is not yet fully elaborated.• Even partial implementations of the model, such as the risk
management plan, are compatible with the other process models.
23
Un
ive
rsity
of
Ed
uca
tion
Oka
ra
Ca
mp
us
References
• www.slideshare.net• www.buzzle.com• www.cavehill.uwi.edu
24
Un
ive
rsity
of
Ed
uca
tion
Oka
ra
Ca
mp
us