System in use story Hectic lifestyle has made most of the people lack sufficient time to cook.

Usually people will opt for fast food but on regular basis. Not only the price is expensive, this habit is unhealthy. An entrepreneur had thought of solution to this problem by providing homemade food delivery service. There will be a variety of homemade dishes everyday prepared by a skilled chef, and the customers can choose the menu for their lunch or dinner based on their preference and with affordable price. In order to allow customers to order the dishes more conveniently and Internet access is almost available for everyone, the entrepreneur decides to come out with an online system named Mangkuk Tingkat Online as one of the mediums to provide services. This system allows customers to place their orders via online based on menu list posted on the website. The customers can choose whether they wanted to have food delivered for lunch, dinner or both. The customers can set the time and date for their food to be delivered. Orders will be stored in the database. The receptionist can access the system with administrations approval (login password) and will be in charge of receiving orders from customers and checking the schedule stored in the database whether the booking slot on that particular day is full or not. The receptionist will then respond to the customers whether they can proceed with the booking or not by sending confirmation messages. Inside the confirmation message, customer will be informed whether the booking is success or not. If it is successful, customers will receive attached documents such as receipt. Payment must be made by the customers at least one day before the delivery date or the booking will be cancelled. Once the order is confirmed the food will be delivered on the agreed time and date. The chef can also enter the website as one of the admins and use it to update the menus from time to time. The programmer will make maintenance to website, including updating promotions, making videos and animations and checking and troubleshooting webpage and system errors.

Use case 1: Placing Order Use case Description: Placing order is a use case that allow customer to choose the available menu and place their orders. Primary flow: 1. 2. 3. 4. 5. The use case starts when the customer enters the website. The customer searches for the menu category. The customer enters the date for receiving order. The menu list on that particular date will be displayed on website. The customer chooses his/her preferred menu. If preferred menu is not available, proceed to AF1. 6. The customer fills in the necessary particulars and the menu list. 7. The customer clicks the menu confirmation button and sends the order. If the order is unable to be sent, proceed to EF1. 8. The use case ends. AF1: 1. Preferred menu is not available, the customer makes a request for special booking. 2. The customer sends a menu list which he or she wants to book. 3. The use case ends. EF1: 1. The error message will be displayed. 2. The customer is asked to reload the page and repeat the booking process. 3. The use case ends. Use Case 2. Make payment Description: Make payment is a use case that allow customer to make payment for the order. Primary flow: 1. 2. 3. 4. 5. 6. 7. 8. 9. 10. The use case begins when customer received food confirmation details. Customer will click the payment button. Customer will choose payment method. If payment is made through online banking, Alternate Flow 1 AF1 is performed. If payment is made through PayPal/Credit Card, Alternate Flow 2 AF2 is performed. If payment is made through wired transfer, Alternate Flow 3 AF3 is performed. The system will verify the payment. If the payment is not verified EF1 is performed. Website will display verification message. Payment receipt is displayed. The use case ends.

Alternate Flow AF1: 1. 2. 3. 4. 5. 6. The website will generate payment form The customer will enter account no The system will verify the payment. If the payment is not verified EF1 is performed. Website will display verification message. Payment receipt is displayed. The use case ends.

Alternate Flow 2 AF2: 1. 2. 3. 4. 5. 6. Website will redirect to Paypal website. The customer will enter account no The system will verify the payment. If the payment is not verified EF1 is performed. Website will display verification message. Payment receipt is displayed. The use case ends.

Alternate Flow 3 AF3: 1. Customer provide proof of payment like account number, date of payment and amount of payment. 2. The system will verify the payment. If the payment is not verified EF1 is performed. 3. Website will display verification message. 4. Payment receipt is displayed. 5. The use case ends. Error Flow1 EF1: 1. 2. 3. 6. 7. 8. Website display payment status. Gives customer option to re-enter payment or cancel order. If customer chooses re-enter payment return to no 3 of primary flow. If cancel order, Website will display verification message. Payment receipt is displayed. The use case ends.

Pre - Condition: Customers have agreed with the payment value. Use Case 3. Take Order Use case description i. ii. take order use case allow the receptionist to retrieve the order from the customer pre order condition: the use case start when there are order from customer

Primary flow i. ii. the use case begin when the receptionist login into the website the database request the user name and the password

iii. iv. v. vi. vii. viii. ix.

the receptionist key in the user name and password the receptionist check the incoming order booking database display the order from the customer the receptionist check the schedule of the chef the database display the booking schedule of the chef. If the booking schedule full, Alternate Flow 1 AF1 is performed the receptionist add the order to the booking schedule The use case end

Alternate flow, AF1 i. ii. iii. The receptions will response to customer for another booking The receptionist ask customer whether to change date or the menu The use case end

Use Case 4. Confirm order Description: Confirm order is a use case that allows the receptionist to confirm with the customers whether their booking/order is successful. Primary Flow: 1. The use case begins when the receptionist login to the website to check the food the customers had ordered. 2. The receptionist will send email to inform the customers about the booking status. 3. The receptionist will confirm the date and the delivery address with the customers. 4. If the customers confirm the order, Alternate Flow 1 AF1 is performed. 5. If not, Alternate Flow AF2 is performed. 6. If the server is down when sending the message Error Flow 1 is performed. 7. The use case ends. Alternate Flow 1 AF1: 1. 2. 3. 4. Payment instructions are sent to the customers. Food order list/ details and date of food delivery are sent. Online payment bill is displayed. The use case ends.

Alternate Flow 2 AF2: 1. Receptionist will communicate with the customers and find solutions to solve their ordering problems. 2. The use case ends.

Error Flow 1 EF1: 1. The website reloads the message. 2. The use case ends.

Use case 5: Updating Menu Use case Description: Updating menu allows chef to upload the menu list in the system for customers to choose and place their orders. Primary flow: 1. The use case starts when the chef enters the website. 2. The chef enters the password for verification. If the verification is not successful, proceed to AF1. 3. The chef searches for upload category. 4. The chef uploads the food photos and enters the full description about food and also the price. If not successful, proceed to AF2. 5. The chef posts the photos with descriptions after clicking the upload confirmation button. 6. The use case ends. AF1: 1. 2. 3. 4. Error message will be displayed. The chef reenters the password. If password is correct, the chef searches for upload category. The chef uploads the food photos and enters the full description about food and also the price. If not successful, proceed to AF2. 5. The chef posts the photos with descriptions after clicking the upload confirmation button. 6. The use case ends. AF2: 1. The error message will be displayed. 2. The chef is asked to reload the page and repeat the upload process. 3. If successful, the chef posts the photos with descriptions after clicking the upload confirmation button. 4. The use case ends.

Use Case 5: Making Maintenance Primary flow -The use of case begin when programmer login into the website as an admin

-All the setting of the website will be displayed -Programmer need to be choose either to check error (AF1) or update promotion (AF2) Alternate flow 1 (AF1) -The programmer will check each application one by one -If error, the programmer will save all the data first then (EF1) will be performed -If OK, the programmer will recheck the website application -Programmer logout from website -Use case end Error flow 1 (EF1) -Programmer reset the website application -Programmer also changed or put extra features into the website for better performance - If the error has fixed, the programmer recheck the website application -Programmer log out from website -Use case end Alternate flow 2 (AF2) -Programmer need to be alert of the latest promotion -Confirm the promotion with the chef -Programmer update the picture, video or animation of the promotion -The new design will be displayed -Programmer logout from website -Use case end

Comments: Relationships and arrows are not drawn properly. Please do so, okay?

Placing Order

Customer

Making Payment

receptionist

Taking Order

Confirming Order
Chef

Database

Updating Menu
Programmer

Performing Maintenance