Use Case TABLE with Actors & Goals

Putcha V. Narasimham
Knowledge Enabler Systems,
205, Krishna Apts, Avenue No. 6, Banjara Hills,
Hyderabad 500034
Mobile: 91 98660 71582
putchavn@yahoo.com,

Founder Professor & Proprietor

Our Ref: In the footer
Date: 24FEB11, Rev 23SEP11, 13DEC11, 29MAY12, 08SEP12, APR13, 08NOV13

Use Case TABLE
with Actors and Goals
Diagrams are OK but they take too long to
make / edit / refine. Certain diagrams, the
contents of which have good structure can
be better represented and quickly edited
in Word Tables.
Use Case Table has columns for the obvious
Actor and Use Case Name and GOAL. Later
I have felt a need to add Business Policies
and Rules relating to GOAL. I have added
that too but it is optional.
This is similar to CONTEXT TABLE which was
used to elaborate on Context Diagram of
SSAD.
See the next example. Read with 5 Use
Case Diagram PPT, Word document and
Template.
Creating and refining Use Case Diagram is a
long and time-consuming activity. It slows
down thinking, exploration, and recording.
The Use Case Diagram itself does not have
much pictorial / visual information of
value: Hence this Table. Hope you will find
it quick, easy and useful.

5 Use-Case TABLE with Actors & GOALS
Copyright © by Putcha V. Narasimham, 2013

Page No 1 of 6

Hyderabad 500034
Mobile: 91 98660 71582
putchavn@yahoo.com,


See the explanation here and the examples
in the next page before applying. Come
back to this template while working on your
project. Best wishes,
Use Case Table UCT-1

Commented [PVN1]: Identify by a suitable Name and
Number.

<System Name>
Srl
No

Actor (s)
Playing a
single role

Use Case Name

1

Goal and Business Policies & Rules
Start with some definition but make it comprehensive
(covering all relevant stakeholders) iteratively.
This is the cell for Business Policies and Rules applicable to the
Goal. Delete this comment and enter Policies & Rules.

2

Commented [PVN2]: This is the system or subsystem under
development.
Commented [PVN4]: Actor is often mistaken to be an entity
a person or a device which may play different roles. Experts
in UML explain that Actor represents a single ROLE like
“requester” “initiator” “first level approver” “final decision
maker” etc. But this correct interpretation is NOT well
understood nor used. So, I RELUCTANTLY continue the
popular incorrect use of Actor to mean an Entity. So
the same entity is shown participating in a number of different
Use Cases (2,3&4). The cells are merged into one under
Actor playing a single ROLE.
Commented [PVN6]: This table is mostly for GOALS. Let it
be long but include the objectives of the service.

3

Commented [PVN7]: This is an extension. I felt the need
for it to cite the Policy and Rules for each Service or Use Case.
There is no standard mechanism to refer to them in any UML
Diagram. They are very crucial in all business applications.

4

Commented [PVN5]: The Name of the service offered by
the system. The service action is assumed to be the System
always. So pays or buys means system pays or buys….NOT
the Actor. If the action belongs to the Actor, then the UC
name begins with “Enable” as in “Enable to Register”, “Enable
to Approve”, ”Enable to Withdraw Cash”

5

Add rows for more use cases.

Commented [PVN3]: Of the Use Case

For a large system, the number of rows
may overflow a page. Then the Table
can be split and shown on different
pages. That is the advantage of the
Table. See the second example of ATM
System.


Page No 2 of 6

Hyderabad 500034
Mobile: 91 98660 71582
putchavn@yahoo.com,


Example: Training Management System
Training Management System TMS is a sub-system
of Human Resource Management System. It is
advantageous to represent large systems as a
network of subsystems each of which can be
separately modeled and developed. Here all other
sub-systems interacting with this subsystem TMS
would appear as Actors in the Use Case Diagram of
TMS.
Mr S V Ramanan and the author created the TABLE
for his project: Training Management System
interacting over Skype (Audio).
Use Case naming convention: State the services
with reference to the System, NOT ACTORS
Use Case Table TMS-1

Training Management System
Srl
No

Actor(s)
Role

Goal and Business Policies & Rules

Capture Training
Objectives & Needs

To get training objectives and volumes from user
departments.

Capture Training
Programs, Syllabus,
Standards

To enable design of training programs, Syllabus and
standards to meet the objectives and ….

Enable Training
Calendar Creation

To provide an annual plan of training programs for
employees / managers

4

Enable Resource
Allocation for
Sessions

To provide effective training as planned with all
resources

T5

Capture Training
Requests

Let employee choose training they like / need

Conduct Quizzes and
Tests

To conduct quizzes and tests and maintain scores /
progress of learning

Capture feedback

To capture feedback on training provided

1

HODs &
Managers

Use Case Name

2

3

6
7

Training
Manager

Employee


Page No 3 of 6

Commented [PVN8]: Not shown in this Table. See the next
example ATM in page 3.
Commented [PN9]: This is an entity name or job title but
not a role name

Hyderabad 500034
Mobile: 91 98660 71582
putchavn@yahoo.com,

Enable to Register,
Present / Update
Profile
Capture Training
Material / Quizzes
Capture Grades /
Evaluation Reports
Capture decisions on
training requests /
needs

8
9


Faculty
Ext
Int

10

Organization enlists and maintains a pool of faculty /
Trainers for effective training
To capture refine and maintain Training Material and
Quizzes / standards
To capture grades and evaluation reports for all training
conducted
To provide training as per job requirements / needs and
employee interest. Formal decisions are obtained.

11

Manager

12

HR Record
Management
System

Obtain relevant HR
Records for Training

To draw on master data maintained in the HR Record
Management System and send Training data

13

All Actors

Show Training
Calendar

To display Training Calendar to all interested parties to
provide and utilize training

Example:

ATM System

Description is not given since it is well known-- Not a good practice.

Use Case Table 1A

Automatic Teller Machine System
Srl
No

Actor(s)
Role

Use Case Name
Enable Login &
Offer Services to

1

This absorbs “Show
Account
Information” Use
Case

Bank
Customer

2

Enable Query
and Cash
Withdrawal and
Transfers from
selected account


Goal & Business Policies & Rules
To enable authentic Bank Customers to log in
and offer services they are entitled to.
2 Show Account Info, 3 Enable Deposit 4
Deliver Receipt + related info 5 New Service
Only authentic Bank Customers can log in. There is no provision
to become a customer online. Once the Bank Customer logs in
successfully, all the services he is entitled to are presented.
They are the Use Cases 2 to 5. We do not know them
now…provision for extension
To enable Bank Customers to A view / query
selected bank accounts, B make cash
withdrawals or C electronic fund
A Bank customer may hold many types of accounts as per the
rules of the Bank. He may choose to operate any of the
accounts.
Client may like to do electronic fund transfer under this Use Case
or have a separate Use Case…check with the client. Electronic
Fund Transfer requires Registration of Beneficiaries under each
account. This suggests a need for another use case: Enable
Opening Account and Selecting Facilities ---This can be done
manually, over the internet or ATM

Page No 4 of 6

Commented [PVN10]: This table got too long and had to
be split. To start with it was single and compact. If one
wishes, a copy of it can be made and expanded.
This keeps the related information well connected and
organized. Apt for incremental iterative development.

Hyderabad 500034
Mobile: 91 98660 71582
putchavn@yahoo.com,

Srl
No

Actor(s)
Role

Use Case Name

3

Enable Deposit of
cash or cheques

4

Deliver Receipts &
other reports


Goal & Business Policies & Rules
To enable deposit of A cash or B cheques into the
selected account.
Can be added….
To deliver receipts and other reports of the latest
transactions…successful or otherwise with date
time location etc.
Can be added

Query and Get
Approvals from

5
Bank
Computer
System

Send periodic
reports to

5A

Proposed

6

Cash
Loader

7

To access the Bank Computer in which all the
customer account details are maintained and obtain
status reports or approvals etc
ATM does not maintain any customer information…so the Bank
Computer has to be accessed for any customer service.
This use case is activated while the Bank Customer is still progressing
with his Use Case. The transactions are so fast that the Bank Customer
Gets an impression that everything is happening between him and the
ATM.
Note this is NOT a part of Bank Customer’s Use Case but is interlocked
with it. If the network or Bank Computer fail, Bank Customer’s Use
Case has to be aborted.
ATMs need to be initiated and monitored for various
operational and safety reasons. For this, ATMs need
to send periodic reports.
Not asked for but to be thought of. Turn your creative imagination
ON…. To be checked with the client….let him turn it down…not your
creativity.
To receive cash and the related data from an
authorized representative of the Bank.
The access is to confidential cash bins which may have a physical lock
and key. The cash loader must be able to enter data relating to how
much cash he has loaded. This has to be reported to Bank Computer
through a separate use case associated with the Bank computer. This
can also be a part of “Send Periodic Reports to”

Any forgotten
actor?

Receive Cash and
related data

Commented [PVN12]: Not in the original model. This
would take care of a lot of interactions with the bank
computer. Keep it open for additions

Commented [PVN13]: This can be existing or new Actors
that automation demands. Creative imagination is required
here. Keep checking…delete it after all stakeholders agree
that all the Actors are well identified.

Now the Use Case Diagram can be drawn…if there is any use for it. See the next page.


Commented [PVN11]: Don’t just call it bank. Identify a
human or machine actor that actually interacts with the
system.

Page No 5 of 6

Hyderabad 500034
Mobile: 91 98660 71582
putchavn@yahoo.com,


Is it necessary? What additional information does it give with reference to the
Use Case Table? Send examples and reasons to kenablersys@yahoo.com
---III---


Page No 6 of 6

Use Case TABLE with Actors & Goals

Recommended

Recommended

More Related Content

What's hot

What's hot (20)

Viewers also liked

Viewers also liked (20)

Similar to Use Case TABLE with Actors & Goals

Similar to Use Case TABLE with Actors & Goals (20)

More from Putcha Narasimham

More from Putcha Narasimham (20)

Recently uploaded

Recently uploaded (20)

Use Case TABLE with Actors & Goals