Use Case Specification

Actor : Telephone Agent

Basic flow (USE CASE – FIND CUSTOMER)

 The use case begins with the agent opening the Online shopping application
 The agent selects the “Track customer” option
 The system opens the track customer page
 The agent enters the customer name and phone number and submits
 The system communicates with the customer registry database to find the customer associated with
the customer name and phone numbers entered
 The system displays the customer data
 The use case ends successfully
 Alternate flows are similar to basic flows in structure, in that they also describe the interaction
between the actor and the system, but they consider any and all possible alternate paths for the use
case to be completed successfully, including edge cases. Below is an example of alternate paths for
the same use case in the above example.

Alternative flow(USE CASE – FIND CUSTOMER)

Customer not found

If in step 5, the system does not find the customer in the database that is associated with the customer name
and phone number, then it will display the message “Customer not found” and the use case will resume at
step 4

Invalid name

If in step 4, the agent entered an invalid customer name data type, the system will display the message “Please
enter valid name” next to the name field and de-activates the submit button. The use case resumes at step 4.
See special requirements WC-1 for valid customer name data type

Invalid Phone number

If in step 4, the agent entered an invalid Phone number, the system will display the message “Please enter a
valid Phone number” next to the Phone number and de-activates the submit button. The use case resumes at
step 4. See special requirements WC-2 for valid phone number data type.

1.Brief Description:This use case describes how a Telephone Agent uses the OS system to Store Order Number
with list ofItems and time
2.ActorsI.1Telephone Agent
3.PreconditionsThere is an active network connection to the OS system.“Extract Order details” and “Extract
Customer details” use cases are executed.
4.Basic Flow of Events
1.The use case begins when the telephone agent selects the items that are chosen by the customer.
2.The list of items along with the item number and unit price are displayed in the OS system.
3.Telephone agent clicks on “Place order” button
4.The list of items with the order number and the time of order being placed are stored in the OS system.
5.Then the use case is completed successfully.
5.Alternative Flows
5.1Selected Item not available:If step 2 of basic flow, when the telephone agent selects list of items and places
orderthen if the item selected is not available
.1. OS system displays “Selected item not available. Item number: XXX”.
2.The use case resumes at step 1.
 5.2 Failure in display of items and its details:If in step 2 of the basic flow of events if the telephone agent is
unable to view the itemnumber and its unit price
1. Telephone agent selects the items again, even is if does not show thelist of items.
2. The use case resumes at Step2.

Usecase – Catagories

Description : The use case begins when the actor indicates the intent to view, update, add or delete
Categories record. It ends when the actor closes the Category form.

Actor – Admin

Pre-Condition: 1-The Categories record exists for editing/view.

2-The admin is logged in

Post Conditions : The Categories record is added, deleted or updated.

Usecase- Customer catalog

Actor - Admin

Description : The use case begins when the actor indicates the intent to view, update add or delete Customer’s
record. It ends when the actor closes the Customer form…

Pre-condition: 1-The Customer’s record exists for editing/delete

2-The actor is logged in

Post-conditions : The Customer’s record is added or updated.

Usecase : Order catalogue

Actor – Admin

Description : The use case begins when the actor indicates the intent to view orders detail of customers.

Pre-condation: 1-The order record exists for editing/view.

2-The actor is logged in.

Post-Condition: The actor dispatch or cancel the customer record.

Use Case Diagram:

 Online Shopping Application

«uses» Order Registry

*
Search Customer
Order details «uses»
*
Customer Catalog *
* ** *
*
* *
*
*
* «uses»
Order registry
Telephone Agent order number Admin
*

*
* «uses»
Customer catalog Add
Customer Name
«uses»
*

Customer Phone No. Delete

Add customer
details
* *
*
«uses» Order Number
*
Modify
«uses»
Customer * Place Order Order Time
*
* *
*
* Quantity
Item Price Item No.

«uses»

Cancel Order
* «uses»

Message Alert
* *

System clock
Activity Diagram

Telephone agent access system

Select the Item

Order Number Customer Name & No.

Add Item Cancel Item

Order Registry Customer Catolog

[Cancel]

Customer and order details Item Number,Quantity, Price Display

[Confirmation]

Display Total Price

Payment Process

Order Number & Time recorded