Scribd
Upload
7 views

Spiral-Model-1

The Spiral Model is a risk-driven software development process introduced by Barry W. Boehm in 1986, designed to address the limitations of traditional models by incorporating iterative development and risk management. It is particularly suitable for large, complex projects with uncertain requirements, allowing for flexibility and early prototyping, but can be complex and costly to manage. The model consists of four phases: planning, risk analysis, engineering, and evaluation, with iterative cycles for continuous improvement.

Uploaded by

Cherrylyn Ramos
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
7 views

Spiral-Model-1

The Spiral Model is a risk-driven software development process introduced by Barry W. Boehm in 1986, designed to address the limitations of traditional models by incorporating iterative development and risk management. It is particularly suitable for large, complex projects with uncertain requirements, allowing for flexibility and early prototyping, but can be complex and costly to manage. The model consists of four phases: planning, risk analysis, engineering, and evaluation, with iterative cycles for continuous improvement.

Uploaded by

Cherrylyn Ramos
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
You are on page 1/ 21

SPIRAL

Andre Flores
Gian Bello

MODEL IN Jaryl Rodelas


Jomar Cedeno

SYSTEM Joshua Bueta


Maverick
ANALYSIS AND Bautista
Symond Clark

DESIGN Niog
HISTORY AND FOUNDER
OF THE SPIRAL MODEL
THE SPIRAL MODEL IS A RISK-DRIVEN SOFTWARE
DEVELOPMENT PROCESS MODEL. BASED ON THE UNIQUE
RISK PATTERNS OF A GIVEN PROJECT, THE SPIRAL MODEL
GUIDES A TEAM TO ADOPT ELEMENTS OF ONE OR MORE
PROCESS MODELS, SUCH AS INCREMENTAL, WATERFALL,
OR EVOLUTIONARY PROTOTYPING. THE SPIRAL MODEL
WAS FOUNDED BY BARRY W. BOEHM IN 1986. HE
INTRODUCED IT IN HIS PAPER "A SPIRAL MODEL OF
SOFTWARE DEVELOPMENT AND ENHANCEMENT" TO
ADDRESS THE LIMITATIONS OF TRADITIONAL MODELS
LIKE THE WATERFALL MODEL BY INCORPORATING
ITERATIVE DEVELOPMENT AND RISK MANAGEMENT.
BOEHM WAS A RENOWNED AMERICAN SOFTWARE
ENGINEER AND RESEARCHER KNOWN FOR HIS
CONTRIBUTIONS TO SOFTWARE COST ESTIMATION, RISK
MANAGEMENT, AND SOFTWARE ENGINEERING
METHODOLOGIES. HIS WORK SIGNIFICANTLY INFLUENCED
MODERN SOFTWARE DEVELOPMENT PRACTICES,
PROS AND CONS
OF THE SPIRAL
MODEL
ADVANTAGES
1.Risk Management •OF
This isSPIRAL MODEL
the biggest strength.
The spiral model explicitly addresses risks at each
phase. This proactive approach helps identify
potential problems early on, allowing for mitigation
strategies or even project cancellation if the risks
are too high. 2.Flexibility • Changes can be made at
any stage and the customer’s needs might evolve.
3.Early Prototyping • Customers can see and test an
early version of the product. 4.Suitable for Large
Projects • The model is ideal for complex, long-term
projects where requirements are not fully known at
the start.
DISADVANTAGES
1.Complexity • TheOF SPIRAL
spiral MODEL
model can be
complex to manage, requiring expertise in
risk assessment and project management.
It's not suitable for teams lacking this
experience 2.Cost and Time • Repeated
iterations and risk analysis can make the
process expensive and time-consuming.
3.End of Project Uncertain • Frequent
changes make it difficult to set a clear
deadline, this can be a challenge for
projects with fixed deadlines.
IDEALISTIC
OF THE SPIRAL
MODEL
what project if software
development can I use?
IF YOU WANT TO USE THE SPIRAL DEVELOPMENT
CONCEPT, CONSIDER PROJECTS THAT ARE LARGE,
COMPLEX, HAVE UNCERTAIN REQUIREMENTS, OR
CARRY HIGH RISK, SUCH AS DEVELOPING A NEW
ENTERPRISE RESOURCE PLANNING (ERP) SYSTEM, A
COMPLEX MEDICAL SOFTWARE APPLICATION, OR A
CUTTING-EDGE GAMING PLATFORM, WHERE
FREQUENT ITERATIONS AND RISK ANALYSIS ARE
CRUCIAL TO ENSURE SUCCESSFUL DEVELOPMENT.
KEY
CHARACTERISTICS OF
PROJECTS SUITABLE
FOR THE SPIRAL
MODEL:
High-risk elements:
PROJECTS WHERE SIGNIFICANT
UNKNOWNS OR POTENTIAL
ISSUES COULD ARISE DURING
DEVELOPMENT.

NEED FOR FREQUENT FEEDBACK:


SITUATIONS WHERE USER INPUT
AND ADJUSTMENTS ARE REQUIRED
THROUGHOUT THE DEVELOPMENT
PROCESS.
Complex requirements:

PROJECTS WITH INTRICATE


FUNCTIONALITIES OR
EVOLVING NEEDS THAT
MAY NOT BE FULLY
DEFINED AT THE START.
ITERATIVE REFINEMENT:
Ability to continuously improve the
product through multiple
development cycles.
Examples of software development
projects that could benefit from the
spiral model:
Developing a new operating system
with innovative features
Creating a complex simulation
software for a scientific application
Building a large-scale e-commerce
platform with dynamic user
interactions
Designing a custom healthcare
information system with sensitive
data handling requirements
Developing a cutting-edge
augmented reality application with
evolving technology
MODEL/DIAGRAM
OF THE SPIRAL
MODEL
PHASE 1: PLANNING ACTIVITIES:

IDENTIFY SYSTEM OBJECTIVES AND SCOPE.


GATHER INITIAL REQUIREMENTS. DEFINE
CONSTRAINTS AND ALTERNATIVES. ESTIMATE
COST, TIME, AND RESOURCES.

PEOPLE INVOLVED: BUSINESS ANALYSTS –


GATHER AND DOCUMENT REQUIREMENTS.
PROJECT MANAGERS – DEFINE SCOPE AND
ESTIMATE COSTS. STAKEHOLDERS/CLIENTS –
PROVIDE SYSTEM REQUIREMENTS.
PHASE 2: RISK ANALYSIS ACTIVITIES:

IDENTIFY TECHNICAL, FINANCIAL, AND OPERATIONAL


RISKS. CONDUCT FEASIBILITY STUDIES AND
PROTOTYPING. DEVELOP RISK MITIGATION
STRATEGIES.

PEOPLE INVOLVED:

SYSTEM ARCHITECTS – ASSESS TECHNICAL RISKS.


BUSINESS ANALYSTS – ANALYZE BUSINESS
FEASIBILITY. PROJECT MANAGERS – PLAN RISK
MITIGATION. STAKEHOLDERS – REVIEW RISK
ASSESSMENT RESULTS.
PHASE 3: ENGINEERING (DEVELOPMENT &
TESTING) ACTIVITIES:

DESIGN SYSTEM ARCHITECTURE AND SOFTWARE


COMPONENTS. DEVELOP, INTEGRATE, AND
IMPLEMENT SOFTWARE MODULES. PERFORM
UNIT, INTEGRATION, AND SYSTEM TESTING.
PEOPLE INVOLVED:

SOFTWARE ENGINEERS – DEVELOP AND


INTEGRATE CODE.

SYSTEM ARCHITECTS – DESIGN SYSTEM


STRUCTURE.

QA TESTERS – CONDUCT TESTING FOR


FUNCTIONALITY AND BUGS.

PROJECT MANAGERS – OVERSEE DEVELOPMENT


PROGRESS.
PHASE 4: EVALUATION & REVIEW ACTIVITIES:

GATHER FEEDBACK FROM END USERS.

EVALUATE SYSTEM PERFORMANCE AND QUALITY.

IDENTIFY REQUIRED IMPROVEMENTS AND


REFINEMENTS.

DECIDE WHETHER TO PROCEED TO THE NEXT


ITERATION OR MODIFY FEATURES.
SPIRAL
MODEL/DIAGR
AM
PEOPLE INVOLVED:

END USERS – PROVIDE FEEDBACK ON


FUNCTIONALITY.

BUSINESS ANALYSTS – VALIDATE REQUIREMENTS

FULFILLMENT. QA TESTERS – ASSESS SOFTWARE


QUALITY.

PROJECT MANAGERS – MAKE GO/NO-GO


DECISIONS.
ITERATIVE PROCESS (LOOPING BACK TO
PLANNING PHASE)

- AFTER EVALUATION, REFINEMENTS ARE


PLANNED FOR THE NEXT ITERATION.

- THE PROCESS REPEATS IN A SPIRAL,


IMPROVING THE SYSTEM WITH EACH CYCLE
UNTIL THE FINAL VERSION IS COMPLETE.

You might also like