Embed Size (px)
Citation preview
ANALYSIS AND DESIGN
DOCUMENTS
FOR DEVELOPMENT OF
RESTAURANT E-MENU PROTOTYPE
Project: E-menu on iPad for Thai restaurant
Subject: Research outcome#1
Content: Functional Requirements, UML Use case and Class Diagrams, and Workflow and Process diagrams.
Created by Traitet Th.
Created Date 31 July 2012
Revised Date 6 Sep 2012
Revision No. 1.0
Document Name O01-001
1) FUNCTIONAL REQUIREMENTS
2
1) FUNCTIONAL REQUIREMENTS
3
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
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 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.
4E-m
en
u o
n iP
ad
for
Resta
ura
nt
Cu
sto
mers
1) FUNCTIONAL REQUIREMENTS (CONT.)
Functional Requirements (E-menu application on iPad)
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.
5E-m
en
u o
n iP
ad
for
Resta
ura
nt
Cu
sto
mers
1) FUNCTIONAL REQUIREMENTS (CONT.)
Functional Requirements (E-menu application on Web)
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
6E-m
en
u o
n iP
ad
for
Resta
ura
nt
Sta
ff
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 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.
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 take 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 Dish
Cook 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
Simple Current Restaurant System (As-it system)
6.2) DESIGN OF RESTAURANT SERVICE PROCESS
For developing the e-menu prototype (To-be system)
7) E-MENU WORKFLOW
DIAGRAM (E-MENU)
20
7) WORKFLOW DIAGRAM
For developing the e-menu prototype
