• No results found

Use Case Description

In document Online Ordering System Project (Page 38-45)

Use case name Maintain Staff

Brief Description This use case allows staff add, edit and search staff information.

Actor Adminsitrator

Main Flow

Actor Action System Response

1. Display Main Menu 3. Administrator select the “Maintain

Staff”

4. Display Add New Staff and Update Staff

Subflows:

S-1 Add New Staff

System auto generate staff ID when form load. Administrator key in new staff details. System validate key in new staff details. Adminsitrator press save button, then the system will add member record into database.

S-2 Update Staff

Administrator key in staff ID or username. System varify staff ID or username status and display staff details. Administrator press edit button and edit details. Staff press save button, system validate edited details and update staff database.

Alternative flows :

A-1 Step S-1 and S2 : if the data enter is invalid ‐ Display “ invalid data” message A-2 Step S1 : if the staff position is Administrator

‐ Auto generate staff id , the first character of staff id is “A” A-3 Step S1 : if the staff position is Staff

‐ Auto generate staff id , the first character of staff id is “S” A-3 Step S1: if the staff does not select “Done” button option

‐ System will not add new staff data

Maintain Member Module

Use case name Maintain Member

Brief Description This use case allows member add, edit and search member information.

Actor Member

Main Flow

Actor Action System Response

1. Display Main Menu 2. Member select the “register member” 3.Display registration form 4. Key in member details

5.Click save button 6. Validate member key in details

7.Display login form

8. Key in Username and password 9. Validate username and password 10. Display member main menu 11. Select View “my profile” 12. Display member profile details 13. Click edit button

14. Edit member details

15. Select Done button 16. Validate member edited details

17. Update member record Alternative flows :

A-1 Step 3 : if the username is exist

‐ Display “ This username has been use by another person”

A-2 Step 5 : if the date enter is invalid

‐ Display “ invalid data” message ‐ Cursor will point to the particular field

A-3 Step 15: if the member not select “Done” button option ‐ System will not update member data

Maintain Table Module

Use case name Maintain Staff

Brief Description This use case allows staff add, edit, delete and search table information.

Actor Adminsitrator

Main Flow

Actor Action System Response

1. Display Main Menu 4. Administrator select the “Maintain

Table”

4. Display Add, Update and Delete button.

Subflows:

S-1 Add New Table

Administrator key in new table details. Administrator press Done button to save new table information. The system validate staff key in details and add a record into table database

S-2 Update Table

Administrator key in table number, press search button. System diplays table information. Administrator press edit button and edit table information. System validate input data and update the table information into database.

S-2 Delete Table

Administrator key in table number and press search button, System display table information. Administrator press delete button. System prompt up a comfrimation massage “ are you sure want to delete the table”. Administrator were chosen confirm to delete the table. System will delete the table from database.

Alternative flows :

A-1 Step S-1 and S2 : if the data enter is invalid ‐ Display “ invalid data” message ‐

A-5 Step S-2: if the administrator does not select “Done” button option ‐ System will not update table data

Reservation, and Design Platform Party

Use case name Reservation, Pay payment and Design Platform Party

Brief Description This use case enable customer to make a reservation, inculded table and meal. After reserve table and meal, the this use case also allow member view payment and pay payment , andl also design platform party.

Actor Member

Main Flow

Actor Action System Response

1. Reservation form 2. Select date and time

3. Click search button 4. Verify the date and time and save reservation detail into reservation database.

5.Display table information

6. Select table number and add into reserved table

7. Click finish button 8. Update reservation detail into database and display reservation information.

9. Display back to reserve table form, continue to reserve meal and print button.

10. Click continue reserve meal

11. Display reserve meal page 12. Select food category

13. Enter food quantity

14. click order list button 15. Display reserve meal detail 16. Show back to reserve meal button , confirm delete meal item button and confirm reserve meal button.

17. Select comfirm reserve meal

18. System display pay payment page

19. Key in credit card details and click done

print receipt

21. Display back home page button, and go to design platform party button

22. Select go to design platform party button.

23. Display platform design page 24. Customize platform design

25. Select print platform design

26. Prompt up print window

Alternative flows :

A-1 Step S-4: if system have not generate reservation id ‐ System generate reservation id and display it

A-1 Step S-16: if member select confirm delete meal item button ‐ Customer select particular item is require to remove. ‐ System remove the item from data base

‐ System recalculate the total price at bottom of grid view

A-1 Step S-6 and S-16: if member select does not add any item or delete all item ‐ System display back to previous page function of button only

A-1 Step S-20: if member key in wrong data

Payment Module

Use case name Pay Payment

Brief Description This use case allows member computerized payment (cash) and e-payment via credit card .

Actor Member

Main Flow

Actor Action System Response

1. Display payment form after user comfirm about meal order with delivery or take away.

2.Display payment method option, which are credit card and cash 4. Select payment option and press done

option

6. Validate payment details

7. Save data into database and print receipt.

Alternative flows :

A-1 Step 4 : if member select payment option is credit card ‐ Display credit card form that require user key in

‐ System calculate deposit user require to pay and balance ‐ System validate user key in credit card details

A-2 Step 4 : if the member select payment option is cash ‐ Display the balance

A-3 Step 1 : if the member select order meal with delivery

‐ System calculate government tax, service charge, transport fees, total charge

A-4 Step 1: if the member select order meal with take away

‐ System calculate government tax, service charge and total charge

Generate Report

Use case name Generate Report

Brief Description This use case allows administrator to generate the customer annual sales report, daily member payment report, and daily reservation report

Actor Member

Main Flow

Actor Action System Response

1. Display main menu

2. Select “report option” 2.Display sub menu: annual sales report, daily member payment report, and daily reservation report

Subflow:

If the sub menu selected is annual sales report, the S-1: annual sales report If the sub menu selected is daily member payment report, the S-2: daily member payment report

If the sub menu selected is a daily reservation report, the S-3: daily reservation report

Alternative flows : S-1 Annual sales report

Administrator can view the report to know whole year of sale profit and know which month is better sales. When administrator clicks the print option, system will print the report.

S-2 Daily member payment report

Administrator can select specific date to view report, purpose is to know which member is haven’t pay payment and the day total payment collect and total balance is haven’t collect. . When administrator clicks the print option, system will print the report.

S-3 Daily reservation report

Administrator can view the report to know what is the table, what is the time, what is the meal and member detail on specific day. . When administrator clicks the print option, system will print the report.

3.4 Activity Diagram

In document Online Ordering System Project (Page 38-45)

Related documents