Scenario
- •
- •
- •
- •
Formality types
- •
brief — a terse, one-paragraph summary, usually of just the main success scenario
- •
casual — an informal, multi-paragraph format covering the main scenario plus some alternates
- •
fully dressed — the most elaborate; every step and variation is written out, with supporting sections for preconditions, success guarantees, stakeholders' interests, special requirements, and technology/data variations
- •
- •
Fully dressed use case sections
- •
name, scope, level, primary actor, stakeholders and interests, preconditions, success guarantee, main success scenario, extensions (alternate scenarios), special requirements, technology/data variations, frequency of occurrence, open issues
- •
- •
Two-column variant
- •
the main success scenario can be split into "actor action/intention" vs. "system responsibility" columns, clarifying exactly who does what at each step
- •
- •