% Use Case

# Cockburn

__Full__

* Title: "an active-verb goal phrase that names the goal of the primary actor"[10]
* Primary Actor
* Goal in Context
* Scope
* Level
* Stakeholders and Interests
* Precondition
* Minimal Guarantees
* Success Guarantees
* Trigger
* Main Success Scenario
* Extensions
* Technology & Data Variations List

__Casual__

Cockburn recognizes that projects may not always need detailed "fully dressed" use cases. He describes a Casual use case with the fields:[9]

* Title (goal)
* Primary Actor
* Scope
* Level
* (Story): the body of the use case is simply a paragraph or two of text, informally describing what happens.

# Fowler

Martin Fowler states "There is no standard way to write the content of a use case, and different formats work well in different cases." He describes "a common style to use" as follows:

* Title: "goal the use case is trying to satisfy"
* Main Success Scenario: numbered list of steps
  * Step: "a simple statement of the interaction between the actor and a system"
* Extensions: separately numbered lists, one per Extension
  * Extension: "a condition that results in different interactions from the main success scenario"