Used Case.docx

Used-case description

Use-case:

Inventory check

Primary actor:

Owner

Goal in context:

To monitor and update the balance of the inventory.

Preconditions:

The owner has a valid username and password

Trigger:

The owner needs access to the system to monitor the inventories of the business.

Scenario:

1. The owner logs on to the system. 2. The owner selects inventory check from the Main menu.. 3. The module for the inventory balances is shown. 4. The owner has given access to the system. 5. The owner can add items to the inventories.

Exceptions:

The username and password is invalid.

Use-case:

Monitor the sales

Primary actor:

Owner

Goal in context:

To check the accuracy of the sales report

Preconditions:

The transactions are known

Trigger:

The owner needs to evaluate the cost and profit of the businees for the period.

Scenario:

1. The owner logs on to the system. 2. The owner selects the sales button form the main menu. 3. The systems lists the items sold, cost and sales of each item. 4. The system displays the total sales, cost of goods sold, and profit. 5. The owner confirms the information about the sales.

Exceptions:

The username and password is invalid.

Use-case:

Input the customer’s orders

Primary actor:

Cashier

Goal in context:

To record the orders of the customers

Preconditions:

The quantity of the items ordered is known.

Trigger:

The cashier needs to input and check the orders of the customers.

Scenario:

1. The cashier logs on to the system. 2. The system prompts the order form. 3. The cashier check the items or packages acquired by the customers and inputs the quantity of the items. 4. The cashiers clicks the proceed button. 5. The system displays the list and amount of items ordered. 6. The system computes the total cost, payment and balance of the customer. 7. The cashier proceeds to the customer’s information form. 8. The customer fills up the form and confirms it to be processed. 9. The system prompts a message of the successful transaction.

Exceptions:

Use-case:

View the needed information for the event.

Primary actor:

Employee

Goal in context:

To view the informations of the event

Preconditions:

The employee has a valid username and password.

Trigger:

The employees need to know the necessary informations of the event to render the service.

Scenario:

1. The employee logs on to the system. 2. The employee selects the event info button from the main menu. 3. The system displays the informations of the event. 4. The employee has given an option to print or close the informations. 5. The information is closed or printed.

Exceptions:

The username and password is invalid.