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
 Executive Summary
Café Reservation and Ordering System (CROS) is a system designed for The Wheel Bar &
Café . The main objective of this system is to produce an efficient and effective ordering of
food to save customer time and reserve tables. Before arriving to the café the customers
could reserve a table for them and order their food via the new website that is designed for
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.

CHAPTER 1

INTRODUCTION

1.0 Background
Café Reservation & Ordering System (CROS) is an important system to Wheel Café & Bar to
have effective ordering and taking customer reservation. CROS cater the needs of the Café
to have an effective flow of day to day business. By using this system, The owner could track
how many reservations they are getting everyday and what foods are on demand. At the
other hand the customers can order food without interacting with the employee and they
could reserve tables for events where they need tables when the café is full.

1.1 Problem Statement

The Wheel Care & Bar is sometimes full of new customers trying out the foods and loyal
customers. 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 don’t get the tables
they need.

1.2 Objective
The purpose of CROS is to produce 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.
1.3 Project Scope
User Scope Description
Owner Reservation Details
- View Reservation details
Order Details
- View Order Details
Update Feedbacks
- Update and View Customer
feedback
Customer Details
- View Customer Details
- Customer Name and Reservation
number
Employee Order Details
- View order details
- Update order details When there is
a change
Reservation Details
- View Reservation Details
- Update reservation details
Customer Details
- View Customer Details
- Customer Name and Reservation
number
Customer Menu
- View Food & Beverages Menu
Availability
- Check availability of Table and food

Table 1.3 : User Scope

1.4 Project Timeline

Week
Activities
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

Figure 1.4 : Project Timeline

CHAPTER 2
ANALYSIS & SYSTEMS REQUIREMENTS
2.0 Review of the systems
The review of the system consist of a comparison of similar systems and the software
development methodology and requirements gathering technique.

2.1 Review On Current System

For now, Wheel Bar & Café does not have any web-based system yet to run an effective and
efficient business. They are still using old method to take order and take reservations by
writing them out. This process takes time and energy. This will increase the employee
workloads.

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 some changes as the developed system has few features
that the existing system does not have.
2.2.1 Atmosphere360 Reservation System
(https://www.tableapp.com/partner/atmosphere360-kltower#/)

Figure 2.2 Atmosphere360 Reservation Page

This system allows any user to make reservation at their desired time and how many people
are coming.
 Figure 2.2.1 Form fill up page

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

2.2.2 Comparison between similar system and proposed system

Table 2.1 Comparison Table

Features Atmosphere360 Café Reservation & Ordering

System
Login x /
Reservation / /
Menu x /
Ordering x /
Feedback / /
2.3 Business Process flow diagram

Figure 2.3 Proposed System Flowchart

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 a high-quality software that meets or exceeds
customer expectations.

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 used for developing reference. Then the design will be reviewed by the
stakeholders before development.
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.
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.
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.

2.5 Requirement Gathering Technique

For this project Survey has been done to gather all the requirement from the customers
perspective.

Chart 2.5.1

Chart 2.5.1 shows the Professional status of the respondent.

Chart 2.5.2

Chart 2.5.2 shows the percentage of people who have visited the café and percentage of
people who havent
 Chart 2.5.3

Chart 2.5.3 shows the percentage of respondent who had an issue of not getting a table

Chart 2.5.4

Chart 2.5.4 shows the percentage of respondents who are aware of the café’s best sellers.
 Chart 2.5.5

Chart 2.5.5 shows the time the respondents waited get their food based on their experience.

Chart 2.5.6

Chart 2.5.6 shows how the respondents were introduced to the café at the first place.
 Chart 2.5.7

Chart 2.5.7 shows how often the respondents visit the café.

Chart 2.5.8

Chart 2.5.8 shows the preferred method of the respondent to order the food.
 Chart 2.5.9

Chart 2.5.9 shows the preferred method to make a reservation for the respondents.

Chart 2.5.10

Chart 2.5.10 shows how likely for the respondents to recommend the café to other from 1 to
5 where 5 is most likely.

From This survey we could find out that customers need an online system for the café.
2.6 Tools and Technology
The tools and software that are used in this project is Notepad++, HTML, PHP, CSS, PHP
myAdmin and WAMP server. Notepad++ is used because it is more user friendly and it has
many features to make website development easier. CSS is used to make the website more
attractive for the customers. It is easier to develop source code using notepad++ since it is
easier to add PHP and MySQL.
CHAPTER 3
DESIGN
3.0 Overview
In this chapter, there are few diagrams such as Use case diagram, Data Flow Diagram(DFD)
, Entity Relationship Diagram(ERD) which is used in the development of the proposed
system. Every diagram shows in details about how the system work. Other than that mock-
up of the proposed system will be included in this chapter.
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
3.2 Context Diagram

Figure 3.2 : context Diagram

Figure 3.2 shows the context diagram of Café Reservation & Ordering System. The diagram
shows the relationship between entities and the system. The system contain two entities
which is customer and owner/employees.
3.3 Database Design
3.3.1 Entity Relationship Diagram (ERD

Figure 3.3.1 : Entity Relationship Diagram

Figure 3.3.1 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
3.3.2 Data Dictionary

No Entity Attribute Data type Constraint

1 Customer User_ID Int (11) Primary key (PK)
Full_Name Varchar (255)
Email Varchar (255)
Phone number Int(11)V
2 Reservation Reservation_ID Int (11) Primary key (PK)
Date Date
Time Time

3 Order Order_ID Int (11) Primary key (PK)

Food_Items Varchar (255)
Drink_Items Varchar (255)
Other_Notes Varchar (255)
4 Owner/Employee Admin_ID Int (11) Primary Key (PK)
User_ID Int (11) Foreign key (FK)
Reservation_ID Int (11) Foreign key (FK)
Order_ID Int (11) Foreign key (FK)
Order_Status Varchar (255)

Table 3.3.2 : Data Dictionary for Café Reservation & Ordering System
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.
3.5 Interface Design

Figure 3.5.1 : Homepage

Figure 3.5.1 show the mock up homepage of the proposed system website. The website
header has navigation of Menu, Reservation, Account, Order and About.
 Figure 3.5.2 : Menu Page

Figure 3.5.2 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é.
 Figure 3.5.3 : Reservation Page

Figure 3.5.3 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
 Figure 3.5.4 : Login Page

Figure 3.5.4 shows the login page of the mock up website. Customers can login to save their
information and manage their booking.
 Figure 3.5.5 : Sign Up page

Figure 3.5.5 show the sign up page of the mock up website. Customer who are new to the
site can create their account here with their email.
 Figure 3.5.6 : Order Page

Figure 3.5.6 shows the order page of the mock up website. Customers can order their food
here before they arrive to the café to avoid the waiting time. Owners and employees can
check the order details of the customers.
 Figure 3.5.7 : About Page

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