This document provides analysis and design documents for developing an e-menu prototype for a Thai restaurant, including: 1. Functional requirements for an e-menu iPad application and web application for restaurant staff and customers. 2. Non-functional requirements regarding system performance, security, and data integration. 3. UML diagrams including a use case diagram and class diagram to model the system. 4. Entity-relationship and revised entity-relationship diagrams to design the database. 5. Process diagrams depicting the current and proposed e-menu-based food ordering workflows in the restaurant.

1. ANALYSIS AND DESIGN
DOCUMENTS
FOR DEVELOPMENT OF
RESTAURANT E - MENU PROTOTYPE
Created by Traitet Th.
Project: E-menu on iPad for Thai restaurant
Created Date 31 July 2012
Subject: Research outcome#1 Revised Date 6 Sep 2012
Revision No. 1.0
Content: Functional Requirements, UML Use case and Class
Document Name O01-001
Diagrams, and Workflow and Process diagrams.

2. 1) FUNCTIONAL REQUIREMENTS
2

3. 3 1) FUNCTIONAL REQUIREMENTS
E-menu system consists of
1. E-menu application on iPad for restaurant
customers
Main features
• Ordering food & drinks
• Confirm and view orders
• Request services
2. E-menu web application for restaurant staff
• Manage table
• Open & Close table
• Operate order
• Drinks, Starter, Main course, and Sweet
Operate services requested
• Call waiter, main course and bill

4. 4 1) FUNCTIONAL REQUIREMENTS
Functional Requirements (E-menu application on iPad)
Restaurant Customers
E-menu on iPad for
 Restaurant customers can order food and drinks on e-menu.
 Restaurant customers can search menu items by menu categories such
as appetisers, main course, sweets and drinks.
 Restaurant customers can check ordered items before confirming.
 Restaurant customers can cancel ordered items before confirming.
 Restaurant customers can request waiting staff on e-menu
 Restaurant customers can request billing on e-menu.
 Restaurant customers can request delivery of main course on e-menu
after they have finished their appetisers.
 Restaurant customers can check status of ordered items, such as
queuing, cooking, serving and served, on e-menu.
 Restaurant customers can select different languages to make their order.

5. 1) FUNCTIONAL REQUIREMENTS
5
( CONT.)
Restaurant Customers
Functional Requirements (E-menu application on iPad)
E-menu on iPad for
 E-menu can provide basic information for customers, such as pictures,
names and prices of each menu item.
 E-menu can provide additional information, such as menu descriptions,
levels of spic and recommended items.
 E-menu can summarise list of order including total price and number of
items ordered.
 The system can transfer information from iPad e-menu to a kitchen and
bar for preparation of food and drinks.
 The system can transfer information from iPad e-menu to a cashier to
prepare for payment.
 The system can transfer information from iPad e-menu to show list of
services requested by restaurant customers.

6. 1) FUNCTIONAL REQUIREMENTS
6
( CONT.)
Functional Requirements (E-menu application on Web)
E-menu on iPad for
Restaurant Staff
 The system can operate table for a new customer groups such as
opening or closing a new table and Ordering.
 Waiting staff can monitor and operate services requested by customers
such as a request of main course, waiter and billing.
 Chef and waiting staff can view and maintain orders transferred from
iPad e-menus to prepare food and drinks for customers.
 Chef and waiting staff can record ordering status for preparing, cooking
and serving.
 Waiting staff can check order list requested by customers

7. 2) NON-FUNCTIONAL
REQUIREMENTS
7

8. 8 2) NON-FUNCTIONAL REQUIREMENTS
Non-functional Requirements
 Real-time Information can be transferred from iPad e-menu to a
kitchen, cashier, and bar though wireless connection.
 User interfaces’ e-menu should be user-friendly and easy to use.
 E-menu should provide useful information including authentic images of
food and drinks so restaurant customers can easily understand menu
description.
 E-menu on iPad can consume web services provided by a external
server through internet connection.

9. 2) NON-FUNCTIONAL REQUIREMENTS
9
(CONT.)
Non-functional Requirements
 E-menu system must provide web services to integrate data between
iPad e-menu, back office application and a database.
 E-menu system must have adequate security to access system
information such as Web service authentication.
 E-menu system should record log of each transaction including
transaction, user name and time to make analytics reports in the future.
 E-menu system must provide real-time information with quick
response. All transactions must take less than 2 seconds.

10. 3) USE CASE DIAGRAM
10

11. 3) USE CASE DIAGRAM

12. 4) CLASS DIAGRAM
12

13. 4) CLASS DIAGRAM
For developing the e-menu prototype

14. 5) ER DIAGRAM
14

15. 5.1) ER-DIAGRAM
For developing the e-menu prototype

16. 5.2) REVISED ER-DIAGRAM
(To develop a real e-menu application in the future)

17. 6) DESIGN OF RESTAURANT
SERVICE PROCESS (E-MENU)
17

18. Food ordering processes
6.1) DESIGN OF RESTAURANT SERVICE PROCESS
18 Simple Current Restaurant System (As-it system)
Order from Customer
Drinks Starters Main Dishes Sweet
1. Kitchen
2. Bar
3. Front-bar
Taken Order
(3 copies)
Post on board in
Prepare Main
front of the Cook Starters Give to bar
Dishes
kitchen
Request to eat Cook Main
Main Dish Dishes
Serve Main Serve Drinks and
Serve Starter
Dishes Sweet

19. 6.2) DESIGN OF RESTAURANT SERVICE PROCESS
For developing the e-menu prototype (To-be system)

20. 7) E-MENU WORKFLOW
DIAGRAM (E-MENU)
20

21. 7) WORKFLOW DIAGRAM
For developing the e-menu prototype