ANALYSIS AND DESIGN DOCUMENT

FOR DEVELOPMENT OFRESTAURANT E-MENU PROTOTYPE

Project: E-menu on iPad for Thai restaurant

Subject: Research outcome#1

Content: Functional Requirements, Use Case Diagram, Class Diagram and Work flow diagrams

Created by Traitet Th.

Created Date 31 July 2012

Revised Date 22 Aug 2012

Revision No. 1.0

Document Name O01-001

1) FUNCTIONAL REQUIREMENTS

2

1) FUNCTIONAL REQUIREMENTS3

E-menu system consists of1. E-menu application on iPad for restaurant

customersMain 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

• Starter, Main course, drinks and sweet

• Operate services requested• Call waiter, main course and bill

1) FUNCTIONAL REQUIREMENTS

Functional Requirements (E-menu application on iPad)

Restaurant customers can order food and drinks on e-menu. Restaurant customers can search menu items by menu

categories such as appetisers, main dishes (main course), drinks and sweets

Restaurant customers can check list of ordering items before confirming orders.

Restaurant customers can remove ordering items before confirming order.

Restaurant customers can request waiting staff on e-menu Restaurant customers can request for billing on e-menu. Restaurant customers can request main dishes (main course) on

e-menu after they have appetisers. Restaurant customers can check status of ordering items on e-

menu, such as queuing, cooking, serving and served. Restaurant customers can select a language to make orders.

4E-

men

u on

iPad

for

Rest

aura

nt

Cust

omer

s

1) FUNCTIONAL REQUIREMENTS (CONT.)

Functional Requirements (E-menu application on iPad)

E-menu can provide basic information for customers, such as picture, name and price of each menu item.

E-menu can provide additional information, such as menu description and levels of spicy and recommended items.

E-menu can summarise list of order including total price and a number of items ordered.

The system can transfer information from iPad e-menu to a kitchen and bar for preparing food and drinks.

The system can transfer information from iPad e-menu to a cashier for preparing payment.

The system can transfer information from iPad e-menu to show list of services requested by restaurant customers.

5E-

men

u on

iPad

for

Rest

aura

nt

Cust

omer

s

1) FUNCTIONAL REQUIREMENTS (CONT.)

Functional Requirements (E-menu application on Web)

The system can operate table for a new customer group such as opening a new table and closing table or order.

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 of preparing, cooking and serving.

Waiting staff can check list of order requested by customers

6E-

men

u on

iPad

for

Rest

aura

nt S

taff

2) NON-FUNCTIONAL REQUIREMENTS

7

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 beautiful images of food and drinks for restaurant customers to be easy to understand menu description.

E-menu on iPad can consume web services provided by a external server through internet connection.

8

2) NON-FUNCTIONAL REQUIREMENTS

(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 spend time less than 2 seconds.

9

3) USE CASE DIAGRAM

10

3) USE CASE DIAGRAM

4) CLASS DIAGRAM

12

4) CLASS DIAGRAM For developing the e-menu prototype

5) ER DIAGRAM

14

5.1) ER-DIAGRAMFor developing the e-menu prototype

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

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

17

18

Order from Customer

Drinks Starters Main Dishes Sweet

Taken Order(3 copies)

1. Kitchen2. Bar3. Front-bar

Cook Starters Prepare Main Dishes

Serve Starter

Request to eat Main

DishCook Main

Dishes

Serve Main Dishes

Post on board in front

of the kitchen

Serve Drinks and Sweet

Give to bar

Food ordering processes6.1) DESIGN OF RESTAURANT SERVICE PROCESS

Current Restaurant System

6.2) DESIGN OF RESTAURANT SERVICE PROCESS

For developing the e-menu prototype

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

20

7) WORKFLOW DIAGRAM

For developing the e-menu prototype