Online Restaurant Management System.
BORANG PENGESAHAN STATUS TESIS*
JUD'UL-. O N L m RESTAURANT MANAGEMENT SYSTEM
SESI P E N G m 2007 / 2008
Saya HANISAH BINTI MD TAHA
(I-IURUF BESAR)
mengaku membcnarkan -is (PSM/SarjmaDoktor Fa1safa.h) hi& s i m p di
PerpustakaanFakulti Tehologi Maklumat dan Komukikasi dengan syarat-syarat
kegunaan seperti berikut:
1. Tesis dan projek hakmilik Umversiti Teknikal Kebangsaan Malaysia M e l h
2. Perpustakaan Fakulti Teknologi Maklumat dan Komunikasi dibenarkan membuat
salinan untuk tujuan pengajian &.a.
3. Perpustakaan Fkulti Teknologi Maklumat dan Komunikasi dibenarkan membuat
salinan tesis ini sebagai bahan pertukaran antara institusi pengajian tinggi.
4. * * Sila tandakan (0
SULIT
TERHAD
(Mengandungi maklumat yang berdarjah
keselamatan atau kepentingan Malaysia seperti
termaktub di dalam AKTA RAHSIA RASMI
1972)
(Mengandungi maklumat TERHAD yang
&tmtukan oleh mganisasi/badandi mana
penyelidikan dijalankan)
Alamat tetap: No l.lorong S i a h 14,
Seberang Java,
13700 Prai, Pulau Pinang.
DrAnton Satria Prabuwon~
Tarikh: 28 A~ril2008
Tarikh: 28 AWil2008
CATATAN: *Tesis dimaksudkan sebagai Laporan Akhir Projek Sarjana Muda (PSM)
* * J itesis ini SULIT atau TERHAD, sila lampirkan surat daripada
pihak berkuasa.
ONLINE R E S T A U W T MANAGEMENT SYSTEM (ORMS)
HANISAH BINTI MD TAHA
This report is submitted in partial fulfillment of the requirements for the Bachelor of
Computer Science (Database Management)
FACULTY OF INFORMATION AND COMMUNICATION TECHNOLOGY
UNIVERSITI TEKNIKAL MALAYSIA MELAKA
2008
DECLARATION
I hereby declare that this project report entitled
ONLINE RESTAURANT MANAGEMENT SYSTEM
is written by me and is my own effort and that no part has been plagiarized without
citations.
:
Date: 28 April 2008
SUPERVISOR:
Date: 28 April 2008
STUDENT
iii
DEDICATION
To my beloved parents, lecturers and fkiends.
ACKNOWLEDGEMENTS
In the name of Allah the Almighty and Most Merciful.. .....
First and foremost, I would like to take this opportunity to express my
appreciation to my supervisor, Dr.Anton Satria Prabuwono who has helped me a lot in
sharing her knowledge and giving me useful guide and advises for the project. During
the duration of the project, Dr.Anton Satria Prabuwono has giving her full effort in
encourage me to excel in this project.
Besides that, I would like to express my gratitude to all lecturers who has shared
their knowledge and skills with me which enables me to fulfill this project especially to
Encik Sazalinsyah Bin Razali and Mrs.Siti Azirah Asmai.
Last but not least, I would like to thank to my family and friends who has given
me tremendous support and encouragement during this time.
ABSTRACT
"Online Restaurant Management System (ORMS)" is web application to
restaurant management. This system wake to provide service facility to restaurant and
also to the customer. The services that are provided is food ordering and reservation
table management by the customer through the system online, customer information
management and waiter information management, menu information management and
report, Main objective build the system this is to provide ordering and reservation
service by online to the customer. With this system online, ordering and reservation
management will become easier and systematic to replace traditional system where are
still using W r . Furthermore, this system is applicable any time and where also
customer. During the development of ORMS, the methodology being used is
Prototyping model. Each process during the development process is followed by each
phases in Prototyping model, Software and hardware used are AppServ, Macromedia
Dreamweaver 8, Microsoft Visio 2003, Apache serve and MySQL database.
Furthermore, this project will develop for restaurants management and enhance business
in system business by online. Others, this project to facilitate customer for make online
ordering and reservation.
"Online Restaurant Management System ( O M )
"
adalah pcnggunaan jaringan
untuk pengurusan restoran. Sistem ini dibangunkan untuk memberi kemudahan
perkhidmatan kepada pihak restoran dan juga kepada pelanggan. Di antara perkhidmatan
yang disediakan ialah pengurusan tempahan makanan dan tempahan meja oleh
pelanggan melalui sistem online, pengurusan maklumat pelanggan dan maklumat
penpelayan, pengurusan maklumat makanan dan laporan. Objektif utama
membangunkan sistern ini adalah untuk memberi perkhidmatan tempahan makanan clan
tempahan meja secara online kepada pelanggan. Dengan sistem online ini, pengurusan
tempahan makamn dan tempahan meja akm menjadi lebih mudah dan sistematik untuk
menggantikan sistem tradisional yang masih menggunakan kertas. Tarnbahan pula,
sistem ini boleh digumkan pada bila-bii masa dan di mana jua peianggan berada. Di
sepanjang pembangunan ORMS, model Prototyping telah dipilih. Setiap proses yang
terdapat di dalam model tersebut dijadikan panduan dalam pembangunan sistem ini.
Perkakasan dan perisian yang digunakan adalah AppServ, Macromedia Dreamweaver 8,
Micrctsoft Visio 2003, Apache server dm pmgkalan data MySQL. Tambahan pula,
projek ini dibangunkan untuk pengurusan restoran dan meningkatkan perniagaan di
dalarn system perniagaan secara online. Selain itu, projek ini untuk memudahkan
pelanggan di dalam pengurusan tempahan secara online.
vii
TABLE OF CONTENTS
CHAPTER
S W C T
DECLARATION
DEDICATION
ACKNOWLEDGEMENTS
ABSTRACT
ABSTRAK
TABLE OF CONTENTS
LIST OF TABLES
LIST OF FIGURES
LIST OF ABBREVIATIONS
LIST OF APPENDICES
CHAPTER I
INTRODUCTION
1.1 Project Background
1.2 Problem Statement
1.3 Objective
1.4 Scope
1.4.1 Target User
1.4.2 Target Area
1.4.3 Project Deliverables
1.5 Project Significance
1.5 Expected Output
1-7 Conclusion
CHAPTER 11 LITERATURE REVIEW AND PROJECT
METHODOLOGY
2.1 Introduction
2,2 Facts and Findings
2.2.1 Domain
2.2.2 Existing System
2.2.3 Technique
2.3 Project Methodology
PAGE
..
11
iii
iv
v
vi
vii
X
xi
xii
xiii
2.3.1 Prototype Model
2.3.2 Database Life Cycle (DBLC)
2.3.3 Database Initial Study
2.3.4 Database Design
2.3.5 Implementation And Loading
2.3.6 Testing And Evaluation
2.3.7 Operation
2.3.8 Maintenance And Evaluation
Project Requirements
2.4.1
Software requirement
Hardware requirement
2.4.2
Other requirement
2.4.3
Project Schedule and Milestones
Conclusion
CHAPTER 111
ANALYSIS
3.1 Introduction
3.2 Problem Analysis
Background Of The Current
3.2.1
System
Problem Statement
3.2.2
Requirement Analysis
Data Requirement
3.3.1
3.3.2
Functional Requirement
3.3.2.1
Scope
3.3.2.2
Context Diagram
3,3.2.3 Data Flow Diagram
@FD)
3.3.3 Non-functional Requirement
3.3.4
Others Requirement
3.3.4.1
Software Requirement
3.3.4.2
Hardware Requirement
3.3.4.3 Network Requirement
Conclusion
DESIGN
Introduction
High-Level Design
4.2.1
System Architecture
User Interface Design
4.2.2
4.2.2.1
Navigation Design
4.2.2.2 Input Design
4.2.2.3
Output Design
4.2.3
Database Design
4.2.3.1
Conceptual Database
Design
4.2.3.2
Logical Database
Design
DBMS Selection
4.2.3.3
Detailed Design
Software Specification
4.3.1
4.3.2 Physical Database Design
Conclusion
IMPLEMENTATION
Introduction
Software Development Environment Setup
5.2.1
Software, Hardware and Network
Development Environment Setup
5.2.2 Database Development
Environment Setup
Database Implementation
Software Configuration Management
5.4.1
Configuration Environment Setup
Implementation Status
Conclusion
TESTING
Introduction
Test Plan
6.2.1
TestOrgankation
6.2.2 Test Environment
Test Schedule
6.2.3
Test Strategy
6.3.1 Classes of tests
Test Design
Test Description
6.4.1
6.4.2 Test Data
Test Results and Analysis
Conclusion
PROJECT CONCLUSION
Observation on Weaknesses and Strengths
7.1.1
Strength
7.1.2 Weaknesses
Proposition for Improvement
Contribution
Conclusion
REFERENCES
TABLE
TITLE
2.1
2.2
Software Requirement For Development Tool
Software Requirement For Operating System / Web
Server
Software Requirement For Database System
Hardware Requirement
Other Requirement
Software Requirements For Server Side
Software Requirement For Client Side
Hardware Requirement For Client And Server Side
Hardware Requirements
Netwcrrk Requirement
File Input/Output For Customer Login
File InputIOutput For Add Staff Information
File InputIOutput For Add Menu
File Input/Output For Menu Information
F i e Input/Output For Waiter Information
Development Status
Individual Involved In Testing Phases
Test Environment Specification
Test Schedule For ORMS
Test Cases, Description And Expected R d t For
Login Module
Test Data Of Admin And Staff Login
Test Result For Login Module
Comparison between current system and ORMS
PAGE
28
28
LIST OF FIGURJ3S
DIAGRAM
TITLE
Saloma Theatre Restaurant Online Reservation
Beryani King Online Ordering
DJU Catering Restaurant Online Ordering
Table-Booking.Com Reservation Table
Prototype Model
Database Life Cycle (Dblc)
Context Diagram For Current System
DFD Level 0 For Restaurant Pak Hus& Tom
Yam
Context Diagram For ORMS
DFD Level 0 For ORMS
DFD Level 1For Menu Process
DFD Level 1For Customer Process
DFD Level 1For Authentication Process
DFD Level 1For Ordering And Reservation
Process
DFD Level 1For Feedback Process
DFD Level 1For Waiter Process
DFD Level 1For Report Process
System Archittxhre
Navigation Design
Entity Relationship Wi (ERD)
AppServ Control Panel To Start The Database
Service
Configuration Of Database Connection
PAGE
LIST OF ABBREVIATIONS
ORMS
ICT
ECSB
MTC
PHP
MYSQL
DFD
ERD
DBLC
DBMS
SQL
LAN
PC
PSM
API
WYSNVYG
HTML
CSS
DDL
DCL
IDE
Online Restaurant Management System
Information And Communications Technology
Expressive Creations Sdn. Bhd.
Malaysia Tourism Centre
Pre-Hypertext Processor
Structured Query Language
Data Flow Diagram
Entity Relationship Diagram
Database Life Cycle
Database Management System
Structured Quexy Language
Local Area Network
Personal Computer
Projek Sarjana Muda
Application Programming Interface
What Yon See Is What You Get
Hypertext Markup Language
Cascading Style Sheets
Data Definition Language
Data Control Language
Integrated Development Environment
xiii
LIST OF APPENDICES
APPENDIX
A
TITLE
MILESTONE OF PSM
Table A. 1
Milestone of PSMl
Table A.2
Milestone of PSM2
B
GANTT CHART OF PSM
C
DATA REQULREMENT
Table C. 1
Data Requirement for Admin Data
Table C.2
Data Requirement for Customer Data
Table C.3
Data Requirement for Feedback Data
Table C.4
Table C.5
Table C.6
Data Requirement for Menu Data
Data Requirement for Tempahan Data
Data Requirement for Waiter Data
USER INTERFACE DESIGN
Figure D. 1 Homepage
Figure D.2
Our menu page
Figure D.3
How to order page
Figure D.4
Customer login interface
New customer registration
Figure D.5
Figure D.6
Customer ordering and reservation page
Figure D.7
Customer ordering and reservation report
Figure D.8
Figure D.9
Figure D.10
Figure D.ll
Figure D.12
Figure D.13
Figure D.14
Page
Admin login interface
Adrnin homepage
Menu information page
Add new menu page
Update menu interface
Waiter information page
Add new waiter page
PAGE
xiv
Figure D. 15 Search and update waiter inf'tion page
Figure D. 16 Waiter schedule page
INPUT DESIGN
Table E. 1
Attribute of input design
OUTPUT DESIGN
Figure F. 1
Output design for customer online ordering
information
DATA DICTIONARY
Table G. 1
Data dictionary for admin data
Table G.2
Data dictionary for customer data
Table G.3
Data dictionary for feedback data
Table G.4
Table G.5
Table G.6
Data dictionary for menu data
Data dictionary for tempahan data
Data dictionary for waiter data
NORMALIZATION
Figure H. 1
Third normal form (3 NF) for admi.table
Figure H.2
Third normal form (3 NF) for customer
table
Third
normal form (3 NF) for menu table
Figure H.3
Figure H.4
Third normal form (3 NF) for tempahan
table
Figure H.5
Third normal form (3 NF) for waiter table
Third normal form (3 NF) for feedback
Figure H.6
table
CREATE TABLE
Figure L 1
Create table admin
Figure 1.2
Create table feedback
Create table customer
Figure 1.3
Figure 1.4
Create table menu
Figure 1.5
Create table tempahan
Create table waiter
Figure 1.6
ASSIGNING ADMIN AND CUSTOMER LOGIN
Figure J.1
Figure 5.2
Assigning Admin Login
Assigning customer login
TEST DESCRIPTION
Table K. 1
Test cases, description and expected result
for customer registration module
Table K.2
Test cases, description and expected result
for online ordering module
Table K.3
Test cases, description and expected result
for menu module
Test cases, description and expected result
Table K.4
for customer waiter module
Table K.5
Test cases, description and expected result
for customer feedback module
Table K.6
Test cases, description and expected result
for customer generate report module
TEST DATA
Table L. 1
Test Data of customer registration data
Test Data of feedback data
Table L.2
Table L.3
Test Data of online ordering data
Table L.4
Test Data of menu data
Table L.5
Test Data of waiter data
TEST RESULTS AND ANALYSIS
Table M. 1
Test Result for customer registration data
Table M.2
Test Result for feedback data
Test Result for online ordering data
Table M.3
Test Result for menu data
Table M.4
Table M.5
Test Result for waiter data
BAB I
INTRODUCTION
1.1
Project Background
Ontine Restaurant management system is the system for manage the restaurant
business. The main point of developing this system is to help restaurant administrator
manage the restaurant business and help customer for online ordering and reserve table.
The project is developing ,
many restaurants have a lot difficult to
manage the business such as customer ordering and reservation table. By using manual
customer ordering is difficult to waiter keep the correct customer information and maybe
loss the customer information.
So, online restaurant management system will develop to help the restaurant
administratorto manage restaurant management and for customer make their online
ordering and reservation table. Other than that, this project is to upgrade the manual
system and make the business easily to access and systematic.
12
Problem Statement
Nowadays, many restaurants manage their business by manual especially take
customer ordering. Today, restaurant waiter takes the customer ordering by manual
system with using paper. This is problem for restaurant waiter the probability lost and
duplicates custumer information Additionally, it would affect to reputation restaurant in
operate management of ordering.
Besides, the restaurant waiter information also by manual system kept use paper
and this is difficult for restaurant administrator to find waiter information, probability
missing the paper and difficult to arrange the schedule. Sometimes, waiter information
and customer information is important to restaurant administrator for reference in the
future.
Furthermore, restaurant side needs management in the section menu. This is the
important to restaurant waikr to manage the menu. Besides this section is for customer
viewer the menu that restaurant prepmed and make their ordering.
As a result, the current system (manual system) is not effective and efficient to
use anymore because the current system cannot save, manage and monitor the restaurant
waiter infbrmatiun, menu information, customer adering infomation and generate
report well.
Based on the problems stated above, the objectives of the project are:
i.
to develop online odering and reservation system in restaurant
ii.
to develop use interface for online restaurant management system
iii.
to provide online menu information for customer
1A
Scope
This section consist of three components which is target user, target area and
project deliverables.
1.4.1
Target User
The groups of user that had been identified to use the system are customer and
administrator.
This user will register to be a member to use the online system of this online
restaurant management system (ORMS). This online ordering divided into two type of
customer, it is customer dinein ordering and take-away ordering. For din-in ordering,
customer will view menu, make online ordering and make a reservation table. But takeaway ordering, customer can view menu and online ordering without reservation table.
After customer make online ordering, customer can take ordering the date that customer
was choose during make online ordering. Event though, customer must amfirm online
ordering with restaurant three days before customer take the ordering for dine-in
customer and for take-away customer will be confirm one hour before it whether by
email or phone.
Administrator is the person who will manage the entire system. This type of user
will also do maintenance and control the application of this system. Administrator takes
a responsibility to register new customer, register new waitex, register new menu into
database, and etc.
1.4.2
Target Area
This system will be placed at restaurant.
Regarding to the module that had been identified, the flow of an activity will be
described in term of customer registration module, customer online ordering and
reservation module, waiter moduk, ftedback module, menu module and generate report
module.
Customer Registration Module
Customer ~lcgistrdionmodule contains customer's infixmation such as customer
personal information and other information related to that customer. Then, all of this
information recorded into database.
Customer O n h e Ordering A d Reservation Module
Customer online ordering and reservation module provides a form that needs to
be fulfilling in term of ordering food and reservation table via online.
Waiter Module
Waiter module contains waiter information such as waiter personal information,
task schedule and other information related to that waiter. Then, all of this information
recorded into database.
Feedback Module
Based on food or everything about the restaurant, customer can send any
suggestion or comment to the restaurant with feedback form. From this form, side of
restaurant will know their weaknesses and strengths.
Menu Module
Menu module is food that restaurant pqmredfor customer. This module,
customer can view the menu and make decision for order.
Generate Report Module
System provides an option for generate a report. The contents of the report as the
followitlg:
1.
The report of customer ordering and reservation table.
2.
Customer's information and waiter information.
3.
Suggatbn or comment that customer insertat feedback form
4.
Profit business for restaurant
1.5
Project Significance
This system will be going to help customer and administrator in restaurant
especially part of online ordering and reservation table. Most of restaurant has a problem
of the ordering and reservation table. The result of odine odering and reservation table
will give customer easy to make ordering and reservation table online and hopefully can
smoothen up the job of administrator and waiter. This system also produces a
computerized system in defining the best solution in each ordering and reservation
problem faces by customer and administrator.
1.6
Expected Output
The expected output from this project is a system-based that will be able to store
customer's information, waiter's information, menu's information, store customer
information of online ordering and reservation information and customer's suggestion
and generate profit business report. Otherwise this system will change form manual
system to axup-
system.
ORMS are developed as a system-based. Chapter I described each problem
occurred by using the manual system. Project objective and project scope identified the
solution for each of the problem. Pmject Significance also being explains to convince
benefits that can be gathered from this system. This system hopefully can overcome the
problem in the current system. Chapter I1 elaborates the Literature Review and Project
Methodology.
JUD'UL-. O N L m RESTAURANT MANAGEMENT SYSTEM
SESI P E N G m 2007 / 2008
Saya HANISAH BINTI MD TAHA
(I-IURUF BESAR)
mengaku membcnarkan -is (PSM/SarjmaDoktor Fa1safa.h) hi& s i m p di
PerpustakaanFakulti Tehologi Maklumat dan Komukikasi dengan syarat-syarat
kegunaan seperti berikut:
1. Tesis dan projek hakmilik Umversiti Teknikal Kebangsaan Malaysia M e l h
2. Perpustakaan Fakulti Teknologi Maklumat dan Komunikasi dibenarkan membuat
salinan untuk tujuan pengajian &.a.
3. Perpustakaan Fkulti Teknologi Maklumat dan Komunikasi dibenarkan membuat
salinan tesis ini sebagai bahan pertukaran antara institusi pengajian tinggi.
4. * * Sila tandakan (0
SULIT
TERHAD
(Mengandungi maklumat yang berdarjah
keselamatan atau kepentingan Malaysia seperti
termaktub di dalam AKTA RAHSIA RASMI
1972)
(Mengandungi maklumat TERHAD yang
&tmtukan oleh mganisasi/badandi mana
penyelidikan dijalankan)
Alamat tetap: No l.lorong S i a h 14,
Seberang Java,
13700 Prai, Pulau Pinang.
DrAnton Satria Prabuwon~
Tarikh: 28 A~ril2008
Tarikh: 28 AWil2008
CATATAN: *Tesis dimaksudkan sebagai Laporan Akhir Projek Sarjana Muda (PSM)
* * J itesis ini SULIT atau TERHAD, sila lampirkan surat daripada
pihak berkuasa.
ONLINE R E S T A U W T MANAGEMENT SYSTEM (ORMS)
HANISAH BINTI MD TAHA
This report is submitted in partial fulfillment of the requirements for the Bachelor of
Computer Science (Database Management)
FACULTY OF INFORMATION AND COMMUNICATION TECHNOLOGY
UNIVERSITI TEKNIKAL MALAYSIA MELAKA
2008
DECLARATION
I hereby declare that this project report entitled
ONLINE RESTAURANT MANAGEMENT SYSTEM
is written by me and is my own effort and that no part has been plagiarized without
citations.
:
Date: 28 April 2008
SUPERVISOR:
Date: 28 April 2008
STUDENT
iii
DEDICATION
To my beloved parents, lecturers and fkiends.
ACKNOWLEDGEMENTS
In the name of Allah the Almighty and Most Merciful.. .....
First and foremost, I would like to take this opportunity to express my
appreciation to my supervisor, Dr.Anton Satria Prabuwono who has helped me a lot in
sharing her knowledge and giving me useful guide and advises for the project. During
the duration of the project, Dr.Anton Satria Prabuwono has giving her full effort in
encourage me to excel in this project.
Besides that, I would like to express my gratitude to all lecturers who has shared
their knowledge and skills with me which enables me to fulfill this project especially to
Encik Sazalinsyah Bin Razali and Mrs.Siti Azirah Asmai.
Last but not least, I would like to thank to my family and friends who has given
me tremendous support and encouragement during this time.
ABSTRACT
"Online Restaurant Management System (ORMS)" is web application to
restaurant management. This system wake to provide service facility to restaurant and
also to the customer. The services that are provided is food ordering and reservation
table management by the customer through the system online, customer information
management and waiter information management, menu information management and
report, Main objective build the system this is to provide ordering and reservation
service by online to the customer. With this system online, ordering and reservation
management will become easier and systematic to replace traditional system where are
still using W r . Furthermore, this system is applicable any time and where also
customer. During the development of ORMS, the methodology being used is
Prototyping model. Each process during the development process is followed by each
phases in Prototyping model, Software and hardware used are AppServ, Macromedia
Dreamweaver 8, Microsoft Visio 2003, Apache serve and MySQL database.
Furthermore, this project will develop for restaurants management and enhance business
in system business by online. Others, this project to facilitate customer for make online
ordering and reservation.
"Online Restaurant Management System ( O M )
"
adalah pcnggunaan jaringan
untuk pengurusan restoran. Sistem ini dibangunkan untuk memberi kemudahan
perkhidmatan kepada pihak restoran dan juga kepada pelanggan. Di antara perkhidmatan
yang disediakan ialah pengurusan tempahan makanan dan tempahan meja oleh
pelanggan melalui sistem online, pengurusan maklumat pelanggan dan maklumat
penpelayan, pengurusan maklumat makanan dan laporan. Objektif utama
membangunkan sistern ini adalah untuk memberi perkhidmatan tempahan makanan clan
tempahan meja secara online kepada pelanggan. Dengan sistem online ini, pengurusan
tempahan makamn dan tempahan meja akm menjadi lebih mudah dan sistematik untuk
menggantikan sistem tradisional yang masih menggunakan kertas. Tarnbahan pula,
sistem ini boleh digumkan pada bila-bii masa dan di mana jua peianggan berada. Di
sepanjang pembangunan ORMS, model Prototyping telah dipilih. Setiap proses yang
terdapat di dalam model tersebut dijadikan panduan dalam pembangunan sistem ini.
Perkakasan dan perisian yang digunakan adalah AppServ, Macromedia Dreamweaver 8,
Micrctsoft Visio 2003, Apache server dm pmgkalan data MySQL. Tambahan pula,
projek ini dibangunkan untuk pengurusan restoran dan meningkatkan perniagaan di
dalarn system perniagaan secara online. Selain itu, projek ini untuk memudahkan
pelanggan di dalam pengurusan tempahan secara online.
vii
TABLE OF CONTENTS
CHAPTER
S W C T
DECLARATION
DEDICATION
ACKNOWLEDGEMENTS
ABSTRACT
ABSTRAK
TABLE OF CONTENTS
LIST OF TABLES
LIST OF FIGURES
LIST OF ABBREVIATIONS
LIST OF APPENDICES
CHAPTER I
INTRODUCTION
1.1 Project Background
1.2 Problem Statement
1.3 Objective
1.4 Scope
1.4.1 Target User
1.4.2 Target Area
1.4.3 Project Deliverables
1.5 Project Significance
1.5 Expected Output
1-7 Conclusion
CHAPTER 11 LITERATURE REVIEW AND PROJECT
METHODOLOGY
2.1 Introduction
2,2 Facts and Findings
2.2.1 Domain
2.2.2 Existing System
2.2.3 Technique
2.3 Project Methodology
PAGE
..
11
iii
iv
v
vi
vii
X
xi
xii
xiii
2.3.1 Prototype Model
2.3.2 Database Life Cycle (DBLC)
2.3.3 Database Initial Study
2.3.4 Database Design
2.3.5 Implementation And Loading
2.3.6 Testing And Evaluation
2.3.7 Operation
2.3.8 Maintenance And Evaluation
Project Requirements
2.4.1
Software requirement
Hardware requirement
2.4.2
Other requirement
2.4.3
Project Schedule and Milestones
Conclusion
CHAPTER 111
ANALYSIS
3.1 Introduction
3.2 Problem Analysis
Background Of The Current
3.2.1
System
Problem Statement
3.2.2
Requirement Analysis
Data Requirement
3.3.1
3.3.2
Functional Requirement
3.3.2.1
Scope
3.3.2.2
Context Diagram
3,3.2.3 Data Flow Diagram
@FD)
3.3.3 Non-functional Requirement
3.3.4
Others Requirement
3.3.4.1
Software Requirement
3.3.4.2
Hardware Requirement
3.3.4.3 Network Requirement
Conclusion
DESIGN
Introduction
High-Level Design
4.2.1
System Architecture
User Interface Design
4.2.2
4.2.2.1
Navigation Design
4.2.2.2 Input Design
4.2.2.3
Output Design
4.2.3
Database Design
4.2.3.1
Conceptual Database
Design
4.2.3.2
Logical Database
Design
DBMS Selection
4.2.3.3
Detailed Design
Software Specification
4.3.1
4.3.2 Physical Database Design
Conclusion
IMPLEMENTATION
Introduction
Software Development Environment Setup
5.2.1
Software, Hardware and Network
Development Environment Setup
5.2.2 Database Development
Environment Setup
Database Implementation
Software Configuration Management
5.4.1
Configuration Environment Setup
Implementation Status
Conclusion
TESTING
Introduction
Test Plan
6.2.1
TestOrgankation
6.2.2 Test Environment
Test Schedule
6.2.3
Test Strategy
6.3.1 Classes of tests
Test Design
Test Description
6.4.1
6.4.2 Test Data
Test Results and Analysis
Conclusion
PROJECT CONCLUSION
Observation on Weaknesses and Strengths
7.1.1
Strength
7.1.2 Weaknesses
Proposition for Improvement
Contribution
Conclusion
REFERENCES
TABLE
TITLE
2.1
2.2
Software Requirement For Development Tool
Software Requirement For Operating System / Web
Server
Software Requirement For Database System
Hardware Requirement
Other Requirement
Software Requirements For Server Side
Software Requirement For Client Side
Hardware Requirement For Client And Server Side
Hardware Requirements
Netwcrrk Requirement
File Input/Output For Customer Login
File InputIOutput For Add Staff Information
File InputIOutput For Add Menu
File Input/Output For Menu Information
F i e Input/Output For Waiter Information
Development Status
Individual Involved In Testing Phases
Test Environment Specification
Test Schedule For ORMS
Test Cases, Description And Expected R d t For
Login Module
Test Data Of Admin And Staff Login
Test Result For Login Module
Comparison between current system and ORMS
PAGE
28
28
LIST OF FIGURJ3S
DIAGRAM
TITLE
Saloma Theatre Restaurant Online Reservation
Beryani King Online Ordering
DJU Catering Restaurant Online Ordering
Table-Booking.Com Reservation Table
Prototype Model
Database Life Cycle (Dblc)
Context Diagram For Current System
DFD Level 0 For Restaurant Pak Hus& Tom
Yam
Context Diagram For ORMS
DFD Level 0 For ORMS
DFD Level 1For Menu Process
DFD Level 1For Customer Process
DFD Level 1For Authentication Process
DFD Level 1For Ordering And Reservation
Process
DFD Level 1For Feedback Process
DFD Level 1For Waiter Process
DFD Level 1For Report Process
System Archittxhre
Navigation Design
Entity Relationship Wi (ERD)
AppServ Control Panel To Start The Database
Service
Configuration Of Database Connection
PAGE
LIST OF ABBREVIATIONS
ORMS
ICT
ECSB
MTC
PHP
MYSQL
DFD
ERD
DBLC
DBMS
SQL
LAN
PC
PSM
API
WYSNVYG
HTML
CSS
DDL
DCL
IDE
Online Restaurant Management System
Information And Communications Technology
Expressive Creations Sdn. Bhd.
Malaysia Tourism Centre
Pre-Hypertext Processor
Structured Query Language
Data Flow Diagram
Entity Relationship Diagram
Database Life Cycle
Database Management System
Structured Quexy Language
Local Area Network
Personal Computer
Projek Sarjana Muda
Application Programming Interface
What Yon See Is What You Get
Hypertext Markup Language
Cascading Style Sheets
Data Definition Language
Data Control Language
Integrated Development Environment
xiii
LIST OF APPENDICES
APPENDIX
A
TITLE
MILESTONE OF PSM
Table A. 1
Milestone of PSMl
Table A.2
Milestone of PSM2
B
GANTT CHART OF PSM
C
DATA REQULREMENT
Table C. 1
Data Requirement for Admin Data
Table C.2
Data Requirement for Customer Data
Table C.3
Data Requirement for Feedback Data
Table C.4
Table C.5
Table C.6
Data Requirement for Menu Data
Data Requirement for Tempahan Data
Data Requirement for Waiter Data
USER INTERFACE DESIGN
Figure D. 1 Homepage
Figure D.2
Our menu page
Figure D.3
How to order page
Figure D.4
Customer login interface
New customer registration
Figure D.5
Figure D.6
Customer ordering and reservation page
Figure D.7
Customer ordering and reservation report
Figure D.8
Figure D.9
Figure D.10
Figure D.ll
Figure D.12
Figure D.13
Figure D.14
Page
Admin login interface
Adrnin homepage
Menu information page
Add new menu page
Update menu interface
Waiter information page
Add new waiter page
PAGE
xiv
Figure D. 15 Search and update waiter inf'tion page
Figure D. 16 Waiter schedule page
INPUT DESIGN
Table E. 1
Attribute of input design
OUTPUT DESIGN
Figure F. 1
Output design for customer online ordering
information
DATA DICTIONARY
Table G. 1
Data dictionary for admin data
Table G.2
Data dictionary for customer data
Table G.3
Data dictionary for feedback data
Table G.4
Table G.5
Table G.6
Data dictionary for menu data
Data dictionary for tempahan data
Data dictionary for waiter data
NORMALIZATION
Figure H. 1
Third normal form (3 NF) for admi.table
Figure H.2
Third normal form (3 NF) for customer
table
Third
normal form (3 NF) for menu table
Figure H.3
Figure H.4
Third normal form (3 NF) for tempahan
table
Figure H.5
Third normal form (3 NF) for waiter table
Third normal form (3 NF) for feedback
Figure H.6
table
CREATE TABLE
Figure L 1
Create table admin
Figure 1.2
Create table feedback
Create table customer
Figure 1.3
Figure 1.4
Create table menu
Figure 1.5
Create table tempahan
Create table waiter
Figure 1.6
ASSIGNING ADMIN AND CUSTOMER LOGIN
Figure J.1
Figure 5.2
Assigning Admin Login
Assigning customer login
TEST DESCRIPTION
Table K. 1
Test cases, description and expected result
for customer registration module
Table K.2
Test cases, description and expected result
for online ordering module
Table K.3
Test cases, description and expected result
for menu module
Test cases, description and expected result
Table K.4
for customer waiter module
Table K.5
Test cases, description and expected result
for customer feedback module
Table K.6
Test cases, description and expected result
for customer generate report module
TEST DATA
Table L. 1
Test Data of customer registration data
Test Data of feedback data
Table L.2
Table L.3
Test Data of online ordering data
Table L.4
Test Data of menu data
Table L.5
Test Data of waiter data
TEST RESULTS AND ANALYSIS
Table M. 1
Test Result for customer registration data
Table M.2
Test Result for feedback data
Test Result for online ordering data
Table M.3
Test Result for menu data
Table M.4
Table M.5
Test Result for waiter data
BAB I
INTRODUCTION
1.1
Project Background
Ontine Restaurant management system is the system for manage the restaurant
business. The main point of developing this system is to help restaurant administrator
manage the restaurant business and help customer for online ordering and reserve table.
The project is developing ,
many restaurants have a lot difficult to
manage the business such as customer ordering and reservation table. By using manual
customer ordering is difficult to waiter keep the correct customer information and maybe
loss the customer information.
So, online restaurant management system will develop to help the restaurant
administratorto manage restaurant management and for customer make their online
ordering and reservation table. Other than that, this project is to upgrade the manual
system and make the business easily to access and systematic.
12
Problem Statement
Nowadays, many restaurants manage their business by manual especially take
customer ordering. Today, restaurant waiter takes the customer ordering by manual
system with using paper. This is problem for restaurant waiter the probability lost and
duplicates custumer information Additionally, it would affect to reputation restaurant in
operate management of ordering.
Besides, the restaurant waiter information also by manual system kept use paper
and this is difficult for restaurant administrator to find waiter information, probability
missing the paper and difficult to arrange the schedule. Sometimes, waiter information
and customer information is important to restaurant administrator for reference in the
future.
Furthermore, restaurant side needs management in the section menu. This is the
important to restaurant waikr to manage the menu. Besides this section is for customer
viewer the menu that restaurant prepmed and make their ordering.
As a result, the current system (manual system) is not effective and efficient to
use anymore because the current system cannot save, manage and monitor the restaurant
waiter infbrmatiun, menu information, customer adering infomation and generate
report well.
Based on the problems stated above, the objectives of the project are:
i.
to develop online odering and reservation system in restaurant
ii.
to develop use interface for online restaurant management system
iii.
to provide online menu information for customer
1A
Scope
This section consist of three components which is target user, target area and
project deliverables.
1.4.1
Target User
The groups of user that had been identified to use the system are customer and
administrator.
This user will register to be a member to use the online system of this online
restaurant management system (ORMS). This online ordering divided into two type of
customer, it is customer dinein ordering and take-away ordering. For din-in ordering,
customer will view menu, make online ordering and make a reservation table. But takeaway ordering, customer can view menu and online ordering without reservation table.
After customer make online ordering, customer can take ordering the date that customer
was choose during make online ordering. Event though, customer must amfirm online
ordering with restaurant three days before customer take the ordering for dine-in
customer and for take-away customer will be confirm one hour before it whether by
email or phone.
Administrator is the person who will manage the entire system. This type of user
will also do maintenance and control the application of this system. Administrator takes
a responsibility to register new customer, register new waitex, register new menu into
database, and etc.
1.4.2
Target Area
This system will be placed at restaurant.
Regarding to the module that had been identified, the flow of an activity will be
described in term of customer registration module, customer online ordering and
reservation module, waiter moduk, ftedback module, menu module and generate report
module.
Customer Registration Module
Customer ~lcgistrdionmodule contains customer's infixmation such as customer
personal information and other information related to that customer. Then, all of this
information recorded into database.
Customer O n h e Ordering A d Reservation Module
Customer online ordering and reservation module provides a form that needs to
be fulfilling in term of ordering food and reservation table via online.
Waiter Module
Waiter module contains waiter information such as waiter personal information,
task schedule and other information related to that waiter. Then, all of this information
recorded into database.
Feedback Module
Based on food or everything about the restaurant, customer can send any
suggestion or comment to the restaurant with feedback form. From this form, side of
restaurant will know their weaknesses and strengths.
Menu Module
Menu module is food that restaurant pqmredfor customer. This module,
customer can view the menu and make decision for order.
Generate Report Module
System provides an option for generate a report. The contents of the report as the
followitlg:
1.
The report of customer ordering and reservation table.
2.
Customer's information and waiter information.
3.
Suggatbn or comment that customer insertat feedback form
4.
Profit business for restaurant
1.5
Project Significance
This system will be going to help customer and administrator in restaurant
especially part of online ordering and reservation table. Most of restaurant has a problem
of the ordering and reservation table. The result of odine odering and reservation table
will give customer easy to make ordering and reservation table online and hopefully can
smoothen up the job of administrator and waiter. This system also produces a
computerized system in defining the best solution in each ordering and reservation
problem faces by customer and administrator.
1.6
Expected Output
The expected output from this project is a system-based that will be able to store
customer's information, waiter's information, menu's information, store customer
information of online ordering and reservation information and customer's suggestion
and generate profit business report. Otherwise this system will change form manual
system to axup-
system.
ORMS are developed as a system-based. Chapter I described each problem
occurred by using the manual system. Project objective and project scope identified the
solution for each of the problem. Pmject Significance also being explains to convince
benefits that can be gathered from this system. This system hopefully can overcome the
problem in the current system. Chapter I1 elaborates the Literature Review and Project
Methodology.