Use Case Model

A Use Case Model describes the proposed functionality of new system. A Use Case represents a
discrete unit of interaction between a user (human or machine) and the system.

List of Actors

 Customer; this person check items, buy them and give feedback.

 Administration; this person manages the whole system.

List of Use Cases

 Browse Catalog; customer read superficially a list of things.

 Search Catalog; customer finds the desired item.

 Create Account; customer creates account to buy item.

 Login/Register; customer login to the site to buy item.

 Manage Product; customer manages the selected item.

 Select Product; customer selects the desired item.

 Manage Cart; customer can easily manage his/her cart.

 Add to Cart; customer adds item to cart.

 Add to Wish List; customer adds the item to his/her wish list to buy the item later.

 View Cart; customer views cart to see what he/she selected.

 Edit Item Quality; customer tells the quality/brand that he/she wants.

 Place Order; customer order the selected item.

 Make Payment; customer pays for item.

 By Credit Card; customer can use credit card for payment.

 By Hand; customer pays by hand when he receive item.

 By Cheque; customer pays by cheque.

 Manage Catalog; administration manage the whole catalog. Add new items for customer
to search and buy.

 Receive Orders; administration receives order from customer.

 Check Payment; administration checks the payment paid by customer.

 Dispatch Order; administration verify the order and dispatch it.

 Manage Measures; administration manages the quantity of products.

 Manage Complains; administration manage complains by customers.

System Level Use Case Diagram

Browse Catalog
Receive Orders

Search Catalog

Login/Register Check Payment

Manage Catalog

Dispatch Order
<<include>>
Create Account Manage Product
Administration

Manage Measure
Select Product
Customer

Manage Complains

Place Order

Manage Cart

<<include>>
Add to Cart

Edit Item Quantity

View Cart

Add to Wish List

Make Payment
«extends»

«extends»
«extends»
By Cheque

By Credit Card

By Hand

Daraz.pk Online Shopping System in Pakistan

Fully dressed Format of Use Case
Browse Catalog

Section: Main
Name: Browse Catalog
Actors: Customer
Purpose: See the Products to buy.
Description: The customer browse the catalog. See the new items to buy a
unique and desired item.
Cross References: None
Pre-Conditions None
Successful Post- See the items available on site.
Conditions
Failure Post- Can’t see the items.
Conditions
Typical Course of Events
Actor Action System Response
1 Customer check the items to buy 2 Items appear.
3 Customer selects the desired item from listed item 4 List of items appear.
Alternative Course
Step 1: List don’t appear if internet is not available.

Search Catalog

Section: Main
Name: Search catalog
Actors: Customer
Purpose: Provide a list of items available on site for customer.
Description: Customer can search the desired item by category, by price, by
brand etc.
Cross References: None
Pre-Conditions Home page of Daraz.pk is appear before searching.
Successful Post- List of desired item is appear with price and other specifications.
Conditions
Failure Post- List didn’t appear.
Conditions
Typical Course of Events
Actor Action System Response
1 Type the name of item 2 List is appear
3 Select the price range 4 List appear according to price
Alternative Course
Step 3: Desired item didn’t found

Create account

Section: Main
Name: Create account
Actors: Customer
Purpose: To make customer registered to buy product.
Description: An interface appears holding some blanks to make account for
order.
Cross References: None
Pre-Conditions None
Successful Post- Customer’s account is created.
Conditions
Failure Post- Customer account is not created.
Conditions
Typical Course of Events
Actor Action System Response
1 Selects the option ‘create account’ 2 A new interface appear.
3 Fills the require information 4 Form is filled.
5 Clicks the ‘confirm’ button. 6 Account is created.
Alternative Course
Step 4 Account is not created.

Login/Register

Section: Main
Name: Login/register
Actors: Customer
Purpose: Login the customer to buy product.
Description: Customer login to the account and add the selected product to
cart and order for it.
Cross References: None
Pre-Conditions Account must be created.
Successful Post- Customer is login.
Conditions
Failure Post- Customer is not login.
Conditions
Typical Course of Events
Actor Action System Response
1 Enters the email/password and click 2 Logged.
Login.
Alternative Course
Step-7. Invalid user name or password.

Manage product

Section: Main
Name: Manage product
Actors: Customer
Purpose: Provide facility to customer to manage his/her products.
Description: Customer is able to manage his/her selected products. He/she
can order for it.
 Cross References: Req4.
Pre-Conditions Customer is logged in.
Successful Post- Customer manages his/her products.
Conditions
Failure Post- Products are not managed.
Conditions
Typical Course of Events
Actor Action System Response
1 Manages the products. 2 Products are managed.
Alternative Course
Step 5: Interface didn’t appear.

Select product

Section: Main
Name: Select product
Actors: Customer
Purpose: Selects product easily.
Description: The customer will see the products and select the desired product
to buy.
Cross References: None
Pre-Conditions User is logged in the system.
Successful Post- Product is selected.
Conditions
Failure Post- Product is not selected.
Conditions
Typical Course of Events
Actor Action System Response
1 Selects the product to buy. 2 Product is selected.
Alternative Course
Step 6: Product is not available.
 Step 7: Product is finished.

Place order

Section: Main
Name: Place order
Actors: Customer
Purpose: Order the selected product.
Description: Customer will place his/her order by a defined way.

Cross References: Req3, Req4.

Pre-Conditions Customer is logged in.
Successful Post- Order is placed.
Conditions
Failure Post- Order is not placed.
Conditions
Typical Course of Events
Actor Action System Response
1 Selects the product to buy. 2 Product is selected.
3 Place the order to buy. Give 4 Order is placed.
information about how he pays and
where to deliver etc.
Alternative Course
Step 8: Invalid order
Step 9: Invalid address/information.

Manage Cart

Section: Main
Name: Manage cart
Actors: Customer
Purpose: Provide facility for customer to manager his/her cart.
 Description: Customer can manage his/her cart. He/she can do anything with
cart like add, delete etc.
Cross References: Req4.
Pre-Conditions Customer is logged in. Cart is empty.
Successful Post- Cart is managed.
Conditions
Failure Post- Cart is not managed.
Conditions
Typical Course of Events
Actor Action System Response
1 Selects the option ‘manage cart’ 2 Interface appear to manage cart.

Alternative Course
Step-7. Cart is not filled

Add to cart

Section: Main
Name: Add to cart
Actors: Customer
Purpose: Customer can add new products to cart.
Description: Customer has to select product and then add to his/her cart.

Cross References: None

Pre-Conditions None
Successful Post- Product is added to cart.
Conditions
Failure Post- Product is not added to cart.
Conditions
Typical Course of Events
Actor Action System Response
1 Selects the product to add 2 Product is selected.
3 Add the selected product to cart. 4 Product is added to cart.
 Alternative Course
Step 8: Product is not available yet.

Add to wish list

Section: Main
Name: Add to wish list
Actors: Customer
Purpose: Customer can add product to a list he/she wants.
Description: Customer adds the product to his/her Wish List to buy it later.

Cross References: None

Pre-Conditions None
Successful Post- Product is added to Wish List.
Conditions
Failure Post- Product is not added to Wish List.
Conditions
Typical Course of Events
Actor Action System Response
1 Selects the product that he/she likes. 2 Product is selected.
3 Add product to Wish List 4 Product is added.
Alternative Course
Step 9: Product is not available.

View cart

Section: Main
Name: View cart
Actors: Customer
Purpose: Customer can view his/her cart.
Description: Customer click on the option View Cart and can check what is in
his/her cart.
 Cross References: None
Pre-Conditions None
Successful Post- Cart is viewed.
Conditions
Failure Post- Cart us not viewed.
Conditions
Typical Course of Events
Actor Action System Response
1 Selects ‘View cart’. 2 Cart viewed.
Alternative Course
Step 10: Cart is empty.

Edit item quality

Section: Main
Name: Edit item quality
Actors: Customer
Purpose: Customer can edit the quality of product he/she wants.
Description: Customer will add the quality as brand, size, color etc.

Cross References: None

Pre-Conditions Product is selected.
Successful Post- Quality is edit.
Conditions
Failure Post- Quality is not edit.
Conditions
Typical Course of Events
Actor Action System Response
1 Selects the product. 2 Product is selected.
3 Selects the quality or specification 4 Edit.
that he/she wants.
 Alternative Course
Step 11: Product quality is invalid.

Make payment

Section: Main
Name: Make payment
Actors: Customer
Purpose: To provide an easy way for customer to pay for product.
Description: The customer will select the product and its specification and
then order it and pay for it by desired way.
Cross References: Req6, Req7.
Pre-Conditions Customer is logged in. product is selected.
Successful Post- Product is selected and payment method is selected.
Conditions
Failure Post- Not selected.
Conditions
Typical Course of Events
Actor Action System Response
1 Selects the ‘buy product’ 2 Selected.
3 Selects a payment method he/she 4 Selected.
wants.
Alternative Course
Step 12: Payment is insufficient.

By credit card

Section: Main
Name: By credit card
Actors: Customer
Purpose: Customer can pay by a credit card.
Description: Customer will choose the option ‘by credit card’ to pay from a
 card.
Cross References: None
Pre-Conditions Product is selected and added to cart and ready to buy.
Successful Post- Payment method is selected and order is placed and delivered.
Conditions
Failure Post- Payment is insufficient. Card number is invalid.
Conditions
Typical Course of Events
Actor Action System Response
1 Selects the payment method as ‘by 2 Selected.
credit card’.
Alternative Course
Step 13: Credit card it empty / money is not sufficient or card
number is invalid.
Step 14: Invalid credit card.

By hand

Section: Main
Name: By hand
Actors: Customer
Purpose: Customer can pay on delivery by hand.
Description: Customer will choose the option ‘by hand’ to pay on delivery.

Cross References: None

Pre-Conditions Product is selected and added to cart and ready to buy.
Successful Post- Payment method is selected and order is placed and delivered.
Conditions
Failure Post- Address is invalid or customer refused to receive the product.
Conditions
Typical Course of Events
Actor Action System Response
1 Selects the payment method as ‘by 2 Selected.
hand’.
Alternative Course
Step 15: Order is not received.

By cheque

Section: Main
Name: By cheque
Actors: Customer
Purpose: Customer can pay by a cheque.
Description: Customer will choose the option ‘by cheque’ to pay on delivery.

Cross References: None

Pre-Conditions Product is selected and added to cart and ready to buy.
Successful Post- Payment method is selected and order is placed and delivered.
Conditions
Failure Post- Payment is insufficient
Conditions
Typical Course of Events
Actor Action System Response
1 Selects the payment method as ‘by 2 Selected.
cheque’.
Alternative Course
Step 16: Signature is invalid.
Step 17: Amount is not sufficient.

Manage catalog

Section: Main
Name: Manage catalog
Actors: Administration
Purpose: Provide facility to manage catalog for easy management.
Description: The admin will manage the catalog for his ease.

Cross References: None

Pre-Conditions Home page is open.
Successful Post- New interface appear to manage a catalog.
Conditions
Failure Post- Catalog didn’t appear.
Conditions
Typical Course of Events
Actor Action System Response
1 Selects the ‘manage catalog’ to 2 Managed.
manage items
Alternative Course
Step 18: Catalog is not managed.

Receive order

Section: Main
Name: Receive order
Actors: Administration
Purpose: To receive order from customers.
Description: The order of customer is send to administration to confirm it and
deliver it on time.
Cross References: None
Pre-Conditions No order is received or order is pending.
Successful Post- Order is received and confirmed.
Conditions
Failure Post- Invalid order.
Conditions
Typical Course of Events
Actor Action System Response
1 Open the order in notification. 2 Order viewed.
3 Confirms the order. 4 Order confirmed.
5 Product is send to customer. 6 Notification is clear.
Alternative Course
Step 19: Notification is not received.
Step 20: Color is not available yet.
Step 21: Size is not available yet.

Check payment

Section: Main
Name: Check payment
Actors: Administration
Purpose: Administration checks the payment whether it is correct or not.
Description: Administration will confirm the order and check the payment and
also check the payment method selected by the customer.
Cross References: None
Pre-Conditions Order is confirmed.
Successful Post- Payment is confirmed and order is send.
Conditions
Failure Post- Payment is not sufficient.
Conditions
Typical Course of Events
Actor Action System Response
1 Checks the payment. 2 Checked.
Alternative Course
Step 22: Payment is not sufficient.

Dispatch order

Section: Main
Name: Dispatch order
Actors: Administration
Purpose: Send order to customer.
Description: Administration will confirm the order, check the payment and
send order to customer.
Cross References: None
Pre-Conditions Order is confirmed.
Successful Post- Order sent.
Conditions
Failure Post- Order is not sent.
Conditions
Typical Course of Events
Actor Action System Response
1 Selects the ‘dispatch’ option to send 2 Order is dispatched.
product to customer.
Alternative Course
Step 23: Order is not sent
Manage measure

Section: Main
Name: Manage measure
Actors: Administration
Purpose: To supervise the quantity of products.
Description: Handle the amount of products. See which product is required
and which product is demanded by customer more.
Cross References: None
Pre-Conditions None
Successful Post- List of amount of products is shown.
Conditions
Failure Post- List is not shown.
Conditions
Typical Course of Events
Actor Action System Response
1 See the product quantity to check 2 List appear.
which is in stock.
Alternative Course
Step 24: List didn’t appear

Manage complains

Section: Main
Name: Manage complains
Actors: Administration
Purpose: To provide better products.
Description: Administration will see complains and try to make product and
system better.
Cross References: None
Pre-Conditions Product is used.
Successful Post- Complain is received by administration.
Conditions
Failure Post- Complain is not received.
Conditions
Typical Course of Events
Actor Action System Response
1 See the notification of complain. 2 Notification appear.
Alternative Course
Step 25: Products is not used.
Step 26: Feedback is not given.