You are on page 1of 15

USE CASE DOCUMENT

<RETAIL STORE MANAGEMENT SYSTEM>

COEPD
SR NAGAR
HYDERABAD, TELANGANA, 500038

DATE

1
2
3
CHECK AVAILABILITY USE CASE

Name of Use Case: Check availability


Created By: Coepd Last Updated By: Raghavendra kuthadi

Date Created: 20/04/19 Last Revision Date: xx/xx/xx

Description: The retailer checks for the availability of goods in the system.

Actors: retailer
Preconditions: 1. retailer has pre-approval in retail store management system.
2. Active network connection.

Postconditions: Successful post condition


1.check stock availability is performed successfully.

Failure Post Condition


2. check stock availability is not performed.

Flow: 1. The use case begins when the retailer signals the system that he/she
wants to check for the availability of the goods in the store.
2. System displays the search form.
3. Retailer enters the goods name and submit the search form.
4. System displays the availability of the goods in quantity.
5. Use case ends.

4
Alternative Flows: In step 4 of the basic flow

1. If the goods are not available the system displays the message
required not available”.

Exceptions: 1. NA

Special Requirements: 1. The system must support simultaneous users.

5
PLACE ORDER USE CASE

Name of Use Case: Place order


Created By: Coepd Last Updated By: Raghavendra kuthadi

Date Created: 15/04/19 Last Revision Date: xx/xx/xx

Description: The retailer places order of the goods if they are not available in the store.

Actors: Retailer
Preconditions: 1.The retailer has pre-approval in retail store management system.
2.Active network connection.

Postconditions: Successful post condition


1.order has been placed successfully. (recorded in the system)

Failure Post Condition


2.order has not been recorded.

Flow: 1. The use case begins when the retailer signals the system that he/she
wants to order goods.
2. System displays the order form.
3. System prompts the retailer to fill the order form.
4. retailer enter the goods name and quantity in order form and submits.
5. upon submissions by the retailer system updates the order form in the
database.

6
Alternative Flows: 1. NA

Exceptions: 2. NA

Special Requirements: 5. The system must support simultaneous users(RETAILER).

7
MAKE PAYMENT USE CASE.

Name of Use Case: MAKE PAYMENT


Created By: Coepd Last Updated By: Raghavendra kuthadi

Date Created: 15/04/19 Last Revision Date: xx/xx/xx

Description: The use case make payment describes the functionality of how the retailer
records the payment information which is made to the supplier after
receiving order.
Actors: Retailer
Preconditions 1.Retailer has pre-approval in POST system.
2.Active network connection.

Postconditions: Successful post condition


1.payment has been recorded which is made to the supplier

Failure Post Condition


2.payment information has not been recorded.

Flow:
1.The use case begins when the retailer signals the system that he/she
wants to record the payment to supplier information into the system
database.

2.System displays the payment to supplier form.

3.System prompts the retailer to add the payment information to the form.

4.retailer adds the payment info, which includes supplier name, payment
value.

8
5.System prompts the retailer to select the mode of payment from a
dropdown menu which includes cash, third party.

6. The retailer clicks on the submit button.


7. Use case ends.

Alternative Flows: 1. NA

Exceptions: 3. NA

Special Requirements: 8. The system must support simultaneous users.

9
Name of Use Case: Accept payment
Created By: Coepd Last Updated By: Raghavendra kuthadi

Date Created: 15/04/19 Last Revision Date: xx/xx/xx

Description: retailer accepts payment from the customer for the items.

Actors: Retailer
Preconditions: 1.retailer has pre-approval in retail store management system.
2.Active network connection.
3.Ensure enough cash in change is available.

Postconditions: Successful post condition


1.Payment has been received successfully.

Failure Post Condition


2.Paymnet has not been received.

10
Flow: 1.The use case begins when the retailer signals the system that he/she
wants accept payment.
Case A: accept payment by cash.
1.retailer selects the mode of payment as cash.
2.System prompts the retailer to enter the amount given by customer.
3.retailer enters the amount in denominations.
4. system calculates balance amount to be given to the customer.
5. system displays the amount to be returned to the customer.
“ As Change “.
6.accept by cash ends.

Case B: accept payment by card.


1.Retailer selects the mode of payment as card.
2.system prompts the retailer to enter amount.
3.retailer enters the amount.
4.system prompts the retailer to validate pin.
5.system displays a message payment accepted.
6.accept payment by card ends.

Use case ends.

Alternative Flows: In step 4 of case B of the normal flow, if the card pin is incorrect.

1.The system should send a message “invalid credentials”.


2.System should prompt to re-enter the credentials.

Exceptions: 1.During payment by card if the bank account doesn’t have sufficient funds
payment must abort.

11
Special Requirements: 1.The system must support simultaneous users(retailers).

ARRANGE GOODS USE CASE

Name of Use Case: ARRANGE GOODS


Created By: Coepd Last Updated By: Raghavendra kuthadi

Date Created: 15/04/19 Last Revision Date: xx/xx/xx

Description: This use case describes the functionality of arrange goods in the system so
that the goods can be arranged by price or by product.
Actors: Retailer
Preconditions: 1.Active network connection.
2. retailer has pre-approval in retail store management system.

12
Postconditions: Successful post condition
1.goods have been arranged successfully.

Failure Post Condition


2.goods are not arranged successfully.

Flow: The use case begins when the retailer signals the system that he wants to
arrange goods.
CASE A: Arrange goods by price
1. The system prompts the user to select the arrange by price form a
dropdown list which include arrange by price, arrange by product.
2. The retailer selects arrange by price.
3. The system arranges the goods by price.
4. System displays the arranged goods by price.

CASE B: Arrange goods by product.


5. The system prompts the user to select the arrange by product form a
dropdown list which include arrange by price, arrange by product.
6. The retailer selects arrange by product.
7. The system arranges the goods by product.
8. System displays the arranged goods by product.

Use case ends.

Alternative Flows: NA.

Exceptions: NA.

13
Special Requirements: NA.

ACTIVITY DIAGRAM

14
15