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/ 12
SPIRAL MODEL
SHOAIB ALI RAJPER
2K23/NFIT/19
Department of Information Technology
Presented to: Miss Saba Nizam
AGENDA Spiral Model Key Characteristics Advantages Disadvantages When to Use SPIRAL MODEL
A software development model
that essentially combines Waterfall and Iterative models. It was first introduced by Barry Boehm in 1986. The Spiral Model is characterized by its emphasis on risk analysis and management throughout the software development lifecycle. KEY CHARACTERISTICS:
1. Iterative approach: The Spiral Model is based on an iterative approach,
where the project is divided into smaller cycles or spirals.
2. Risk-driven: The model is risk-driven, meaning that the level of risk
determines the number of spirals and the level of retail in each spiral. 3. PHASES OF SPIRAL MODEL
Planning: Define the goals and objectives for the spiral.
Risk Analysis: Identify and evaluate the risks associated with the spiral. Engineering: Develop and test the software. Evaluation: Review and evaluate the software. KEY CHARACTERISTICS:
4. Customer Involvement: The
customer is involved throughout the development process, providing feedback and guidance. ADVANTAGES
1. Flexibility: The Spiral Model is flexible and can be adapted to changing
requirements. 2. Risk management: The model provides a built-in risk management approach. 3. Customer satisfaction: The customer is involved throughout the development process, ensuring that the software meets their needs. 4. Large Projects: used for developing large & complex projects. 5. Meta Model: It contains good characteristics of many models. DISADVANTAGES
1. Complexity: The Spiral Model can be complex to manage, especially for
large projects. 2. Time-consuming: The model requires a significant amount of time and effort to complete each spiral. 3. High risk: The model assumes that the risks will be identified and mitigated, but this may not always be the case. 4. Expensive: The spiral method is expensive because it handles risk- oriented software projects and hence requires a significant amount of investment in planning, risk analysis and evaluation. WHEN TO USE:
1. High risk-projects: The Spiral Model is suitable for high-risk
projects where the requirements are not well-defined. E.g: Space Exploration, Nuclear Power Plant, Self-Driving Cars etc. 2. Complex projects: The model is suitable for complex projects that require a flexible and iterative approach. E.g: Operating System Development, Database management Systes, Scientific Research Software. WHEN TO USE:
3. Customer-driven projects: The model is suitable for projects
where the customer is heavily involved and requires frequent feedback and delivery. E.g: E-commerce Website Development, Mobile App development, Online Educational Platforms(Coursera or Udemy)
(Ebook) Practical Rust Projects: Build Serverless, AI, Machine Learning, Embedded, Game, and Web Applications by Shing Lyu & Andrew Rzeznik ISBN 9781484293317, 1484293312 - The ebook is ready for download with just one simple click