# Barry Boehm

> 1935–2022 · Computer Scientist, Software Economist
>
> **Recorded contribution:** COCOMO; spiral model; software economics; anchored agile

## How to use this dossier

Read for a causal chain, not a hero story: inherited problem → contribution → mechanism → downstream capability → limit. Then close the page and complete the reconstruction exercise from memory.

## 1. Historical orientation

Barry Boehm (1935–2022) was a software engineer whose models connected cost, schedule, risk, and lifecycle choices. COCOMO estimated effort from software size and project factors using empirical calibration; the spiral model organized development as repeated cycles of objectives, alternatives, risk reduction, construction, and stakeholder review. Boehm later promoted stakeholder 'win conditions' and risk-driven combinations of plan-driven and agile practice. The spiral is often misdrawn as merely iterative waterfall. Its distinctive mechanism is that the next work is chosen by the largest unresolved risk, which may require a prototype, analysis, negotiation, or implementation—not a fixed phase sequence.

## 2. The problem inherited

Large software projects committed early to plans despite uncertain requirements, technology, cost, and safety, while managers lacked empirical models for effort and risk.

## 3. The central contribution

Boehm supplied quantitative estimation models and a risk-driven lifecycle in which teams repeatedly expose and reduce the uncertainties most capable of causing project failure.

## 4. Reconstruct the mechanism

1. Set the current cycle's stakeholder objectives, constraints, and candidate approaches.
2. Identify and rank risks such as feasibility, usability, security, cost, schedule, or incompatible stakeholder goals.
3. Build the cheapest evidence that reduces the dominant risk—prototype, benchmark, simulation, review, or production increment.
4. Evaluate results with stakeholders, update estimates and commitments, and plan the next cycle around remaining risk.

## 5. What changed downstream

- COCOMO made software-cost assumptions explicit and calibratable.
- The spiral model legitimized prototyping and iteration in high-assurance development.
- Risk-driven tailoring influenced modern incremental, architecture, and DevOps practices.

## 6. Attribution, limits, and uncertainty

- Models depend on historical calibration and can mislead when size, domain, team, or technology differs.
- The spiral requires skill at recognizing risk; ritual loops without evidence do not implement it.
- Quantitative estimates can be weaponized as commitments and hide political uncertainty behind precise-looking numbers.

## 7. Reconstruction lab

Choose a small application with one uncertain dependency. Estimate it with a simple COCOMO-style model, rank five risks, and run a one-day experiment on the top risk. Update the estimate and explain why the next cycle changed.

## 8. Evidence trail

- [A Spiral Model of Software Development and Enhancement](https://doi.org/10.1109/2.59) — Computer
- [Barry Boehm](https://viterbi.usc.edu/news/news/2022/in-memoriam-barry.htm) — University of Southern California

---

*Research checked 2026-08-09. Dates, roles, and claims about living people are historical snapshots. Linked sources remain the authority; this dossier is original instructional synthesis.*