Exemplary Use Cases

<Note: everything surrounded by <> is either a placeholder to be filled in or a comment to be deleted. All tables contain fictional example entries which should be removed.>

<Source for this template: Managing Software Requirements: A Use Case Approach, Second Edition, by Dean Leffingwell and Don Widrig, page 252.>

Item	Value
Use-case name	<name>
Brief description	<A short description of the use case.>
Actor(s) involved	<A list of all actors related to this use case.>
Basic flow of events	<An explanation of how the use case normally works, usually expressed with a combination of natural language and algorithm.>
Alternate flow(s) of events	<A list of all common alternatives to the basic flow, along with what the flow would be for each alternative.>
Pre-conditions to use case	<Conditions - if any – that are assumed by the use case to be true immediately before it begins.>
Post-conditions of use case	<Conditions which should be true immediately after the use case terminates.>
Special requirements	<Non-functional requirements related only to this use case e.g. performance requirements for this use case.  Any special requirements related to the entire software should go into the supplemental specifications artifact.>

<Duplicate the above table as needed for each exemplary use case.>