# Ivar Jacobson

> 1939– · Computer Scientist, UML Co-creator
>
> **Recorded contribution:** UML co-creator; use cases; Objectory; Rational Unified Process

## 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

Ivar Jacobson (born 1939) is a Swedish software engineer who developed use cases while working on telecommunications systems, created the Objectory method, and later joined Grady Booch and James Rumbaugh in unifying object-modeling notations into UML. A use case describes how an external actor pursues a goal through interactions with a system; it is not merely a screen list or implementation task. UML became a broad diagram standard, while Rational Unified Process combined iterative development with roles and artifacts. None of these guarantees good software: their value depends on selecting the smallest models that expose requirements, boundaries, and design decisions.

## 2. The problem inherited

Large systems projects lacked a shared way to connect user goals and external interactions with internal object-oriented analysis and iterative delivery.

## 3. The central contribution

Jacobson made goal-oriented usage scenarios a first-class requirements artifact and helped standardize a visual vocabulary connecting behavior, structure, and development work.

## 4. Reconstruct the mechanism

1. Identify an external actor, the goal they seek, and the system boundary within which behavior is designed.
2. Write a main success path as observable actor–system interactions rather than internal implementation steps.
3. Add alternate and failure paths tied to conditions, preserving the goal and postconditions.
4. Use the scenario to derive tests, responsibilities, and design collaborations, updating the model as working increments reveal errors.

## 5. What changed downstream

- Use cases became a common bridge among requirements, design, testing, and product discussion.
- UML standardized many object-oriented diagram types across tools and organizations.
- Objectory and RUP influenced iterative enterprise software processes.

## 6. Attribution, limits, and uncertainty

- Booch and Rumbaugh are UML co-creators, and standardization involved the Object Management Group and many contributors.
- Use cases can miss cross-cutting quality attributes, emergent workflows, and people who are affected but not direct users.
- Large UML/RUP artifact sets can become stale bureaucracy if detached from executable evidence.

## 7. Reconstruction lab

Write a use case for password reset with main, expired-token, and compromised-account paths. Derive acceptance tests and a sequence diagram, then delete every diagram element that does not answer a concrete stakeholder or implementation question.

## 8. Evidence trail

- [Ivar Jacobson](https://en.wikipedia.org/wiki/Ivar_Jacobson) — Wikimedia Foundation
- [Object-Oriented Software Engineering: A Use Case Driven Approach](https://archive.org/details/objectorientedso00jaco) — Internet Archive

---

*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.*