This article tries to explain major parts of Use case and present users a simple yet effective template to capture requirements.

1. Use Case Specifications
1. Brief Description
This functionality holds the customer qualification and his education background like
education qualification, passing year of qualification and selected details of the customer.
1.1 Use Case Objective
The objective of this use case is to define the basic, alternate, and exception process flows
that will be useful while creating the use case model during design phase.
1.2 Related Use Cases
1. Individual Customer
2. Actors
2.1 Primary Actors
Actor Name Functional Components
Customer Maker Creates the Education details of the new customer.
Amends the existing record.
Saves the record
Deletes the record.
Clears the record
Exit from the screen.
2.2 Secondary Actors
Actor Name Functional Components
External Interfaces/Systems
Create a new record.
Amends the existing record.
Deletes the Record
System Auth Authorizes the Record
3. Pre-Conditions
Individual Customer record should have been created or already existed in the system
4. Activation
 Create Customer Education Details

2.  From the option. Customer --> Individual Customer --> Create Customer  “
 Modify/Delete Customer Education Details
 From the option. Customer --> Individual Customer --> Modify Customer 
“Education”
 From any external interfaces/systems.
 Authorize Customer Education
 From the option. Customer --> Individual Customer --> Authorize Customer
(Actor forwards the complete individual customer screen for authorization)
 System auto authorizes the records.
5. Post-Conditions
 Individual customer with its Education Details is created in the system.
 Changes to the active authorized/un-authorized individual customer education details
are saved in the system.
 Audit trail is maintained
 History is maintained for the changes done in the data
6. Assumptions
 Specialist users are needed for maintaining customer function and they are referred as
Accounting User in the use cases. Accounting user will need to understand the business
logic and their characteristics and be adequately trained in the function. Accounting
user will also need to understand the consequences of their actions of maintaining
products and the implications for other functions within the System.
 Customer Author is the only Actor role to be granted the ability to amend a status, e.g.
‘Authorise’ a newly created customer with his Education Details.
6.1 Basic Flow
6.1.1 Initiate Education Details Record
Step
Number Actor Action SystemAction
1. Actor clicks on “Education”
activity from Individual
Customer Details screen.
From menu option  customer
 individual  create customer
 click on education tab
System displays the blank ‘education details’
screen

3. Step
Number Actor Action SystemAction
2. Actor enters the below details in
the Individual education details
as identified in data sheet.
a) Qualification
b) Education Classification
c) Specialization
d) Institution / University
e) Passing Year
It shall be mandatory for the actor to enter/ select
all the mentioned fields else an error message will
be displayed
3.
4.
5.
6.1.2 Modification of Un-authorized Record
Step
Number
Actor Action SystemAction
1. Actor clicks on “Education”
activity from Individual Customer
Details screen.
From menu option  customer
 individual customer  create
customer  “Education”
System displays the blank ‘education’ detail screen
with list of un-authorized records in the grid below
2. Actor selects the record for
modification by selecting the
checkbox displayed next to the
record.
If the actor selects more than one record for
modification, system displays an error message
Note: Actor can modify only one record at a time.
3.
4.
6.2 Alternate Flows
6.2.1 View Education Details
Step
Number
Actor Action SystemAction
1. Actor clicks on customer 
individual customer  modify
System displays blank ‘search’ for the actor to
enter the search parameters and filter authorized

4. Step
Number
Actor Action SystemAction
customer records.
2. Actor enters the search parameter
and clicks on ‘search’ button
System displays list of authorized records based
on the search parameters specified by the actor
6.2.2 Customer Details
Step
Number Actor Action SystemAction
1. Actor navigates to the ‘customer
detail’ screen by clicking on
menu option customer 
Individual customer  create
customer/ modify customer
System navigates the actor to “Customer
Details” screen.
6.3 Exception Flows
6.3.1 Business Rule Validation Failed
Step
Number
Actor Action SystemAction
1. Actor saves/submits the data. System checks for business rules and shows the
message for failed business rule with “OK”
2. Actor presses “OK” button Message disappears and focus returns to Customer
Education Detail screen
6.3.2 Mandatory Information not Entered
Step
Number
Actor Action SystemAction
1. Actor saves/submits the data. System checks for mandatory rules and shows the
message for failed business rule with “OK”
2. Actor presses “OK” button Message disappears and focus returns to Customer
Education Detail screen
6.4 Specific Requirements
1. The external interfaces/systems should be able to communicate with the system
using System APIs.
7. Issues & Questions

5. # Date Description Resolution Originator Owner Status
8. Additional Information
It is possible to populate the all the data in combo for institution type/university
but if that profile haven't in this category they can also a option of “others”.

6. Use Case Supplementary Sections
9. Business Rules
None
10. Messages
10.1 Message if mandatory fields are not selected/entered
“It is mandatory to enter….”
10.2 Message if more than one checkbox is selected for modification
“One record can be modified at a time”
10.3 Message if no checkbox is selected for deletion
“Select record for deletion”

7. Use Case Data
11. Data: Education Details
Input Field
Element
Name Description
Data
Type
Data
Item
Mode Source LOV Rules Required
Qualification Combo Box Char
Select
Only
Education
Table
List of
Qualification
type
The
default
value
should
be
“select”.
yes
Passing Year Combo Box numeric
Select
Only
Education
Table
List of valid
years
The
default
value
should
be
“select
year”.
yes
Command Fields
Command
Name
Type Action
Add Button
On pressing this button the system will add the credit card details
on grid.
Save Button On click of the button the data would be saved
Update Button
On click of the button, actor would be navigated to the Modify
Customer Screen with the selected Customer's record.
12. Screen Layout: Education Details
Attach Sample Screen Here.
13. Appendices
13.1 Reports Appendices
Audit Trail functionality & Report will be a standard activity and need to be incorporated
in a different document.
13.2 Letters Appendices
None
13.3 Interfaces Appendices
None