Use Case
A Use Case shows how an actor reaches a goal with a system. It includes main, alternate, and failed paths.
Another example
An invoice case covers opening a valid link, choosing payment, handling a declined card, and receiving a receipt.
Main parts
- 01Actor and situation
- 02Desired outcome
- 03System responsibility and boundary
Use it when
Use it when a short user story cannot cover actors, starting needs, branches, or failures.
Do not use it when
Do not list every click, decide the interface too early, or omit broken paths.
Name used in code
actor + precondition + main flow + alternatives Before you ship
Check the target user, wanted result, current baseline, evidence source, scope, owner, and success level. List assumptions, open risks, and the next test or decision.
Outcome: Use Use Case to make a focused product decision backed by evidence. User context: An invoice case covers opening a valid link, choosing payment, handling a declined card, and receiving a receipt. Product concept to apply: Use Case. Why it fits: Use it when a short user story cannot cover actors, starting needs, branches, or failures. Do not use it when: Do not list every click, decide the interface too early, or omit broken paths. Product framing: Name the target user and wanted result. Record the current baseline and evidence. Set what is in and out of scope, the limits, the owner, and the time frame. Decision quality: Keep facts, guesses, and unknowns separate. Record the options you did not choose and what evidence would change the decision. Acceptance criteria: The document names an owner, target user, measurable result, scope limit, evidence source, open risks, and next test. Evidence and limits (evidence boundary): A formal document may still be a draft, release candidate, or final version. Check its status and browser or platform support. Unknowns to confirm: Target group, baseline, success level, owner, time frame, dependencies, and review schedule.
Check this request
Review the current use of Use Case. Definition: A Use Case shows how an actor reaches a goal with a system. It includes main, alternate, and failed paths. Release checks: Check the target user, wanted result, current baseline, evidence source, scope, owner, and success level. List assumptions, open risks, and the next test or decision. Before changing code, report the evidence you found, gaps, severity, and the smallest safe fix.