Editing Use case (section)

==== Fully dressed ====

Cockburn describes a more detailed structure for a use case but permits it to be simplified when less detail is needed. His fully dressed use case template lists the following fields:<ref name=Cockburn120>Cockburn, 2001. Page 120.</ref>

* Title: "an active-verb goal phrase that names the goal of the primary actor"<ref>Cockburn, 2001. Inside rear cover. Field "Use Case Title".</ref>
* Primary Actor
* Goal in Context
* Scope
* Level
* Stakeholders and Interests
* Precondition
* Minimal Guarantees
* Success Guarantees
* Trigger
* Main Success Scenario
* Extensions
* Technology & Data Variations List

In addition, Cockburn suggests using two devices to indicate the nature of each use case: icons for design scope and goal level.

Cockburn's approach has influenced other authors; for example, Alexander and Beus-Dukic generalize Cockburn's "Fully dressed use case" template from software to systems of all kinds, with the following fields differing from Cockburn:<ref>Alexander and Beus-Dukic, 2009. Page 121</ref>

* Variation scenarios "(maybe branching off from and maybe returning to the main scenario)"
* Exceptions "i.e. exception events and their exception-handling scenarios"