A template for use cases.

• Each Use Case should be named so that it can be easily referred to
• Starred sections are optional and can be deleted if necessary.
  

Description:

A brief description of this use case in terms of the Actor's goals and purpose for initiating it.

Actor(s):

Which Actor initiates this use case. Who else might be affected by it.

Preconditions:

What must the system state be in before this can be executed. (e.g. User must be logged in)

Flow of Events:

A description of the sequence of operations that will occur to fulfill the goal (or lead to failure). This should contain some detail and may loop, have alternate pathways etc.

Postconditions*:

What must be true/false after this Use Case has completed successfully.

System/subsystem*:

Which subsystem is responsible for the Use Case.

Special Requirements*:

Performance or other non-functional requirements that apply to this Use Case.