Use cases

description

author
date

Use case name
Summary (used only for large use cases)
Preconditions: (if needed - prerequisites for carrying out the use case)
Main scenario
  1. Actor step1
  2. System response
  3. Actor step - if needed refer to another use case (#) or link to exception [Exception 1: Name]
  4. System response etc (actor or system may also have multiple consecutive actions)
Exceptions and alternate scenarios
  1. Exception name. Short description (use steps if necessary) about the scenarios
  2. Exception name. Short description etc (there may be multiple exceptions - depending on the exeption return to main scenario or abort the use case)
Postconditions: (if needed - what must be accomplished after successul completion of the use case)
Notes
  1. Step descriptions should be short, clear and of the form subject-predicate-object - subject should be either actor role, or the system. If the step requires additional clarifications (e.g. steps repeated in a loop), the table can be supplemented using numbered footnotes.



Use case name

Preconditions:
Main scenario
  1. ...
Exceptions and alternate scenarios
  1. ...
Postconditions:
Notes
  1. ...



etc