Use Case Specification [Title]

[Subject/Project]

Revision Date: | 00/00/0000 | Revision Num: | 1.0 | File Name: | [ Use Case Specification.doc ] | Num of Pages: | [ 6 ] | Author: | [ [Author] ] |

Revision History Date | Revision | Author | Changes | <07/16/2008> | 1.0 | [Author] | <Original document created> | | | | |

Document Reviewers / Approvers Name | Position | Reviewer | Reviewer and Approver | Signature of Approver | Sign-off Date | <Joe Smith> | <Business Executive> | | X | | | <James Underhill> | <Analysis Manager> | X | | | | <Mary Jane> | <Development Manager> | X | | | |

<Note: * The text in blue and italic is for guidance only and should be deleted before the document is published. * If any section of this document is not required for the project at hand it may be delete it or its content replaced with “N/A”. * Go to “File/Properties” and on the “Summary” tab update the following fields to match your project: * Title – replace the (Title) part of the title with the name of the use case described in this document; * Subject – enter your project’s name here; * Author – enter your names or first initial followed by your last name; * Company – enter your company’s name. * For the changes from the “Summary” tab to take effect select the all the text in the document and press F9. * Repeat this in the header and footer areas of the document as well. * If a message shows up after you’ve pressed F9, select the “Update entire table” option. * After each update of the document make sure to increase the revision numbers and update the revision date manually on: * The first page * The document header * In the revision table and to describe the changes * In order to access this template from the “File/New” menu, copy the file in the MS Word template folder. * For MS Word 2003 this folder is: "C:\Documents and Settings\Your Username\Application Data\Microsoft\Templates” . * Then when you want to create a new document using this template you will follow these steps: “File/New” then on the right hand side of the screen select “On my computer...” and choose this template from the “General” tab on the “Templates” window that pops up.

Table of Contents 1 Introduction 5 2 Use Case Description 5 3 Pre-Conditions 5 4 Trigger 5 5 Post-Conditions 5 6 Normal Flow <Name> 5 7 Alternate Flows 6 7.1 Alternative Flow <xx> –<Name> 6 8 Exceptions 6 9 Includes 6 10 Special Requirements 6 11 Assumptions 6 12 Associated Features or Functional Requirements 6

This page intentionally left blank.
<The document content which starts on the next page should always be on an odd numbered page.>

Use Case Specification [Title] * Introduction Use Case Name | Use Case ID | Date Created | Created By | <Use Case Name> | <Assign a unique ID (e.g.UC-1)> | <Date created (mm/dd/yyyy)> | <Analyst’s name > | Primary Actors | Secondary Actors | <Primary actors> | <Secondary actors> |

Use Case Description
<Provide a high level description or goal of the use case, typically a couple of sentence. Add the use-case diagram either before or after the description.>

Pre-Conditions
<List anything that must be complete prior to the initiation of the use case. Document these as a numbered list of Pre-Conditions. For example, the user may be required to be logged into the software application or system>. a)

Trigger
<List the conditions that trigger the use case.> a)

Post-Conditions
<List the end results expected by the user. Document these as a numbered list of Post-Conditions. For example, the user has saved a template in a designated folder.> a)

Normal Flow <Name>
<Replace <Name> with the normal flow name. The main flow of events covers what "normally" happens when the use case is performed. This is the “Happy day scenario”.> Alternate Flows
Alternative Flow <xx> –<Name>
<The alternative flows of events cover behavior of optional or exceptional character in relation to the normal behavior, and also variations of the normal behavior. They handle “what if” scenarios, conditional logic and main flow branching.
Alternative flows = "detours" from the main flow of events
Replace <Name> with the alternative flow’s name and <xx> with its number. For alternative flow numbering see the note below.

Note: When numbering the alternate flows use the number of the step from which the flow branches and add “A” to indicate that this alternate flow is the first branch from this step, then “B” for the second alternative flow branch from this step, etc. Number the steps in the alternative flow by adding 1,2, etc. after the “A”, “B” etc, from the number of the alternate flow.
Possible alternative flows: * Actor selects Yes or No; OK or Cancel, etc. * There is no data * Etc.
After the UC descriptions add as many diagrams as possible: activity, sequence, flow chart, whatever makes sense. Delete this text before publishing the document.>

Exceptions

Includes
<List any use cases that are included or required for the designated use case.>

Special Requirements
<Describe any special requirements associated with the use case, or their reference number, and the document they are originally described, if not this one.>

Assumptions
<Describe any assumptions associated with the use case, or include their reference number, and location if listed elsewhere.>

Associated Features or Functional Requirements
<Identify associated features or functional requirements, or their reference numbers, for the use case and the document they are originally described.>