Use Case Specification

Purpose

Define actors, triggers, flows, exceptions, and outcomes for user-system interactions.

Use when

• functional behavior must be described clearly
• requirements need structured interaction modelling
• design/testing traceability is important

Inputs

• problem context
• available evidence and constraints
• known stakeholders or actors
• desired output format

Procedure

1. Clarify the decision or deliverable.
2. State assumptions before analysis.
3. Apply the technique explicitly rather than implicitly.
4. Capture findings in a structured table or list.
5. Separate facts, inferences, and unknowns.
6. End with implications for next actions.

Outputs

• use case list
• use case descriptions
• normal/alternate/exception flows
• acceptance notes

Guardrails

• Do not present the technique as the answer; use it to inform a decision.
• Flag missing evidence and weak assumptions.
• Keep terminology consistent with the project glossary.
• Where tradeoffs exist, rank them explicitly.

Completion criteria

• technique applied correctly
• assumptions visible
• findings actionable
• next step clear