1

Café Reservation & Ordering System

by

SUGANTHA KUMAARAN A/L KRISHNAN

IS0106028

Project Supervisor: Madam Mohana Shanmugam

PROJECT REPORT SUBMITTED IN PARTIAL FULFILLMENT OF THE

THE REQUIREMENTS FOR THE BACHELOR OF INFORMATION TECHNOLOGY
(INFORMATION SYSTEMS) (HONS.)
UNIVERSITI TENAGA NASIONAL
2020/2021
 2

APPROVAL PAGE

TITLE: CAFÉ RESERVATION & ORDERING SYSTEM

AUTHOR: SUGANTHA KUMAARAN A/L KRISHNAN

The undersigned certify that the above candidate has fulfilled the condition of the Final Year Project in
partial fulfilment for the Bachelor of Information Technology (Information Systems) (Hons.)

SUPERVISOR:

Signature: _______________________
Name: MOHANA SHANMUGAM
Date: _______________________
 3

DECLARATION

I hereby declare that this report, submitted to Universiti Tenaga Nasional as a partial fulfilment of the
requirements for the Bachelor of Information Technology (Information Systems) (Hons.) has not been
submitted as an exercise for a bachelor at any other university. I also certify that the work described here
is entirely my own except for excerpts and summaries whose sources are appropriately cited in the
references.

This report may be made available within the university library and may be photocopied or loaned to
other libraries for the purposes of consultation.

Date: 22 / 5 / 2022
____________
SUGANTHA KUMAARAN KRISHNAN
IS0106028
 4

Executive Summary

These days the main issue that restaurants and cafes are facing is customer management. Café
Reservation and Ordering System (CROS) is a system designed for The Wheel Bar & Café which is located
in Bandar Bukit Tinggi, Klang. The main objective of this system is to give the customers ease of making
a reservation in a click of a button .Other than that it is also to produce an efficient and effective ordering
of food to save employees time. Before arriving at the café the customers could reserve a table for them
via the new website that is designed for the cafe. The customers are prompted to log in or register on the
café's website. In there they could reserve a table by providing their name, contact number, the number of
guest to reserve a table for them. Once the customers reach the café they could order their food online via
the website. Other than that customers could get basic information about the café on the websites.
Customers could access the website to check what are the Food and drinks that are offered in the café.
CROS is an eco-friendly system because it helps to reduce the usage of paper while taking orders and
saves the time of the employees and also the customers time.
 5

Table of contents
Approval Page................................................................................................................ 2

Declaration ..................................................................................................................... 3

Executive Summary ....................................................................................................... 4

Table of Contents ........................................................................................................... 5

List of Tables .................................................................................................................. 8

List of Figures ................................................................................................................. 9

Chapter 1
1.1:Background .............................................................................................................. 11

1.2: Problem Statements................................................................................................ 11

1.3: Objectives................................................................................................................ 11

1.4: Project Scope .......................................................................................................... 12

1.5: Project Timeline ....................................................................................................... 13

Chapter 2

2.1: Review on Current Systems .................................................................................. 14

2.2: Review on Existing Systems .................................................................................. 14

2.2.1: Atmosphere360 Reservation System ................................................................. 15

2.2.2: Café Café ............................................................................................................. 17

2.2.3: Comparison between similar systems and proposed system ............................. 18

2.3: Business process flow diagram .............................................................................. 19

2.4: Software development methodology....................................................................... 20

2.5: Requirements gathering technique .......................................................................... 22

2.6: Tools and technology .............................................................................................. 26

 6

Chapter 3
3.1: Use Case Diagram .................................................................................................. 27
3.2: Context Diagram & Level 0 ..................................................................................... 28
3.3: Database Design - Entity Relationship Diagram (ERD), Data Dictionary ............... 29

3.4: Navigation Diagram................................................................................................. 31

3.5: Interface Design ...................................................................................................... 32

Chapter 4
4.1: Overview .................................................................................................................. 40
4.2: Testing and Results ................................................................................................. 40

Chapter 5
5.1: Introduction ............................................................................................................... 52

5.2: Development Requirement ..................................................................................... 52

5.2.1: Hardware requirement ......................................................................................... 52
5.2.2: Software Requirement........................................................................................... 52

5.3: phpMyAdmin MySQLServer ................................................................................... 53

5.4: Interface and Function ............................................................................................ 54
5.4.1:Main Page .............................................................................................................. 54

5.4.2: Sign Up and Login Modals................................................................................... 56

5.4.3: New Reservation Page ........................................................................................ 57
5.4.4: Menuless Ordering page ....................................................................................... 58

5.4.5: View Reservation Page........................................................................................ 59

5.4.6: View Orders Page ................................................................................................ 59
5.4.7: Menu Page ............................................................................................................ 60

5.4.8: Edit Schedule page .............................................................................................. 61

5.4.9: Edit tables page ................................................................................................... 62
5.4.10: View tables page ................................................................................................. 62
 7

Chapter 6

6.1: Introduction ............................................................................................................... 63

6.2: Project Progress....................................................................................................... 63
6.3: Project Challenges ................................................................................................... 63
6.4: Recommendation ..................................................................................................... 63

Reference ........................................................................................................................ 64
 8

LIST OF TABLES

Table No Page

Table 1.0: User Scope .................................................................................................... 13

Table 1.1: Project Timeline ............................................................................................. 14

Table 2.1: Comparison Table......................................................................................... 19

Table 3.1: Data Dictionary Table .................................................................................... 31

Table 5.1: Hardware Requirement Description ............................................................... 53

Table 5.2: Software Requirement Description ................................................................53

 9

LIST OF FIGURES

Figure No Page

Figure 2.1: Atmosphere360 Reservation Page .............................................................. 14

Figure 2.2: Form fill up page ........................................................................................... 15

Figure 2.3: Café café reservation page .......................................................................... 16

Figure 2.4: Café Café Menu Page .................................................................................. 17

Figure 2.5: Process Flow diagram .................................................................................. 18

Figure 2.6: Software Development Model ...................................................................... 19

Figure 2.7 ........................................................................................................................ 21

Figure 2.8 ........................................................................................................................ 21

Figure 2.9 ........................................................................................................................ 22

Figure 2.10 ...................................................................................................................... 22

Figure 2.11 ...................................................................................................................... 23

Figure 2.12 ...................................................................................................................... 23

Figure 2.13 ...................................................................................................................... 24

Figure 2.14 ...................................................................................................................... 24

Figure 3.1: Use case diagram......................................................................................... 26

Figure 3.2: context diagram ............................................................................................ 27

Figure 3.3: Entity Relationship Diagram ......................................................................... 28

Figure 3.4: Navigation Diagram ...................................................................................... 30

Figure 3.5: Homepage .................................................................................................... 31

Figure 3.6: Menu Page ................................................................................................... 32

Figure 3.7: reservation Page .......................................................................................... 33

Figure 3.8: Login Page.................................................................................................... 34

Figure 3.9: Sign Up page ................................................................................................ 35

 10

Figure 3.10: Order Page ................................................................................................. 36

Figure 3.11: About Page ................................................................................................. 37

Figure 3.12: Reservation Details Page ........................................................................... 38

Figure 3.13: Order Details Page ..................................................................................... 38

Figure 5.0: phpMyAdmin MySqL Server ........................................................................ 52

Figure 5.1: About us........................................................................................................ 53

Figure 5.2: Gallery........................................................................................................... 53

Figure 5.3: Reservation & Menuless Ordering ............................................................... 54

Figure 5.4: Find us & Opening Hours ............................................................................. 54

Figure 5.5: Sign Up Modal .............................................................................................. 55

Figure 5.6: Login Modal .................................................................................................. 55

Figure 5.7: New Reservation Page................................................................................. 56

Figure 5.8: Menuless Ordering Page.............................................................................. 67

Figure 5.9: View Reservations page............................................................................... 58

Figure 5.10: View Orders Page ...................................................................................... 58

Figure 5.11: Food ............................................................................................................ 59

Figure 5.12: Beverages................................................................................................... 59

Figure 5.13: Sides ........................................................................................................... 60

Figure 5.14: Edit schedule page ..................................................................................... 60

Figure 5.15: Edit tables Page ......................................................................................... 61

Figure 5.16: View Tables Page....................................................................................... 61

 11

CHAPTER 1 :INTRODUCTION

1.1 Background
Wheels Bar & café is a café that is located in Bukit Tinggi ,Klang. It was opened in the early
2020 by Mr Selvakumar. The café is well known for its pirate themed soothing environment
which has great food and drinks. The café still uses the traditional way of taking orders by
getting the orders written down by the waiters. The café is open for reservations for private
events such as wedding party, birthday party and many more. But the customers still have to
make a phone call to the café’s landline to reserve some tables.

1.2 Problem Statement

The Wheel Care & Bar still uses the traditional way of taking orders from customers and
accepting reservations from customers through phone calls. The café is sometimes full of new
customers trying out the foods and there are also loyal customers who are waiting for the waiter
to get their orders. The café does not have a website but they have a Facebook page but
people are not using FB much as they used to. It is always ineffective when ordering food since
it might be misplaced or wrongly taken by the employee. These could cost the customers their
time. Sometimes customers aren’t able to do any events in the café since they are not able to
get the tables they need. The reservation are done via phone calls where the data is usually
misplaced or error in the reservation information.

1.3 Objective
The purpose of CROS is to produce an efficient and effective reservation and ordering at The
Wheel Bar & Café.
The objectives of the system are:
1. To enable customers to make table reservations based on availability
2. To enable the employees to manage the reservations efficiently.
3. To reduce the workload of employees taking the orders.
4. To make the ordering easier for the customers
 12

1.4 Project Scope

Table 1.0: User Scope

User Scope Description

Admin 1. Admins can log in at the main page
where they can view all the data.
2. Admin can view the reservation
details
3. View the order details of the
customer.
4. Edit opening schedule of the café
5. Edit number of tables that are set in
the café for a specific day
6. View reserved tables and view total
tables

Customer 1. Registration: Users can register

themselves on the website with their
information such as name, contact
number.
2. Check reservation availability and
reserve according to the number of
pax
3. Order food and drinks
4. View Reservation details
5. View Order details
6. View Menu
 13

1.5 Project Timeline

Table 1.1 : Project Timeline

Week

Activities Project 1

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16

Introduction

Proposal

Executive
summary

Chapter 1

Chapter 2
Submission
executive
summary,
chapter 1,
chapter2
Design

Chapter 3

Poster design

Presentation
and demo
Final report
and logbook

Project 2

Chapter 4

Chapter 5

Chapter 6

Full Report
Submission

Presentation
 14

CHAPTER 2
ANALYSIS & SYSTEMS REQUIREMENTS

2.1 Review On Current System

According to the café owner, Wheel Bar & Café does not have any web-based system yet to
run an effective and efficient business. They are still using the old method to take the order
and make reservations by writing them out. This process takes time and energy. Other than
that this process consumes paper, pen, and resources. This will increase the employee
workloads. The staffs are frustrated when they misplace an order.

2.2 Review On Existing Systems

There are similar systems that are out there which are almost similar to the system that is
going to be developed. There are few features that the existing system does not have.
 15

2.2.1 Atmosphere360 Reservation System

Figure 2.1 Atmosphere360 Reservation Page

This system allows any user to make a reservation at their desired time and how many
people are coming. This shows if there are tables available or not on the desired date and
time.
 16

Figure 2.2 Form fill up page

This web-based application allows user to fill up their credentials to reserve a table. Users have
to input Their first name, last name, email, country, phone number, and purpose.
 17

2.2.2 Café Café

Figure 2.3 : Café café reservation page

This is the reservation page of Café Café Malaysia. Customers are required to fill up their
name, dining outlet, data, time, and number of pax to reserve a table at the café.
 18

Figure 2.4 : Café Café Menu Page

On this page, the customers could get information of what are the dishes served in the café.

2.2.3 Comparison between similar system and proposed system

Table 2.1 Comparison Table

Features Atmosphere360 Café Café Malaysia Café
Reservation &
Ordering
System
Login x x /
Reservation / / /
Ordering x x /
Registration x x /
Picture Gallery / / /
Calendar / / /
Customer Page x x /

The table shows the comparison between proposed system and another 2 similar systems
that are available online. We can observe that the proposed system has all the features that
a similar system has. The difference here is that the proposed system offers customer
reservation and login and ordering.
 19

2.3 Business Process flow diagram

Figure 2.5 Process flow diagram

 20

2.4 Software Development Methodology

The Methodology I have chosen is Software Development Life Cycle (SDLC). I chose this
methodology because it helps to transform the idea of a project into a functional and
completely operational structure. It is a process used to design, develop and test high-quality
software. The SDLC aims to produce high-quality software that meets or exceeds customer
expectations.

Figure 2.6 : Software Development Model

Source : https://www.javatpoint.com/jira-waterfall-model
Phase 1 : Requirement Analysis
This is the most important phase in SDLC. For this project in the requirement phase inputs
has been taken from the client which is The wheel Bar& Café. Survey also has been done to
know the needs of the customers.

Phase 2 : Design
Based on the requirements, More than one design will be focused and the most relevant and
efficient design will be used for developing reference. Then the design will be reviewed by
the stakeholders before development. The stakeholders here would be the business owner.

Phase 3 : Development
In this stage, the actual development of the system will begin. The development must be
according to the design that is proposed and it must be followed accurately to avoid errors.
High-level programming languages are used in this phase.
 21

Phase 4 : Testing
The testing activities are usually done in all phases of the SDLC but at this testing phase, all
the system defects are tracked and reported. The testing of the finished system will be tested
with the owner, employees and also the customers.

Phase 5 : Deployment
Once the system is tested and ready to be deployed, it is given to the client to make their
business process more efficient.

Phase 6 : Maintenance
Once the system is deployed to the client if there is any kind of faults or updates that need to
be added it will be fixed for the client at this phase.
 22

2.5 Requirement Gathering Technique

For this project, Survey has been done to gather all the requirements from the customer's
perspective.

Figure 2.7

As per the survey, 52.4% of the customers of the café are students and 47.6% of the
customers are employed, individuals. Thus, The system can be easily used since students
tend to use websites.

Figure 2.8
52.4% of respondents have been to café before so they understand the business flow there
and the complications.
 23

Figure 2.9

33.3% of the respondents had issues with not getting a table while 42.9% of the respondents
did not have such issues.

Figure 2.10

Figure 2.10 shows that 61.69% of the respondents do not know the foods and drinks served
in the café.
 24

Figure 2.11

According to the survey, 28.6 % of customers have spent a tremendous amount of time
waiting for the food due to some complications. 42.9% of customers spend around 10 to 15
minutes on their food.

Figure 2.12

This survey shows that 57.1 % of respondents were introduced to the café by Friend or
family referral. Other 28.6% and 14.3% of respondents were introduced by Social media
platforms and banners.
 25

Figure 2.13

The survey shows that 71.4% of respondents are not regular customers. Only 28.6% of the
customers are regular customers to the café.

Figure 2.14

The survey shows that 66.7% of customers prefer to make reservations online rather than
making a phone call to the café.
From This survey, we could find out that customers need an online system for the café. This
is because it meets the customer needs as well as the owner’s needs.
 26

2.6 Tools and Technology

The tools and software are identified before starting to developing the system.
2.6.1 Hardware Requirement
• Internet Connection
• I3 or above processor
• Minimum memory : 4GB
• Minimum Hard Drive Capacity : 1 TB
• Monitor
• Laptop/CPU

2.6.2 Software Requirement

• Windows 8 or higher
• Xampp Server
• SQL server
2.6.3 Programming Language and database
• PHP
• MySQL
• HTML
 27

CHAPTER 3
DESIGN
3.1 Use Case Diagram

Figure 3.1 : Use Case Diagram

Figure 3.1 shows Use case diagram for Café Reservation & Ordering System. The diagram
used to gather the requirement of the system and shows interaction among requirement and
actors
 28

3.2 Context Diagram

Figure 3.2 : context Diagram

Figure 3.2 shows the context diagram of the Café Reservation & Ordering System. The
diagram shows the relationship between entities and the system. The system contains two
entities which are customer and owner/employees.
 29

3.3 Database Design

Entity Relationship Diagram (ERD

Figure 3.3 : Entity Relationship Diagram

Figure 3.3 shows Entity-Relationship diagram for Café Reservation & Ordering System. It
shows the relationship between entities and the database of the system with their attributes
and the type of attributes
 30

3.3 Data Dictionary

Table 3.1 : Data Dictionary for Café Reservation & Ordering System

No Entity Attribute Data type Constraint

1 Users user_id Int (11) Primary key (PK)
role_id Int (11) Foreign Key (FK)
uidUsers Varchar (255)
emailUsers Varchar (255)
pedUsers Varchar (255)
reg_date timestamp
2 Reservation reserv_id Int (11) Primary key (PK)
user_fk Int (11) Foreign Key (FK)
f_name Text
l_name Text
num_guests Int(11)
num_tables Int(11)
rdate Date
time_zone Text
telephone Text
comment Text
reg_date Timestamp
3 menuorder menuorder_id Int (11) Primary key (PK)
user_fk Int (11) Foreign Key (FK)
f_name Text
l_name Text
food_order Varchar (255)
food_order2 Varchar (255)
drink_order Varchar (255)
drink_order2 Varchar (255)
sides Varchar (255)
time Varchar (255)
table_num Int(100)
comment Text
4 Schedule Schedule_id Int (11) Primary Key (PK)
date date
open_time time
close_time time
5 tables tables_id Int (11) Primary Key (PK)
t_date date
t_tables Int (11)
6 role Role_id Int(5) Primary Key (PK)
Foreign Key (FK)
 31

3.4 Navigation Diagram

Figure 3.4 : Navigation Diagram

Figure 3.4 shows the navigation diagram for Café Reservation & Ordering System. It shows
the navigational flow of the system website.
 32

3.5 Interface Design

Figure 3.5 : Homepage

Figure 3.5. show the mock-up homepage of the proposed system website. The website
header has navigation of Menu, Reservation, Account, Order, and About.
 33

Figure 3.6 : Menu Page

Figure 3.6 shows the mock-up of the menu page in the proposed system. This is to show the
customers the foods and drinks that are served in the café. It also shows the current
promotions.
 34

Figure 3.7 : Reservation Page

Figure 3.7 shows the mock-up reservation page of the system. It contains a calendar where
customers can choose the reservation date and time. Customers can choose the date and
time of their reservation. Customers need to fill in the number of pax.
 35

Figure 3.8 : Login Page

Figure 3.8 shows the login page of the mock-up website. Customers can log in to save their
information and manage their reservations.
 36

Figure 3.9 : Sign Up page

Figure 3.9 shows the signup page of the mock-up website. Customer who is new to the site
can create their account here with their email.
 37

Figure 3.10: Order Page

Figure 3.10 shows the order page of the mock-up website. Customers can order their food
here once they arrive at the café to avoid. Admin and employees can check the order details
of the customers.
 38

Figure 3.11 : About Page

Figure 3.11 shows the about page of the mock-up site. Customers could check the café's
details such as contact number, email, location.
 39

Figure 3.12 : Reservation Details Page

Figure 3.12 shows the reservation details page that can be viewed by the admin and the
staff.

Figure 3.13 : Order Details Page

Figure 3.13 shows the order details of the customers. This page can only be viewed by the
admins and staff.
 40

CHAPTER 4
Testing

4.1 Overview
all functions in the developed system are tested to ensure it does not have any error and it
also includes test cases documents and the result of the testing.

4.2 Testing and Results

Tests are done separately to the users, admin, and also on the basic website for all
functions available
 41

System Café Reservation & Ordering System (Main Page)

Purpose To test the validation features for all the fields
Test Case Details
Step Description Expected Result Actual Result Commen
t/ Remark
1 Test on the top navigation All five icons Navigates Pass
bar navigate to five to each
different parts of the part of
main page thepage
• About us
• Gallery
• Reservation
• Menuless
Ordering
• Find us

2 Test on reservation navigates to the The button Pass

button in main page reservation page navigates to
the
reservation
page

3 Test on order button navigates to the The button Pass

in main page order page navigates
to the order
page

4 Test on the opening Shows the opening Shows a Pass

hours and closing hours of table with the
1. Enter date the café on the opening hour
2. Click on specific day and closing
check open hour
time

Test by HARIHARAN A/L SELVAM

Date 22/05/2022
Pass/Fail Pass
 42

Commen All functions work according to the requirement. Main page functions are user
t/ Remark friendly and has smooth navigation.

Acceptance of Testing (Signatories)

Verify by Accepted by
 43

System Café Reservation & Ordering System (Sign up & Login)

Purpose To test the validation features for all the fields
Test Case Details
Step Description Expected Result Actual Result Commen
t/ Remark
1 Test sign up button at the Opens a pop up Pop up Pass
top navigation bar modal of the sign up model
page opened
with sign
up form

2 Test if all fields can be Completes the The register Pass

filled and click on registration of the new now button
register now button user completes
the
registration
and shows a
dialog “sign
up
successful
please
login”.

3 Test log in button at the top Opens a pop up Pop up Pass

navigation bar modal of the log in model
page opened
with log in
form

4 Test if all fields can be Log in the user and The log in Pass
filled and click on brings the user button
register now button successfully
logs in and
goes to main
page
 44

Test by HARIHARAN A/L SELVAM

Date 22/05/2022
Pass/Fail Pass
Commen All functions work according to the requirement. Login and sign up works
t/ Remark effectively.

Acceptance of Testing (Signatories)

Verify by Accepted by
 45

System Café Reservation & Ordering System (New Reservation)

Purpose To test the validation features for all the fields
Test Case Details
Step Description Expected Result Actual Result Comme
nt/
Remark
1 Test new registration Navigates user to new Opens Pass
button at the top navigation registration page new
bar registratio
n page

2 Test if all fields can be Show error dialogs if Shows error Pass
filled and click on important fields are not messages if
submit reservation filled fields are not
button filled

3 Test submit reservation Completes the Reservation Pass

button reservation completed
and it
shows your
reservation
was
successful
Test by HARIHARAN A/L SELVAM
Date 22/05/2022
Pass/Fail Pass
Commen All functions work according to the requirement. Reservation has been made.
t/ Remark

Acceptance of Testing (Signatories)

Verify by Accepted by
 46

System Café Reservation & Ordering System (Menuless Ordering)

Purpose To test the validation features for all the fields
Test Case Details
Step Description Expected Result Actual Result Comme
nt/
Remark
1 Test menuless ordering Navigates user to Opens Pass
button at the top navigation menuless ordering menuless
bar page ordering
page

2 Test if all fields can be Show error dialogs if Shows error Pass
filled and click on important fields are not messages if
submit orders button filled required
fields are not
filled

3 Test submit order button Completes the Ordering Pass

ordering completed
and it
shows your
order was
successful

Test by HARIHARAN A/L SELVAM

Date 22/05/2022
Pass/Fail Pass
Commen All functions work according to the requirement. Ordering is well made.
t/ Remark

Acceptance of Testing (Signatories)

Verify by Accepted by
 47

System Café Reservation & Ordering System (View Reservation)

Purpose To test the validation features for all the fields
Test Case Details
Step Description Expected Result Actual Result Comme
nt/
Remark
1 Test view reservation Navigates user to Opens Pass
button at the top navigation view reservation page view
bar reservatio
n page

2 Test if the current The certain reservation Reservation Pass

reservation gets will be deleted if the got deleted
deleted cancel button is clicked and shows
delete was
successful

Test by HARIHARAN A/L SELVAM

Date 22/05/2022
Pass/Fail Pass
Commen All functions work according to the requirement. The reservation made can be
t/ Remark viewed and deleted.

Acceptance of Testing (Signatories)

Verify by Accepted by
 48

System Café Reservation & Ordering System (View orders)

Purpose To test the validation features for all the fields
Test Case Details
Step Description Expected Result Actual Result Comme
nt/
Remark
1 Test view orders button at Navigates user to Opens Pass
the top navigation bar view orders page view
orders
page

2 Test if the current The selected order will Order got Pass
order gets deleted be deleted if the cancel deleted and
button is clicked shows delete
was
successful

Test by HARIHARAN A/L SELVAM

Date 22/05/2022
Pass/Fail Pass
Commen All functions work according to the requirement. The order can be viewed and
t/ Remark deleted correctly.

Acceptance of Testing (Signatories)

Verify by Accepted by
 49

System Café Reservation & Ordering System (Admin – edit schedule)

Purpose To test the validation features for all the fields
Test Case Details
Step Description Expected Result Actual Result Comme
nt/
Remark
1 Test edit schedule button at Navigates user to edit Opens Pass
the top navigation bar schedule page edit
schedule
page

2 Test if all fields can be Submit the schedule The schedule Pass
filled and click on for the chosen date for the
submit schedule selected date
button is submitted
and shows
schedule was
successfully
submitted

Test by HARIHARAN A/L SELVAM

Date 22/05/2022
Pass/Fail Pass
Commen All functions work according to the requirement. Schedule can be edited and
t/ Remark viewed in the mainpage

Acceptance of Testing (Signatories)

Verify by Accepted by
 50

System Café Reservation & Ordering System (Admin – edit tables)

Purpose To test the validation features for all the fields
Test Case Details
Step Description Expected Result Actual Result Comme
nt/
Remark
1 Test edit tables button at Navigates user to edit Opens Pass
the top navigation bar tables page edit tables
page

2 Test if date and Submit the table for the The number Pass
number of tables can chosen date of tables for
be filled and click on the selected
submit tables button date is
submitted
and shows
tables was
successfully
submitted

Test by HARIHARAN A/L SELVAM

Date 22/05/2022
Pass/Fail Pass
Commen All functions work according to the requirement. Tables can be edited
t/ Remark efficiently.

Acceptance of Testing (Signatories)

Verify by Accepted by
 51

System Café Reservation & Ordering System (Admin- view tables)

Purpose To test the validation features for all the fields
Test Case Details
Step Description Expected Result Actual Result Comme
nt/
Remark
1 Test view tables button at Navigates user to Opens Pass
the top navigation bar view tables page view
tables
page

2 Test if the current The selected tables will tables got Pass
tables gets deleted be deleted if the delete deleted and
button is clicked shows delete
was
successful
Test by HARIHARAN A/L SELVAM
Date 22/05/2022
Pass/Fail Pass
Commen All functions work according to the requirement. All the reserved tables and
t/ Remark total tables per date can be viewed.

Acceptance of Testing (Signatories)

Verify by Accepted by
 52

Chapter 5

Implementation

5.1 Introduction

Detailed explanations of the implementation process of café reservation and

ordering system are stated in this chapter. The tasks involved in this process are
code writing programs and creating a database. All the interfaces for the deployed
system along with the description will be included in this chapter.

5.2 Development Requirement

Development requirement is the hardware and software required in developing the
system. In order to ensure the success of system development, suitable hardware
and software need to be used.

5.2.1 Hardware Requirement

Hardware Descriptio
n
Intel(R) Core(TM) i7-7700HQ CPU @ 2.80GHz
Processor

RAM 12.0 GB

Available hard disk space 250 GB

Table 5.1: Hardware Requirement Description

5.2.2 Software Requirement

Softwar Descriptio
e n
Windows 8 and above Operation System platform

Visual Studio Code To write code for website

phpMyAdmin To create database

XampServer To serve live website

Table 5.2: Software Requirement Description
 53

5.3 phpMyAdmin MySQLServer

This software is used to create the database and manage all the data that is acquired from
café reservation and ordering system.

Figure 5.0 phpMyAdmin MySQL server

 54

5.4 Interfaces and functions

All interfaces and functions of café reservation and ordering system will be shown in detail
and with explanation. This is done to provide a better understanding of the system.
5.4.1 Main Page

This page shows basic information about the café. This page also contains attractive images
to attract the customers attention.

Figure 5.1 About us

Figure 5.2 Gallery

 55

Figure 5.3 Reservation & Menuless Ordering

Figure 5.4 Find us & Opening Hours

 56

5.4.2 Sign Up and Login Modals

This shows the sign up modal and login modals that pops up when sign up or login button is
clicked on the navigation bar

Figure 5.5 Sign Up Modal

Figure 5.6 Login Modal

 57

5.4.3 New Reservation Page

This page shows the reservation form that the customers have to fill up and submit in order
to make a new reservation on a specific date.

Figure 5.7 New Reservation Page

 58

5.4.4 Menuless Ordering page

This page shows the menuless ordering form that the customers need to fill up and put the
relevant details to order food, drinks or sides.

Figure 5.8 Menuless Ordering Page

 59

5.4.5 View Reservation Page

This page shows all the reservations that the customer made using this website. It also has a
cancel function that deletes certain reservations.

Figure 5.9 View Reservations page

5.4.6 View Orders Page

This page shows all the reservations that the customers made using this website. It also has
a cancel function that deletes certain orders from the customers.

Figure 5.10 View Orders Page

 60

5.4.7 Menu Page

This page shows the menu for the customers to see and to know what kind of foods,
beverages and sides that the café offers.

Figure 5.11 Food

Figure 5.12 Beverages

 61

Figure 5.13 Sides

5.4.8 Edit Schedule page

In this page the admins can edit the opening and closing hours of the café for specific dates.
The default opening time is also set as the café opens at 12 pm and closes at 12 am.

Figure 5.14 Edit schedule page

 62

5.4.9 Edit tables page

In this page admins can edit how many tables needed to be arranged in the café on a
specific date. The default number of tables that been placed is 20 tables.

Figure 5.15 Edit tables Page

5.4.10 View Tables page

In this page the number of reserved tables is displayed according to the reservation date and
reservation time. This page also displays the total tables per date and the total tables per
date can be deleted by admins.

Figure 5.16 View Tables Page

 63

Chapter 6: Conclusion

6.1 Introduction
The proposed and implemented system is a café reservation and ordering system. The
whole project is to make Reservation handling order taking become effective at the café. The
objective of the system is to enable customers to make table reservations based on
availability. So users can reserve tables efficiently and reduce the workload of the staff.
Customers can also order food on the website after reaching the café according to the table
number. Currently, the café is using the manual system where the employees take
reservations from customers to face to face or by phone calls. The ordering also uses the
classic way with the staff taking orders from the customer.

6.2 Project Progress

This project has been created successfully according to proposed credentials in FYP 1. All
the proposed objective and features has been reached throughout the development phase of
this system. All of the features are well examined to meet the proposed objective of the
project and also to make it better than the proposed idea.

4.3 Project Challenges

The problem faced with this project is completing the project within the given time frame.
There were many obstacles but the main obstacle was the time frame. As a final year
student I have taken multiple elective subjects that require system creation also. Focusing on
developing 2 systems at once was a challenge and it was overcame efficiently. Another
challenge that was faced is dealing with multiple errors and applying simple web
development knowledge to create a well designed system.

6.4 Project Challenges

The project can be improved in the near future for better and efficient usage. For example
customers and admins can be notified if a reservation orders has been cancelled. A mobile
app can be created based on the project for better user friendly environment.
 64

References
http://lms.uniten.edu.my/moodle/pluginfile.php/224254/mod_resource/content/2/Sample1.pdf

https://atmosphere360.com.my

https://cafecafe.com.my/home/

https://www.geeksforgeeks.org/how-to-create-admin-login-page-using-php/

https://www.w3schools.com/html/

http://lms.uniten.edu.my/moodle/pluginfile.php/224255/mod_resource/content/2/Sample2.pdf