Professional Documents
Culture Documents
Description: The retailer checks for the availability of goods in the system.
Actors: Retailer
Basic 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.
3. Retailer enters the goods name and submit the search form.
Alternative Flows:
1. If the goods are not available the system displays the message required not available”.
Special Requirements:
Description: The retailer places order of the goods if they are not available in the store.
Actors: Retailer
Preconditions:
Basic Flow:
1. The use case begins when the retailer signals the system that he/she wants to order goods.
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.
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
Basic 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.
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.
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.
Description: Retailer accepts payment from the customer for the items.
Actors: Retailer
Preconditions:
Basic Flow:
1.The use case begins when the retailer signals the system that he/she wants accept payment.
“ As Change “.
Alternative Flows:
Exceptions: 1.During payment by card if the bank account doesn’t have sufficient funds payment
must abort.
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
Basic Flow:
The use case begins when the retailer signals the system that he wants to arrange goods.
1. The system prompts the user to select the arrange by price form a dropdown list which
include arrange by price, arrange 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.
Check availability
Order Goods
*
*
** Make Payments
**
* *
«extends» By Product
Retailer
Arrange Goods
* «extends»
By Price
*
* *
*
By Credit By Cash
Activity Diagram
Check Goods availability
[Not available
]
[Available
]
Order the goods
Receive goods
Make Payments
Arrange Goods
Prepare bill
Receive Payment
Cash Credit
Complete Sale