---
title: "Spiral model of embedded software life cycle"
subject: "Embedded System"
chapter: 3
key: "semester_6/embedded_system:spiral-model-esdlc"
source: https://www.bctengineer.com/q/semester_6/embedded_system/spiral-model-esdlc
site: BCT Engineering
---

# Spiral model of embedded software life cycle

Embedded System · Chapter 3: Software Design Issues

- Asked in: 2064 Poush (old course)
- Video: [The Embedded System Life Cycle Incremental Model and Spiral Model Lecture 13](https://www.youtube.com/watch?v=im377IFh-Vs) — Yuvraj Parkale
- Answer checked by Claude Opus 5.5 (high effort) on 2026-10-14
- Page: https://www.bctengineer.com/q/semester_6/embedded_system/spiral-model-esdlc
- Whole chapter: https://www.bctengineer.com/md/semester_6/embedded_system/chapter-3

## Question

Explain Spiral Model of Embedded Software Development Life Cycle.

## Short answer

The spiral model iterates through planning, risk analysis, engineering, and customer evaluation in cycles producing prototypes. It emphasizes risk management and suits large, uncertain projects. Early cycles reduce risks; later cycles yield the final product. Drawbacks include cost and expertise need.

## Answer

The **spiral model** develops embedded software through repeated cycles (spirals), each passing through the same four phases. Each cycle produces a more complete prototype, and **risk analysis** is done before the next cycle. It suits large, complex embedded products with uncertain requirements.

```text
 Planning ----------> Risk analysis
    ^                      |
    |                      v
 Evaluation <------- Engineering
 (each loop = one prototype; loops spiral outward)
```

#### Phases of each spiral
1. **Planning / objectives:** determine the objectives, requirements, constraints (cost, memory, timing) and alternatives for this cycle.
2. **Risk analysis:** identify and evaluate technical risks (e.g. missed deadlines, hardware issues) and reduce them using prototypes, simulation or analysis.
3. **Engineering (development and testing):** design, code, integrate and test this cycle's version (first a prototype, then more complete versions).
4. **Customer evaluation:** the customer reviews the result, and the feedback is used to plan the next spiral.

#### Features
- Combines the waterfall model with prototyping and adds risk analysis.
- The radius of the spiral represents cost; the angle shows progress.
- Early cycles produce a concept and prototype; later cycles produce the final product.

**Advantages:** risks are found early; changes in requirements are easy to handle; good for hardware-software co-design. **Disadvantages:** needs risk-analysis expertise; can be costly and long; not suited to small projects.

## Check yourself

The answer's key points as multiple-choice questions, with the correct option and why.

1. How does the spiral model develop software?
   A. Repeated cycles each passing through the same four phases
   B. A single pass in sequence
   C. Without any prototypes
   D. Only coding
   Answer: A. Each cycle yields a more complete prototype. (Key point: Spiral structure)

2. Which phase order is correct?
   A. Coding, planning, testing
   B. Planning, risk analysis, engineering, evaluation
   C. Evaluation, planning, coding, risk
   D. Engineering, planning, evaluation
   Answer: B. Customer evaluation then feeds the next planning. (Key point: Phases)

3. What is the purpose of risk analysis?
   A. Write code
   B. Collect payment
   C. Identify and reduce technical risks before the next cycle
   D. Release the product
   Answer: C. It is what distinguishes the spiral from plain waterfall plus prototyping. (Key point: Risk analysis)

4. For which projects is the spiral model suited?
   A. Small simple projects
   B. Fixed trivial requirements
   C. No-risk projects
   D. Large, complex products with uncertain requirements
   Answer: D. It is costly and needs risk-analysis skill, so it is not for small projects. (Key point: Suitability)

## Related in Embedded System

- [Embedded software development process](https://www.bctengineer.com/question.md?key=semester_6%2Fembedded_system%3Asoftware-development-flow) — Embedded System, chapter 3, asked 3×

## Related in other subjects

- [Spiral model of software development](https://www.bctengineer.com/question.md?key=semester_5%2Finstrumentation_ii%3Aspiral-model) — Instrumentation II, chapter 9, asked 3×
- [Embedded real-time software; model for project](https://www.bctengineer.com/question.md?key=semester_5%2Finstrumentation_ii%3Aembedded-rt-software-model) — Instrumentation II, chapter 9
- [Multimedia application development life cycle](https://www.bctengineer.com/question.md?key=semester_8%2Fmultimedia_system%3Aapp-development-life-cycle) — Multimedia System, chapter 1, asked 4×
- [Project development life cycle phases](https://www.bctengineer.com/question.md?key=semester_7%2Fict_project_management%3Aproject-development-life-cycle) — ICT Project Management, chapter 1