Use Cases

One file per use case, named UCNNN-name.md. The template follows Alistair Cockburn, "Writing Effective Use Cases" (Addison-Wesley, 2000).

A use case is a Derived Document. Change the specifications first, then the use case.

This file is written by repo update; keep notes in another file.

Template

# UCNNN: Name

| Property                   | Value                                       |
| -------------------------- | ------------------------------------------- |
| Level                      | Summary, User Goal, or Subfunction          |
| Primary Actor              | Who wants to reach the goal                 |
| Stakeholders and Interests | Who else cares, and why                     |
| Trigger                    | What starts the use case                    |
| Preconditions              | What holds before it starts                 |
| Success Guarantee          | What holds after it succeeds                |
| Minimal Guarantee          | What holds even if it fails                 |
| Business Rules             | The rules it applies, e.g. BR-001           |
| Capabilities               | Optional: the capabilities it describes     |

## Main Success Scenario

1. The primary actor …
2. The system …

## Extensions

- 2a. Condition that branches off step 2:
    1. The system …