<Project name>_<Use Case name>

Contents
I. DOCUMENT CONTROL ..................................................................................................................... 2

1. GENERAL INFORMATION ............................................................................................................................ 2

2. CHANGE LOG ............................................................................................................................................. 2
3. APPROVALS ................................................................................................................................................ 2

II. USE CASE SPECIFICATION .............................................................................................................. 2

UC NAME ........................................................................................................................................................... 2
ID ....................................................................................................................................................................... 2
PRIORITY ............................................................................................................................................................ 2
BRIEF DESCRIPTION ............................................................................................................................................ 2
PRIMARY ACTOR................................................................................................................................................. 2
TRIGGER ............................................................................................................................................................. 2
PRE- CONDITIONS ................................................................................................................................................ 2
POST CONDITIONS ............................................................................................................................................... 2
MAIN FLOW ........................................................................................................................................................ 2
ALTERNATIVE FLOWS ......................................................................................................................................... 2
EXCEPTIONS ........................................................................................................................................................ 2
BUSINESS RULES ................................................................................................................................................. 3
SPECIAL REQUIREMENTS .................................................................................................................................... 3

III. ADDITIONAL INFORMATION ...................................................................................................... 3

1. DIAGRAM ................................................................................................................................................... 3
2. MESSAGES LOG .......................................................................................................................................... 3
3. GUI ............................................................................................................................................................ 3
4. UI NOTES ................................................................................................................................................... 3
 I. DOCUMENT CONTROL
1. General Information
Created Date
Last Changed By
Last Changed Date
Version
Status

2. Change Log
Date Version Changes Changed By

3. Approvals
Role Name Date

II. USE CASE SPECIFICATION

UC Name

ID

Priority Must Have > Should Have > Nice to Have> …

Brief Description [Give the description about the use case document detailing the context and background of the
functionality described.]

Primary Actor [An actor is a person or other entity external to the system who interacts with the system. Define
all the actors of the use case here.]

Trigger [The event causes starting the use case.]

Pre- conditions [Describe the conditions that must be true before the use case can be started.]

Post conditions [Describe the state of the system at the conclusion of the use case execution.]

Main Flow [Describe system responses that will take place during execution of the use case under normal,
expected conditions.]

Alternative Flows [Describe legitimate branches from the main flow to handle special conditions.]

Exceptions [Describe any anticipated error conditions that could occur during execution of the use case.]

Confidential Page 2 of 4
Business Rules [Describe specific rules or conditions that are imposed by the business.]

Special Requirements

III. ADDITIONAL INFORMATION

1. Diagram
[Attach the use case diagram that were created with respect to the use case document.]

2. Messages Log
Message ID Content Note

3. GUI
[Include any prototype or screens that were created to aid understanding regarding the use case document.]

4. UI Notes
[Any User interface notes and details will come in here.]

Field Name Description Control Type Rules

<Caption of the element <Include: <Put name of data type <Include:

on the wireframe > of the field. See
- Meaning of the field 1/ Data type
guidelines below>
- Where does the data 2/ What is default value?
of this field come
4/ Is it required fields?
from?>
5/ Select values or enable this field, what
other functions or fields will be impacted?
6/ List all Validation rules applied to the
field. See guidelines below
7/ List all Action rules applied to the field.
See guidelines below>

<Guidelines for UI Elements table above:

Control Type:
Use one of the following control type:
- Text field: single line
- Text area: multiple lines
- Drop down: cannot type in the text box

Confidential Page 3 of 4
 - Combo box: allow to type in the text box
- List box
- Date Time
- Date
- Time
- Button
- Radio button
- Check box
- Hyperlink
- Label
Note: Grid control is not listed here because each Grid Column will be presented as a single Field
Name.
Data Type:
Use one of the following data type:
- String (length)
- String
- Integer
- Decimal
- Date Time
- Date
- Time
- Boolean
- Enum {v1, v2, v3}
Validation Rules:
Tell all rules to validate data when leaving fields, or before saving to database, normally including the
following constraints:
- Wrong data type
- Wrong data range
- Wrong data format
- Required field
- Relation between two fields (ex: Value of field A < Value of field B)

Action Rules:
- Tell rules that the system behaves when actor does actions on UI Elements.

Confidential Page 4 of 4