[C LICK HERE AND TYPE P ROJECT N AME ]

U SE C ASE M ODEL

Version <current version>

Page 1 of 4
 Use Case Model

Revision History

Date Version Summary of Change Author

<dd/Mmm/ <x.y> <Section> - <Change> <First Name +
yyyy> Last Name>
12 Apr 2014 0.1 Initial version Thuy Tran
15 May 2014 0.2 Update upon review with internal team: Thuy Tran
Section 3 – Updated flow diagram #
Section 4 - Removed flow #
Section 1 – Add new rule XYZ
1 Jun 2014 0.3 Update upon review with customer: Thuy Tran
Section 2 – Change field label from A to B
Section 4 - Update flow # - step #

Distribution for Review/Approval

Name Title & Company Issue Issue Review Approval

Version Date Date Date
<First Name + <Title> - <Company> <x.y> <dd/ <dd/ <dd/
Last Name> Mmm/ Mmm/ Mmm/
yyyy> yyyy> yyyy>

Page 2 of 4
 Use Case Model

Contents
1 Introduction.....................................................................................................4
1.1 Purpose..........................................................................................................4
1.2 Scope............................................................................................................. 4
1.3 References.....................................................................................................4
2 User Case Diagram........................................................................................4
3 Actors............................................................................................................. 4
4 Use Cases......................................................................................................4

Page 3 of 4
 Use Case Model

1 Introduction
1.1 Purpose
<State the purpose of this Use Case Model:
This document gives a high level view of the system from the user’s perspective
including Actors and Use Cases.

1.2 Scope
<A brief description of the scope of this document>

1.3 References
<Provide a complete list of all documents referenced somewhere in this document.
Each document should be identified by ID, Name, Published Version (optional),
Author, and Storage Location (optional)>

2 User Case Diagram

<Insert a Use Case Diagram here, please remember to express the system
boundary.
If system is complex, the first diagram will present UC Packages then each UC
Package will be detailed in an additional diagram.>

3 Actors
Actor Description
<Actor Name – a <List out all user roles in real business this actor represents for>
noun>

4 Use Cases
Use Case Name Use Case ID Description
<Use Case Name – <Follow <Include:
should start with a naming - Give a brief domain background in case the UC is
verb> convention> complex. For example: What is it? When is it used
and How does it work in reality?
- Purpose of UC>

Page 4 of 4