Use Case Template

CHARACTERISTIC INFORMATION



GEM Element(s)

Use Case Number
<recommendation>
<number><name – the goal as a short active verb phrase>
Goal in Context
<objective>,<rationale>,<reason>
<a longer statement of the goal in context if needed>
Scope


<what system is being considered >
Level


<one of : Summary, Primary Task, Subfunction>
Preconditions
<eligibility>, <inclusion.criterion>, <exclusion.criterion>, <decision.variable>, <value>
<what we expect is already the state of the world>
Success End Condition
<action>, <directive>
<the state of the world upon successful completion>
Failed End Condition


<the state of the world if goal abandoned>
Primary Actors
<intended.audience>, <target.population>
<a role name or description for the primary actor – Actors interact with the System to produce value>.
Secondary Actors

<lab>, <source><other actors or systems of the use case>
Trigger

<source>, <event><the action upon the system that starts the use case>





MAIN SUCCESS SCENARIO








DESCRIPTION
<conditional>, <imperative>


Steps
Actions<the steps of the scenario from trigger to goal delivery,and any cleanup after>




<…>






EXTENSIONS
<conditional>, <imperative>


Steps
Branching Actions





 
<condition causing branching> : <action or name of sub.use case>


<…>
SUB-VARIATIONS
<conditional>, <imperative>


Steps
Branching Actions







<list of variations>






RELATED INFORMATION


<Use case name>
Priority:


<how critical to your system/organization>
Performance


<the amount of time this use case should take>
Frequency


<how often it is expected to happen>
Channels to actors


<e.g. interactive, static files, database, timeouts>
OPEN ISSUES


<list of issues awaiting decision affecting this use case >
Due Date


<date or release needed>
Superordinates


<optional, name of use case(s) that includes this one>
Subordinates


<optional, depending on tools, links to sub.use cases>