Use Case Model

<System>

Team <#, names>

<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.>

Revision History

Date	Version	Description	Edited by
	1.0	Initial Draft

1. Use-Case Diagram

<This is a UML diagram showing all of the use cases defined for the software and their interactions with the system actors.>

2. Use Cases

<There should be one table - using the template below - for each use case.>

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

Name of Use Case	<name>
Brief Description	<A short description of the use case.>
Actor(s)	<A list of all actors related to this use case.>
Basic Flow	<An algorithmic explanation of how the detailed use case normally works from a design point-of-view, referencing objects listed in the previous section where appropriate.>
Alternate Flow(s)	<A list of all common alternatives to the basic flow, along with what the flow would be for each alternative.>
Pre-conditions	<Conditions - if any – that are assumed by the use case to be true immediately before it begins.>
Post-conditions	<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.>