Spiral Model
Uploaded by
kan077bei023Spiral Model
Uploaded by
kan077bei023KANTIPUR ENGINEERING
Department of Computer and Electronics Department
COLLEGE
A PRESENTATION FOR
OBJECT ORIENTED SOFTWARE ENGINEERING:
SPIRAL MODEL OF
SOFTWARE PROCESS
21ST
Prakriti Thapa KAN077BEI023
DECEMBER
1
Introduction It is a Software Development Life Cycle
(SDLC) model that provides a systematic and
iterative approach to software development.
In its diagrammatic representation, looks like a
spiral with many loops. The exact number of
loops of the spiral is unknown and can vary from
SPIRAL MODEL
project to project.
The radius in spiral usually shows the expenses or
cost needed for project development.
Each loop of the spiral is called a Phase of
the software development process.
Introduction
Determine objective, Evaluate alternatives,
alternatives &constraint Risk analysis identify,Resolve Risk
Risk analysis
SPIRAL MODEL
Prototype 3
Risk analysis
Prototype 2
operational Prototype 1
Requirement plan life cycle Concept of Simulati
operation on,mode
development Software requirements ls
plan Detail design
Requirement validationProduct design
code
service
Integration test
Plan Next Phase Develop, verify
Next level product
SPIRAL MODEL DIAGRAM
PHASES: Identify and resolve Risks:
During second quadrant, all the possible solutions
are evaluated to select the best possible solution.
Then the risks associated with that solution are
identified and the risks are resolved using the best
possible strategy. At the end of this quadrant, the
Prototype is built for the best possible solution.
Objectives determination and identify
alternative solutions:
SPIRAL MODEL
Requirements are gather from the customers &
the objectives are identified, elaborated, and Develop next version of the Product:
analyzed at the start of every phase. Then During third quadrant, the identified features
alternative solutions possible for the phase are are developed and verified through testing. At
proposed in this quadrant. the end of the third quadrant, the next version
of the software is available.
Review and plan for the next Phase:
In fourth quadrant, t Customers evaluate the so-
far developed version of the software. In the end,
planning for the next phase is started.
ADVANTAGES Iterative and Incremental Approach: The
Spiral Model provides an iterative and
incremental approach to software
Risk Handling: The projects with many development, allowing for flexibility and
unknown risks that occur as the development adaptability in response to changing
proceeds, in that case, It is the best development requirements or unexpected events.
model to follow due to the risk analysis and risk
handling at every phase.
Improved Quality: The Spiral Model allows
SPIRAL MODEL
for multiple iterations of the software
Good for large projects: It is recommend to development process, which can result in
use the Spiral Model in large and complex improved software quality and reliability.
projects.
Customer Satisfaction: Customers can see
Flexibility in Requirements: Change the development of the product at the early
requests in the Requirements at a later phase phase of the software development and thus,
can be incorporated accurately by using this they habituated with the system by using it
model before completion of the total product.
DIS-ADVANTAGES Resource Intensive: The Spiral Model
can be resource-intensive, as it requires a
Complex: The Spiral Model is much more significant investment in planning, risk
complex than other SDLC models. It involves analysis, and evaluations.
multiple iterations of the software development
process.
Too much dependability on Risk
SPIRAL MODEL
Analysis: The successful completion of the
Expensive: Spiral Model is not suitable for project is very much dependent on Risk
small projects as it is expensive. Analysis. Without very highly experienced
experts, it is going to be a failure to develop a
project using this model.
Time-Consuming: The Spiral Model can be
time-consuming, as it requires multiple Difficulty in time management: As the
evaluations and reviews. number of phases is unknown at the start of
the project, time estimation is very difficult.
