Use Case Name
<A brief description of the use case. Usually a paragraph or less.>
Actors
<A list of the actors who communicate with this use case.>
* <Actor Name - brief description.>
* <Actor Name - brief description.>
* <Actor Name - brief description.>
Priority
<How important is this use case to the project? Must have, should have, would like to have, you're dreaming.>
Status
<What is the status of this use case? High level description, detailed description, scenarios complete, coded, tested, etc.>
Pre-Conditions
* <Something that must be true before the use case begins.>
* <Something that must be true before the use case begins.>
* <Something that must be true before the use case begins.>
Flow of Events
Basic Path
1. <Write the first step in the use case.>
2. <Write the next step in the use case.>
3. <Write the next step in the use case.>
Alternative Paths
<Write any alternatives to the basic path.>
Post-Conditions
* <Something that must be true when the use case ends.>
* <Something that must be true when the use case ends.>
* <Something that must be true when the use case ends.>

"Used" Use Cases
* <Use case Name>
* <Use case Name>
* <Use case Name>
Activity Diagram
<An activity diagram of the flow of events, or some significant or complex part of the flow of events.>
User Interface
<For systems that interface with people, include a description of the user interface, possibly using storyboards.>
Scenarios
<List the scenarios of the use case. Include a brief description of each one.>
* <Scenario Name - brief description.>
* <Scenario Name - brief description.>
* <Scenario Name - brief description.>
Sequence Diagrams
<If you do not have separate scenario documents, you may also wish to include a sequence diagram for each Scenario.>
Subordinate Use Cases
<If the use case has subordinate use cases, include a use case diagram of those subordinate use cases here. Or make a list of the subordinate use cases by name, and tell which subsystem is responsible for each one.>
View of Participating Classes
<A collaboration or class diagram showing all the classes whose objects interact to implement this use case. Include the interfaces to the use case and the classes that implement the interfaces.>
Other Artifacts
<Anything else you might want to include. Possibly an analysis model, a design model, or test plans.>
Other Requirements
<This section includes a list of non-functional requirements that affect the use case.>