Restaurant Management System

Submitted in partial fulfillment of the requirements for the award of

Bachelor of Science degree in Computer Science

by

Preetha. C (Reg. No. 39290080)

Sowmiya. A (Reg. No.39290101)

DEPARTMENT OF COMPUTER SCIENCE

SCHOOL OF COMPUTING

SATHYABAMA
INSTITUTE OF SCIENCE AND TECHNOLOGY
(DEEMED TO BE UNIVERSITY)
Accredited with Grade “A” by NAAC

JEPPIAAR NAGAR, RAJIV GANDHI SALAI, CHENNAI -

600 119
MARCH - 2022
1
 DEPARTMENT OF COMPUTER science
BONAFIDE CERTIFICATE

This is to certify that this Project Report is the bonafide work of C.Preetha (39290080), A.Sowmiya
(39290101) who carried out the project entitled “RESTAURANT MANAGEMENT SYSTEM ” under
my supervision from to
Internal Guide

Dr. M. Maheshwari, M.E., Ph.D.,

Head of the Department

Dr. L. LAKSHMANAN, M.E., Ph.D.,

Submitted for Viva voce Examination held on

2
. Internal Examiner External Examiner

3
 DECLARATION

I, C. Preetha (39290080), A .Sowmiya (39290101) hereby declare that the Project Report

entitled ”RESTAURANT MANAGEMENT SYSTEM” done by me under the guidance of

Dr.M.Maheshwari ,M.E ,Ph. d., is submitted in partial fulfilment of the requirements for the award

of Bachelor of Science degree in Computer Science.

Date:
PLACE: CHENNAI SIGNATURE OF THE CANDIDATE

4
 ACKNOWLEDGEMENT

I am pleased to acknowledge my sincere thanks to Board of Management of SATHYABAMA

for their kind encouragement in doing this project and for completing it successfully. I am
grateful to them.

I convey my thanks to Dr.T.Sasikala ,M.E., Ph.D, Dean, School of Computing Dr,L.

Lakshmanan M.E., Ph.D. , and Dr.S. Vigneshwari M.E., Ph.D. Heads of the Department of
Computer Science and Engineering for providing menecessary support and details at the right
time during the progressive reviews.

I would like to express my sincere and deep sense of gratitude to my Project Guide Dr./Mr./Ms
for his valuable guidance, suggestions and constanten couragement paved way for the
successful completion of my project work.

I wish to express my thanks to all Teaching and Non-teaching staff members of the
Department of Computer Science and Engineering who were helpful in many ways for the
completion of the project.

5
 ABSTRACT

Restaurant management system To begin with, restaurant

management software is specifically designed with features to help
operate and manage the restaurant, consists of various features that help
to make a business more effectively and also more profitable. making each
and every process simple and also faster.
All these problems are solved using this project. The objective of
this project is to build an electronic restaurant management system using all of
the skills and techniques from the field ensuring that no common development
mistakes are reproduced.
Currently, many restaurants use app-based system to
communicate between the restaurant and kitchen which can be shown to
be one Ongoing expense of operating a business also known as operating
costs of the least efficient approaches. Even though this approach is
implemented in successful profitable restaurants, there are several
problems which could be seen as reducing the restaurant’s efficiency. his
report documents the process of designing, developing and testing a
software system to be used in arestaurant usually given the name
restaurant management system. The restaurant management systemis
there to help communication between all teams within a
restaurant by minimising the probabilityof human errors.

6
 TABLE OF CONTENTS
CHAPTER TITLE PAGE
No
ABSTRACT 6

LIST OF FIGURES 7

1 INTRODUCTION 9
1.1 About the Project 9
2 LITERATURE SURVEY 10

3 METHODOLOGY 11

3.1 Login module 12

3.2 Masterclass and delivery module 12

3.3 Employee module 12

3.4 Printable module 13

3.5 Schedule and Reservation module 13

3.6 Technologies used 13

4 RESULTS AND DISCUSSION 14
4.1 Performance Requirements 14
4.2 Safety Requirements 14

4.3 Security Requirements 14

4 DISCUSSIONS 14

7
 4.1,1) Scope and purpose 14
4.1,2) PLATFORM 15

4.2,1) Overall System Design Objectives 16

4.3,3) Structure of Design Document 16

5 CONCLUSION AND FUTURE WORK 17

5.1 System architecture design 17

5.2 Data flow desigh 18

5.3 6 final conclusion 19

6 7 REFERENCES 19

7 7.APPENIDICE 20

7.1 Sorce code 20

7.2 Screenshots 37
LIST OF FIGURES:

FIGURE NO: FIGURE NAME PAGE NO

5.1 System architecture design 17

5.2 Data flow design 18
7.2 screenshots 37

CHAPTER 1

8
 1.INTRODUCTION:

RMS provides features to effectively carry out the activities associated with inventory

management. The features allow the business owner to manage the inventory across

different locations and most importantly, reports or data collected through RMS helps to

identify the current inventory levels to place the next order.

The RMS provides support to develop customer-facing displays The RMS interface is user

friendly and is developed to be integrated seamlessly with pre-existing operations of

restaurants. The customization feature provides even more compatibility and overall

efficiencyelectronic The traditional system is a restaurant paper menu and ordering

system is replaced with an electronic medium i.e. a digital tablet. Due to a digitalized

system, the risk of manual errors is eliminated, thus eliminating the communication The

tablet displays all the information the customer needs to know about the order he has

placed .Now when the customer enters the restaurant, he will place his order with the

help of the touch screen using the intuitive graphical user interface, right from the

selection of language till the payment confirmation. He will select from the food options

according to his choice and the system will display the payment amount he has to make

once he has finished with his order.

1.1 project overview:

This chapter gives an introduction to the project by defining the problems

encountered by restaurants, the main objectives that the system

9
expects to achieve and a brief introduction to existing solutions.
This will minimize the number of employees at the back of the counter.
Miscommunication caused by handwriting. Difficult order tracking and
time management Difficult employee management. Unmanageable order
logging. Inefficient restaurant-kitchen communication.

CHAPTER 2

2. LITERATURE SURVEY:

2.1 Article Main focus Corresponding menu issue Pavesic (1983) Menu

engineering model including weighted contribution margin and

food cost percentage Menu analyzing and Hayes and Huffman

(1985)Menu item profitability analysis and goal value analysis Menu

analyzing

2.2 Bayou and Bennett (1992)Menu item profitability analysis based on analysis of

market segments (four levels of profitability analysis)and Menu analyzing Kelly et al.

(1994)The relationship between price elasticity and pricing Menu pricing

2.3 Shoemaker (1994)The effect of a decoy item on the price value perception of a

menu Menu pricing Bowen and Morris (1995) The relationship between menu item

10
placement on the menu card and sales of menu items and Menu designing LeBruto et al.

(1995) Menu engineering model including labor costs as a menu analysis method

Menu analyzing

2.4 Morrison (1997) Development of menu engineering models and a study on

upscale restaurants menu planning practices Menu analyzing Jones and Mifli (2001)

Menu planning, pricing, designing, analyzing and improving practices of seven

hospitality firms Menu planning

2.5 Naipaul and Parsa (2001)The relationships between psychological pricing comprising

odd and even number price endings, and value and quality perceptions of customers

Menu pricing .Wansink et al. (2001) The relationship between descriptive menu item

labels and customer perceptions Menu designing

2.6 DiPietro et al. (2004)Consumer attitudes towards healthy menu items and

investigation of sales trends in healthy menu items Menu planning Antun and

Gustafson (2005)Menu design characteristics and pricing strategies used by restaurants

and clubs.

CHAPTER 3

3.METHODOLOGY

3.1 - Login module

3.2 - Masterclass and delivery module

11
 3.3 - Employee module

3.4 - Printable module

3.5 - Schedule and Reservation module

3.1 – Login module:

The Login Module is a portal module that allows users to type a user name

and password to log in. This module can be placed on any module tab to

allow users to log in to the system.

3.2– Masterclass and delivery module:

You can access hut list and the name of the hut and add the image of the

hut ,From menu selection we can add menu items and edit the name of

the menu items, In delivery module ,it shows the delivery date, full

name ,contact n. o, address , remarks, orders and process of type product

and status of the project delivered

3.3– Employee module:

The Employee Module has been designed to drive efficiency within your

organization by automating the creation of resume documents and

allowing you to automatically synchronise employee data between Open

Asset and your HR or ERP system.

12
Open Asset uses systems such as HTML and CSS as the single source of

truth for employee-related data, ensuring that errors and inconsistencies in

data management are minimised. If your organization stores employee-

related data in static documents, this information can be managed directly

in Open Asset through customizable fields.

3.4– Printable module:

In printable module we can print the bill And also the payroll and pays lip

of the employee as a pdf format and The payroll and pays lip includes

Employee name ,employee number ,gross deductions ,cash advance and

net pay.

3.5- Schedule and Reservation module:

In schedule Module which contains employee number and name and IN

and out time and this also can be printable In Reservation module which

contains name ,Hut number , Table number ,start date ,End date and

finally orders

3.6 - Technologies used:

PHP

MYSQL

SAP CRYSTAL FORMS

13
CSS

HTML

BOOTSTRAB

4 - RESULTS AND DISCUSSIONS:

4.RESULTS:

4.1. Performance Requirements:

The proposed system that we are going to develop will be used as the

Chief performance system for providing help to the organization in

managing the whole database of the Restaurant management system..

Therefore, it is expected that the database would perform functionally all

the requirements that are specified.

4.2. Safety Requirements:

The database may get crashed at any certain time due to virus or operating

system failure. Therefore, it is required to take the database backup.

4.3. Security Requirements:

The restaurant industry reports some of the highest numbers of security

breaches. A lot of sensitive customer data, including names, addresses, debit,
and credit card details are processed and stored in hotel databases, hence
easily targeted by cybercriminals

4 - DISCUSSIONS:

4.1.1) Scope and purpose

The purpose of the design phase is to develop a clear understanding of

what the developer want people to gain from his/her project. As you the

developer work on the project, the test for every design decision should be

14
"Does this feature ful fill the ultimate purpose of the project?"

A purpose statement affects the design process by explaining what the

developer wants the project to do, rather than describing the project itself.

The Design Document will verify that the current design meets all of the

explicit requirements contained in the system model as well as the implicit

requirements desired by the customer.

4.1. 2) PLATFORM:

Operating System: Microoft Windows

Technologies Used:

Front End: HTML,CSS,BOOTSTRAB.

Web designing language: PHP

MySQL Software Requirements:

PHP 5.0

APACHE HTTP Server

Dream were,FrontPage for Front End Programming

Microsoft Windows or Linux

Hardware Requirements:

Intel Pentium IV processor or equivalent or higher

512 MB Ram or Higher

20 GB HDD or Higher

Network Connectivity

15
4.2.2) Overall System Design Objectives

The overall system design objective is to provide an efficient, modular

design that will reduce the system’s complexity, facilitate change and

result in an easy implementation. This will be accomplished by designing

strongly cohesion system with minimal coupling. In addition, this document

will provide interface design models that are consistent user friendly and

will provide straight forward transition through the various system

functions.

4.3.3) Structure of Design Document

System Architecture Design – The System architecture section has

detailed diagram of the system, server and client architecture.

Data Design – The data Design include an ERD as well as Database

design

16
5 - CONCLUSION AND FUTURE WORK:

5.1.SYSTEM ARCHITECTURE DESIGN:

17
18
5.2 - DATA FLOW

DESIGN:

5.3 - FINAL CONCLUSION:

19
 Here, I have come to the end of the project on the title of

student evaluation system. I tried my best to include all the

necessary points that are required related to the given title.

Some of the information I wrote in the project’s literature

review were taken from the internet and I have also referred

some books. And This presentation contains information and

some concepts of my projects. I do hope that my project will

be interesting and may be even knowledgeable.”

6 - REFERENCES:

[1]PHP book by Vasvani (TMH publications).

[2] Beginning PHP5 by WROX.

[3] www.google.com.

[4] www.wikipedia.com

[5] Mayur Jain,” Smart Home System Using Android Mobile Devices”,
Journal of Computing Technologies Vol 2, Issue 3 ISSN 2278
– 3814.

[6] IEEE std. 802.15.4 - 2003: “Wireless Medium Access Control (MAC) and
Physical Layer (PHY) specifications for Low Rate
Wireless Personal Area Networks (LRWPANs)”

[7] Kiumi Akingbehin , Akinsola Aking behin, “Alternatives for Short

Range Low Power Wireless Communications,” IEEE.2005: 94 -

20
 [8] QIN Tinghao, DOU Xiaoqian, “Application of ZigBee Technology in
Wireless Sensor Network,” Instrumentation Technology, 2007, pp.57-59.
7 - APPENIDICES:

7.1 Source code:

--
-- Database: `db_reservation`
--

-- --------------------------------------------------------

--
-- Table structure for table `attendance`
--

CREATE TABLE `attendance` (

`attendance_id` int(11) NOT NULL,
`employee_id` int(11) NOT NULL,
`date` varchar(20) DEFAULT NULL,
`time_in` varchar(50) DEFAULT NULL,
`time_out` varchar(50) DEFAULT NULL,
`status` int(11) NOT NULL,
`num_hr` decimal(10,2) NOT NULL DEFAULT 0.00
) ENGINE=InnoDB DEFAULT CHARSET=latin1;

-- --------------------------------------------------------

--
-- Table structure for table `biometrics_attendance`
--

CREATE TABLE `biometrics_attendance` (

`bio_id` int(11) NOT NULL,
`biometric_num` text NOT NULL,
`employee_id` int(11) NOT NULL DEFAULT 0,
`employee_name` varchar(50) DEFAULT NULL,
`date` varchar(20) DEFAULT NULL,
`dtr_day` varchar(20) DEFAULT NULL,
`time_in` varchar(20) DEFAULT NULL,
`time_out` varchar(20) DEFAULT NULL,
`dtr_breakin` varchar(20) DEFAULT NULL,
`dtr_breakout` varchar(20) DEFAULT NULL,
`status` int(11) NOT NULL DEFAULT 0,
`num_hr` decimal(10,2) NOT NULL DEFAULT 0.00,
`date_today` varchar(20) DEFAULT NULL
) ENGINE=InnoDB DEFAULT CHARSET=latin1;

--
-- Dumping data for table `biometrics_attendance`
--

21
INSERT INTO `biometrics_attendance` (`bio_id`, `biometric_num`,
`employee_id`, `employee_name`, `date`, `dtr_day`, `time_in`,
`time_out`, `dtr_breakin`, `dtr_breakout`, `status`, `num_hr`,
`date_today`) VALUES
(3, '6231415', 1, 'John Smith', '2021-11-15', 'Monday',
'6:45:32', '16:15:00', '', '', 1, '9.49', NULL),
(4, '6231415', 1, 'John Smith', '2021-11-16', 'Tuesday',
'6:45:32', '16:15:00', '', '', 1, '9.49', NULL),
(5, '6231415', 1, 'John Smith', '2021-11-17', 'Wednesday',
'6:45:32', '16:15:00', '', '', 1, '9.49', NULL),
(6, '6231415', 1, 'John Smith', '2021-11-18', 'Thursday',
'6:45:32', '16:15:00', '', '', 1, '9.49', NULL),
(7, '6231415', 1, 'John Smith', '2021-11-19', 'Friday',
'6:45:32', '16:15:00', '', '', 1, '9.49', NULL),
(8, '6231415', 1, 'John Smith', '2021-11-20', 'Saturday',
'6:45:32', '16:15:00', '', '', 1, '9.49', NULL),
(9, '6231415', 1, 'John Smith', '2021-11-22', 'Monday',
'6:45:32', '16:15:00', '', '', 1, '9.49', NULL),
(10, '6231415', 1, 'John Smith', '2021-11-23', 'Tuesday',
'6:45:32', '16:15:00', '', '', 1, '9.49', NULL),
(11, '6231415', 1, 'John Smith', '2021-11-24', 'Wednesday',
'7:05:23', '16:15:00', '', '', 0, '9.16', NULL),
(12, '6231415', 1, 'John Smith', '2021-11-25', 'Thursday',
'6:45:32', '16:15:00', '', '', 1, '9.49', NULL),
(13, '6231415', 1, 'John Smith', '2021-11-26', 'Friday',
'6:45:32', '16:15:00', '', '', 1, '9.49', NULL),
(14, '6231415', 1, 'John Smith', '2021-11-27', 'Saturday',
'6:45:32', '16:15:00', '', '', 1, '9.49', NULL),
(15, '6231415', 1, 'John Smith', '2021-11-29', 'Monday',
'6:45:32', '16:15:00', '', '', 1, '9.49', NULL),
(16, '6231415', 1, 'John Smith', '2021-11-30', 'Tuesday',
'6:45:32', '16:15:00', '', '', 1, '9.49', NULL);

-- --------------------------------------------------------

--
-- Table structure for table `cashadvance`
--

CREATE TABLE `cashadvance` (

`cash_id` int(11) NOT NULL,
`date_advance` varchar(20) DEFAULT NULL,
`employee_id` varchar(15) NOT NULL,
`amount` decimal(10,2) NOT NULL DEFAULT 0.00
) ENGINE=InnoDB DEFAULT CHARSET=latin1;

--
-- Dumping data for table `cashadvance`

--

22
INSERT INTO `cashadvance` (`cash_id`, `date_advance`,
`employee_id`, `amount`) VALUES
(1, '2021-11-16', '1', '1500.00');
-- --------------------------------------------------------

--
-- Table structure for table `delivery_details`
--

CREATE TABLE `delivery_details` (

`del_det_id` int(11) NOT NULL,
`delivery_id` int(11) NOT NULL DEFAULT 0,
`menu_id` int(11) NOT NULL DEFAULT 0,
`quantity` decimal(10,2) NOT NULL DEFAULT 0.00
) ENGINE=InnoDB DEFAULT CHARSET=latin1;

--
-- Dumping data for table `delivery_details`
--

INSERT INTO `delivery_details` (`del_det_id`, `delivery_id`,

`menu_id`, `quantity`) VALUES
(1, 1, 39, '5.00'),
(2, 1, 37, '1.00'),
(3, 1, 3, '1.00'),
(4, 1, 40, '2.00'),
(5, 2, 40, '2.00'),
(6, 0, 5, '1.00'),
(7, 0, 8, '2.00');

-- --------------------------------------------------------

--
-- Table structure for table `delivery_details_tmp`
--

CREATE TABLE `delivery_details_tmp` (

`del_det_id` int(11) NOT NULL,
`delivery_id` int(11) NOT NULL DEFAULT 0,
`menu_id` int(11) NOT NULL DEFAULT 0,
`quantity` decimal(10,2) NOT NULL DEFAULT 0.00
) ENGINE=InnoDB DEFAULT CHARSET=latin1;

-- --------------------------------------------------------

--
-- Table structure for table `delivery_head`
--

CREATE TABLE `delivery_head` (

`delivery_id` int(11) NOT NULL,
`delivery_date` varchar(20) DEFAULT NULL,
`register_id` int(11) NOT NULL DEFAULT 0,
`address` text DEFAULT NULL,
`remarks` text DEFAULT NULL,

23
 `delivered` int(11) NOT NULL DEFAULT 0
) ENGINE=InnoDB DEFAULT CHARSET=latin1;

--
-- Dumping data for table `delivery_head`
--

INSERT INTO `delivery_head` (`delivery_id`, `delivery_date`,

`register_id`, `address`, `remarks`, `delivered`) VALUES
(1, '2021-11-18', 3, 'Sample Address', 'Sample Only', 1),
(2, '2021-11-18', 3, 'asdadsas asd', 'asd asd', 1),
(3, '2021-11-18', 3, 'test', 'test', 0),
(4, '2021-11-18', 3, 'test', 'test', 0),
(5, '2021-11-18', 3, 'sadads', 'asdasd', 0);

-- --------------------------------------------------------

--
-- Table structure for table `employees`
--

CREATE TABLE `employees` (

`employee_id` int(11) NOT NULL,
`employee_number` varchar(50) DEFAULT NULL,
`firstname` varchar(50) DEFAULT NULL,
`lastname` varchar(50) DEFAULT NULL,
`address` text DEFAULT NULL,
`birthdate` varchar(20) DEFAULT NULL,
`contact_info` varchar(20) DEFAULT NULL,
`gender` varchar(10) DEFAULT NULL,
`position_id` int(11) NOT NULL,
`schedule_id` int(11) NOT NULL,
`photo` varchar(50) DEFAULT NULL,
`created_on` varchar(20) DEFAULT NULL,
`sss_amount` decimal(10,2) NOT NULL DEFAULT 0.00,
`philhealth_amount` decimal(10,2) NOT NULL DEFAULT 0.00,
`pagibig_amount` decimal(10,2) NOT NULL DEFAULT 0.00
) ENGINE=InnoDB DEFAULT CHARSET=latin1;

--
-- Dumping data for table `employees`
--

INSERT INTO `employees` (`employee_id`, `employee_number`,

`firstname`, `lastname`, `address`, `birthdate`, `contact_info`,
`gender`, `position_id`, `schedule_id`, `photo`, `created_on`,
`sss_amount`, `philhealth_amount`, `pagibig_amount`) VALUES
(1, '6231415', 'John', 'Smith', 'Sample Address 101', '1997-06-
23', '091234564789', 'Male', 2, 1, 'avatar.png', '2021-11-18
02:38:54', '375.00', '300.00', '100.00');

-- --------------------------------------------------------

--
-- Table structure for table `huts`

24
--

CREATE TABLE `huts` (

`hut_id` int(11) NOT NULL,
`hut_name` varchar(100) DEFAULT NULL,
`reserved` int(11) NOT NULL DEFAULT 0,
`hut_image` varchar(255) DEFAULT NULL
) ENGINE=InnoDB DEFAULT CHARSET=latin1;

--
-- Dumping data for table `huts`
--

INSERT INTO `huts` (`hut_id`, `hut_name`, `reserved`,

`hut_image`) VALUES
(1, 'Huts 1', 1, 'no-image-available.png'),
(2, 'Huts 2', 0, 'no-image-available.png'),
(3, 'Huts 3', 0, 'Huts 3.jpg');

-- --------------------------------------------------------
--
-- Table structure for table `menu`
--

CREATE TABLE `menu` (

`menu_id` int(11) NOT NULL,
`menucat_id` int(11) NOT NULL DEFAULT 0,
`menu_name` text DEFAULT NULL,
`menu_price` decimal(10,2) NOT NULL DEFAULT 0.00,
`menu_desc` text DEFAULT NULL,
`menu_img` varchar(255) DEFAULT NULL
) ENGINE=InnoDB DEFAULT CHARSET=latin1;

--
-- Dumping data for table `menu`
--

INSERT INTO `menu` (`menu_id`, `menucat_id`, `menu_name`,

`menu_price`, `menu_desc`, `menu_img`) VALUES
(2, 4, 'BUTTERED GARLIC SHRIMP', '230.00', '(250 grams)',
'watermark-2019-07-15-13-51-59-1_orig.jpg'),
(3, 2, 'GRILLED', '120.00', '(250 grams)', 'tilapia-asada-la-
parilla-21187035.jpg'),
(4, 3, 'SINIGANG NA BULGAN', '250.00', 'PER KILO', 'sinigang-na-
bulgan-sa.jpg'),
(5, 2, 'FRIED', '120.00', '(250 grams)', 'tilapiafry.jpg'),
(8, 2, 'GINATA-AN', '150.00', '(250 grams)',
'Chrysanthemum.jpg'),
(9, 4, 'GAMBAS', '200.00', '(250 grams)', 'Spanish-Garlic-
Prawns-I-800x530.jpg'),
(10, 4, 'TEMPURA', '230.00', '(250 Grams)', 'maxresdefault.jpg'),
(11, 4, 'KINILAW', '230.00', '(250 grams)', 'Shrimp-Kinilaw-2-
1.jpg'),
(12, 5, 'BUTTERED GARLIC CRAB', '200.00', '(250 grams)',
'images.jpg'),

25
(13, 5, 'CHILI SAUCE CRAB', '200.00', 'mild spicy, spicy',
'FB_IMG_1503673872844.jpg'),
(14, 5, 'STEAMED CRAB', '180.00', '(250 grams)', '110885865-
steamed-crab.jpg'),
(15, 15, 'CHILI SAUCE ALIMANGO', '280.00', '(250 grams)',
'spicy-crab-recipe.jpg'),
(16, 15, 'GINATA-ANG ALIMANGO', '280.00', '(250 grams)',
'filipino-ginataang-alimango19.jpg'),
(17, 15, 'BUTTERED GARLIC ALIMANGO', '280.00', '(250 grams)',
'48ffa965cf2ac9dc203222da8bea9433.jpg'),
(18, 15, 'STEAMED ALIMANGO', '250.00', '(250 grams)',
'cde5908947e9cde7d95cf876695f9df3.jpg'),
(19, 16, 'SIZZLING SQUID', '200.00', '(250 grams)', 'images
(1).jpg'),
(20, 16, 'CALAMARES', '200.00', '(250 grams)', 'images (2).jpg'),
(21, 16, 'ADOBO', '200.00', '(250 grams)', 'adobong-pusit.jpg'),
(22, 10, 'BINAKOL (native)', '350.00', '(500 grams)', 'chicken-
binakol-2.jpg'),
(23, 10, 'ADOBO (native)', '365.00', '(500 grams)',
'15aa77bbff4868019b2809bdcde00409 (1).jpg'),
(24, 10, 'PECHO PACK', '80.00', 'grilled', 'Snapseed_3.jpg'),
(25, 10, 'PAA', '75.00', 'grilled',
'49688913043_12a19b0e6d_c.jpg'),
(26, 10, 'ISOL', '50.00', 'grilled', 'atay-baticolon-isol.jpg'),
(27, 10, 'ATAY', '35.00', 'grilled', 'grilled_liver.jpg'),
(28, 10, 'BATIKULON', '28.00', 'grilled',
'102b7eea5361aff310c540995_original_.jpg'),
(29, 7, 'BBQ', '25.00', '(per stick) grilled', 'pork-bbq.jpg'),
(30, 7, 'LITSON KAWALI', '250.00', '(500 grams)', 'images
(3).jpg'),
(31, 7, 'CRISPY PATA', '450.00', '', 'crispy-pata1.jpg'),
(32, 7, 'SISIG', '120.00', '',
'0aa0651fa472beea86a02de659f292af.jpg'),
(33, 7, 'BACK RIBS', '150.00', '', 'Pressure-Cooker-Baby-Back-
Ribs.jpg'),
(34, 7, 'LIEMPO', '100.00', '', 'inihaw-na-liempo-4.jpg'),
(35, 7, 'SPARE RIBS', '150.00', '', 'glazed-spareribs-18-
56a8ba813df78cf772a022f9.jpg'),
(36, 7, 'BICOL EXPRESS', '160.00', '', 'bicol-express--lg-
38436p47160.jpg'),
(37, 17, 'CHOPSAUY', '160.00', '(can add meat ingredient)',
'chopsuey-tofu-shiitake-mushrooms-2.jpg'),
(38, 18, 'PLAIN RICE', '15.00', '(Platter for occasion)',
'rice.png'),
(39, 18, 'GARLIC RICE', '20.00', '(Platter for occasion)',
'sinangag2.jpg'),
(40, 19, 'Sample Menu', '300.00', 'This is a sample description
of the menu', 'Sample Menu-40.jpg');

-- --------------------------------------------------------

--
-- Table structure for table `menu_category`
--

26
CREATE TABLE `menu_category` (
`menucat_id` int(11) NOT NULL,
`menusel_id` int(11) NOT NULL DEFAULT 0,
`menu_category` varchar(50) DEFAULT NULL
) ENGINE=InnoDB DEFAULT CHARSET=latin1;

--
-- Dumping data for table `menu_category`
--

INSERT INTO `menu_category` (`menucat_id`, `menusel_id`,

`menu_category`) VALUES
(2, 2, 'TILAPIA'),
(3, 2, 'BULGAN'),
(4, 2, 'SHRIMP'),
(5, 2, 'CRAB'),
(7, 3, 'PORK'),
(8, 2, 'BANGUS'),
(9, 3, 'BEEF'),
(10, 3, 'CHICKEN'),
(12, 3, 'GOAT MEAT'),
(13, 2, 'TALABA'),
(14, 2, 'TANGIGUE'),
(15, 2, 'ALIMANGO'),
(16, 2, 'SQUID'),
(17, 4, 'MIXED VEGES'),
(18, 8, 'RICE'),
(19, 10, 'Menu 101');

-- --------------------------------------------------------

--
-- Table structure for table `menu_selection`
--

CREATE TABLE `menu_selection` (

`menusel_id` int(11) NOT NULL,
`menu_selection` varchar(100) DEFAULT NULL
) ENGINE=InnoDB DEFAULT CHARSET=latin1;

--
-- Dumping data for table `menu_selection`
--

INSERT INTO `menu_selection` (`menusel_id`, `menu_selection`)

VALUES
(2, 'SEAFOODS'),
(3, 'MEAT'),
(4, 'VEGETABLES'),
(5, 'DESSERTS'),
(6, 'PIKA-PIKA'),
(7, 'SOUP'),
(8, 'RICE'),
(9, 'BEVERAGE'),
(10, 'Sample 23');

27
-- --------------------------------------------------------

--
-- Table structure for table `overtime`
--

CREATE TABLE `overtime` (

`overtime_id` int(11) NOT NULL,
`employee_id` int(11) NOT NULL,
`hours` decimal(10,2) NOT NULL DEFAULT 0.00,
`rate` decimal(10,2) NOT NULL DEFAULT 0.00,
`date_overtime` varchar(20) DEFAULT NULL
) ENGINE=InnoDB DEFAULT CHARSET=latin1;

--
-- Dumping data for table `overtime`
--

INSERT INTO `overtime` (`overtime_id`, `employee_id`, `hours`,

`rate`, `date_overtime`) VALUES
(1, 1, '3.50', '500.00', '2021-11-16');

-- --------------------------------------------------------

--
-- Table structure for table `position`
--

CREATE TABLE `position` (

`position_id` int(11) NOT NULL,
`position_name` varchar(50) DEFAULT NULL,
`rate` decimal(10,2) NOT NULL DEFAULT 0.00
) ENGINE=InnoDB DEFAULT CHARSET=latin1;

--
-- Dumping data for table `position`
--

INSERT INTO `position` (`position_id`, `position_name`, `rate`)

VALUES
(1, 'Waiter', '90.00'),
(2, 'Cook', '100.00'),
(3, 'Cleaner', '70.00');

-- --------------------------------------------------------

--
-- Table structure for table `registration`
--

CREATE TABLE `registration` (

`register_id` int(11) NOT NULL,
`fname` varchar(50) DEFAULT NULL,
`mname` varchar(50) DEFAULT NULL,

28
 `lname` varchar(50) DEFAULT NULL,
`contact_no` varchar(20) DEFAULT NULL,
`email` varchar(50) DEFAULT NULL,
`password` varchar(50) DEFAULT NULL
) ENGINE=InnoDB DEFAULT CHARSET=latin1;

--
-- Dumping data for table `registration`
--

INSERT INTO `registration` (`register_id`, `fname`, `mname`,

`lname`, `contact_no`, `email`, `password`) VALUES
(1, 'TETSING', 'Pido', 'TESTING', '1213123',
'[email protected]', '1234'),
(2, 'Jason', '', 'Flor', '09187811212', '[email protected]',
'1234'),
(3, 'Claire', 'C', 'Blake', '09123654988', '[email protected]',
'cblake123');

-- --------------------------------------------------------

--
-- Table structure for table `reservation`
--

CREATE TABLE `reservation` (

`reservation_id` int(11) NOT NULL,
`register_id` int(11) NOT NULL DEFAULT 0,
`start_date` varchar(20) DEFAULT NULL,
`end_date` varchar(20) DEFAULT NULL,
`trans_done` int(11) NOT NULL DEFAULT 0
) ENGINE=InnoDB DEFAULT CHARSET=latin1;

--
-- Dumping data for table `reservation`
--

INSERT INTO `reservation` (`reservation_id`, `register_id`,

`start_date`, `end_date`, `trans_done`) VALUES
(1, 1, '2021-11-19', '2021-11-19', 1),
(2, 3, '2021-11-18', '2021-11-18', 1),
(3, 3, '2021-11-18', '2021-11-18', 0);

-- --------------------------------------------------------

--
-- Table structure for table `reservation_details`
--

CREATE TABLE `reservation_details` (

`res_det_id` int(11) NOT NULL,
`reservation_id` int(11) NOT NULL DEFAULT 0,
`hut_id` int(11) NOT NULL DEFAULT 0,
`menu_id` int(11) NOT NULL DEFAULT 0,
`table_id` int(11) NOT NULL DEFAULT 0,

29
 `done` int(11) NOT NULL DEFAULT 0,
`quantity` decimal(10,2) NOT NULL DEFAULT 0.00
) ENGINE=InnoDB DEFAULT CHARSET=latin1;

--
-- Dumping data for table `reservation_details`
--

INSERT INTO `reservation_details` (`res_det_id`,

`reservation_id`, `hut_id`, `menu_id`, `table_id`, `done`,
`quantity`) VALUES
(1, 1, 0, 40, 0, 1, '3.00'),
(2, 1, 0, 39, 0, 1, '10.00'),
(3, 1, 0, 38, 0, 1, '20.00'),
(4, 1, 0, 37, 0, 1, '2.00'),
(5, 1, 0, 0, 3, 1, '0.00'),
(6, 1, 3, 0, 0, 1, '0.00'),
(7, 2, 0, 37, 0, 1, '2.00'),
(8, 2, 0, 0, 3, 1, '0.00'),
(9, 2, 2, 0, 0, 1, '0.00'),
(10, 3, 0, 40, 0, 1, '2.00'),
(11, 3, 0, 0, 1, 0, '0.00'),
(12, 3, 1, 0, 0, 0, '0.00');

-- --------------------------------------------------------

--
-- Table structure for table `reservation_details_tmp`
--

CREATE TABLE `reservation_details_tmp` (

`res_det_id` int(11) NOT NULL,
`reservation_id` int(11) NOT NULL DEFAULT 0,
`hut_id` int(11) NOT NULL DEFAULT 0,
`menu_id` int(11) NOT NULL DEFAULT 0,
`table_id` int(11) NOT NULL DEFAULT 0,
`done` int(11) NOT NULL DEFAULT 0,
`quantity` decimal(10,2) NOT NULL DEFAULT 0.00
) ENGINE=InnoDB DEFAULT CHARSET=latin1;

-- --------------------------------------------------------

--
-- Table structure for table `reservation_tmp`
--

CREATE TABLE `reservation_tmp` (

`reservation_id` int(11) NOT NULL,
`register_id` int(11) NOT NULL DEFAULT 0,
`start_date` varchar(20) DEFAULT NULL,
`end_date` varchar(20) DEFAULT NULL,
`trans_done` int(11) NOT NULL DEFAULT 0
) ENGINE=InnoDB DEFAULT CHARSET=latin1;

-- --------------------------------------------------------

30
--
-- Table structure for table `schedules`
--

CREATE TABLE `schedules` (

`schedule_id` int(11) NOT NULL,
`time_in` varchar(20) DEFAULT NULL,
`time_out` varchar(20) DEFAULT NULL
) ENGINE=InnoDB DEFAULT CHARSET=latin1;

--
-- Dumping data for table `schedules`
--

INSERT INTO `schedules` (`schedule_id`, `time_in`, `time_out`)

VALUES
(1, '07:00', '16:00');

-- --------------------------------------------------------

--
-- Table structure for table `tables`
--

CREATE TABLE `tables` (

`table_id` int(11) NOT NULL,
`table_no` varchar(100) DEFAULT NULL,
`reserved` int(11) NOT NULL DEFAULT 0,
`table_img` varchar(255) DEFAULT NULL
) ENGINE=InnoDB DEFAULT CHARSET=latin1;

--
-- Dumping data for table `tables`
--

INSERT INTO `tables` (`table_id`, `table_no`, `reserved`,

`table_img`) VALUES
(1, 'Table 1', 1, ''),
(2, 'Table 2', 0, ''),
(3, 'Table 3', 0, 'Table 3.jpg');

-- --------------------------------------------------------

--
-- Table structure for table `users`
--

CREATE TABLE `users` (

`user_id` int(11) NOT NULL,
`username` varchar(50) DEFAULT NULL,
`password` text DEFAULT NULL,
`usertype` int(11) NOT NULL DEFAULT 0 COMMENT '1=Admin,
2=Staff, 3=Users',
`fullname` varchar(50) DEFAULT NULL

31
) ENGINE=InnoDB DEFAULT CHARSET=latin1;

--
-- Dumping data for table `users`
--

INSERT INTO `users` (`user_id`, `username`, `password`,

`usertype`, `fullname`) VALUES
(1, 'admin', 'admin', 1, 'Admin');

--
-- Indexes for dumped tables
--

--
-- Indexes for table `attendance`
--
ALTER TABLE `attendance`
ADD PRIMARY KEY (`attendance_id`);

--
-- Indexes for table `biometrics_attendance`
--
ALTER TABLE `biometrics_attendance`
ADD PRIMARY KEY (`bio_id`);

--
-- Indexes for table `cashadvance`
--
ALTER TABLE `cashadvance`
ADD PRIMARY KEY (`cash_id`);

--
-- Indexes for table `delivery_details`
--
ALTER TABLE `delivery_details`
ADD PRIMARY KEY (`del_det_id`);

--
-- Indexes for table `delivery_details_tmp`
--
ALTER TABLE `delivery_details_tmp`
ADD PRIMARY KEY (`del_det_id`);

--
-- Indexes for table `delivery_head`
--
ALTER TABLE `delivery_head`
ADD PRIMARY KEY (`delivery_id`);

--
-- Indexes for table `employees`
--
ALTER TABLE `employees`
ADD PRIMARY KEY (`employee_id`);

32
--
-- Indexes for table `huts`
--
ALTER TABLE `huts`
ADD PRIMARY KEY (`hut_id`);

--
-- Indexes for table `menu`
--
ALTER TABLE `menu`
ADD PRIMARY KEY (`menu_id`);

--
-- Indexes for table `menu_category`
--
ALTER TABLE `menu_category`
ADD PRIMARY KEY (`menucat_id`);

--
-- Indexes for table `menu_selection`
--
ALTER TABLE `menu_selection`
ADD PRIMARY KEY (`menusel_id`);

--
-- Indexes for table `overtime`
--
ALTER TABLE `overtime`
ADD PRIMARY KEY (`overtime_id`);

--
-- Indexes for table `position`
--
ALTER TABLE `position`
ADD PRIMARY KEY (`position_id`);

--
-- Indexes for table `registration`
--
ALTER TABLE `registration`
ADD PRIMARY KEY (`register_id`);

--
-- Indexes for table `reservation`
--
ALTER TABLE `reservation`
ADD PRIMARY KEY (`reservation_id`);

--
-- Indexes for table `reservation_details`
--
ALTER TABLE `reservation_details`
ADD PRIMARY KEY (`res_det_id`);

33
--
-- Indexes for table `reservation_details_tmp`
--
ALTER TABLE `reservation_details_tmp`
ADD PRIMARY KEY (`res_det_id`);

--
-- Indexes for table `reservation_tmp`
--
ALTER TABLE `reservation_tmp`
ADD PRIMARY KEY (`reservation_id`);

--
-- Indexes for table `schedules`
--
ALTER TABLE `schedules`
ADD PRIMARY KEY (`schedule_id`);

--
-- Indexes for table `tables`
--
ALTER TABLE `tables`
ADD PRIMARY KEY (`table_id`);

--
-- Indexes for table `users`
--
ALTER TABLE `users`
ADD PRIMARY KEY (`user_id`);

--
-- AUTO_INCREMENT for dumped tables
--

--
-- AUTO_INCREMENT for table `attendance`
--
ALTER TABLE `attendance`
MODIFY `attendance_id` int(11) NOT NULL AUTO_INCREMENT;

--
-- AUTO_INCREMENT for table `biometrics_attendance`
--
ALTER TABLE `biometrics_attendance`
MODIFY `bio_id` int(11) NOT NULL AUTO_INCREMENT,
AUTO_INCREMENT=17;

--
-- AUTO_INCREMENT for table `cashadvance`
--
ALTER TABLE `cashadvance`
MODIFY `cash_id` int(11) NOT NULL AUTO_INCREMENT,
AUTO_INCREMENT=2;

--

34
-- AUTO_INCREMENT for table `delivery_details`
--
ALTER TABLE `delivery_details`
MODIFY `del_det_id` int(11) NOT NULL AUTO_INCREMENT,
AUTO_INCREMENT=8;

--
-- AUTO_INCREMENT for table `delivery_details_tmp`
--
ALTER TABLE `delivery_details_tmp`
MODIFY `del_det_id` int(11) NOT NULL AUTO_INCREMENT,
AUTO_INCREMENT=18;

--
-- AUTO_INCREMENT for table `delivery_head`
--
ALTER TABLE `delivery_head`
MODIFY `delivery_id` int(11) NOT NULL AUTO_INCREMENT,
AUTO_INCREMENT=6;

--
-- AUTO_INCREMENT for table `employees`
--
ALTER TABLE `employees`
MODIFY `employee_id` int(11) NOT NULL AUTO_INCREMENT,
AUTO_INCREMENT=2;

--
-- AUTO_INCREMENT for table `huts`
--
ALTER TABLE `huts`
MODIFY `hut_id` int(11) NOT NULL AUTO_INCREMENT,
AUTO_INCREMENT=4;

--
-- AUTO_INCREMENT for table `menu`
--
ALTER TABLE `menu`
MODIFY `menu_id` int(11) NOT NULL AUTO_INCREMENT,
AUTO_INCREMENT=42;

--
-- AUTO_INCREMENT for table `menu_category`
--
ALTER TABLE `menu_category`
MODIFY `menucat_id` int(11) NOT NULL AUTO_INCREMENT,
AUTO_INCREMENT=21;

--
-- AUTO_INCREMENT for table `menu_selection`
--
ALTER TABLE `menu_selection`
MODIFY `menusel_id` int(11) NOT NULL AUTO_INCREMENT,
AUTO_INCREMENT=12;

35
--
-- AUTO_INCREMENT for table `overtime`
--
ALTER TABLE `overtime`
MODIFY `overtime_id` int(11) NOT NULL AUTO_INCREMENT,
AUTO_INCREMENT=2;

--
-- AUTO_INCREMENT for table `position`
--
ALTER TABLE `position`
MODIFY `position_id` int(11) NOT NULL AUTO_INCREMENT,
AUTO_INCREMENT=4;

--
-- AUTO_INCREMENT for table `registration`
--
ALTER TABLE `registration`
MODIFY `register_id` int(11) NOT NULL AUTO_INCREMENT,
AUTO_INCREMENT=4;

--
-- AUTO_INCREMENT for table `reservation`
--
ALTER TABLE `reservation`
MODIFY `reservation_id` int(11) NOT NULL AUTO_INCREMENT,
AUTO_INCREMENT=4;

--
-- AUTO_INCREMENT for table `reservation_details`
--
ALTER TABLE `reservation_details`
MODIFY `res_det_id` int(11) NOT NULL AUTO_INCREMENT,
AUTO_INCREMENT=13;

--
-- AUTO_INCREMENT for table `reservation_details_tmp`
--
ALTER TABLE `reservation_details_tmp`
MODIFY `res_det_id` int(11) NOT NULL AUTO_INCREMENT,
AUTO_INCREMENT=13;

--
-- AUTO_INCREMENT for table `reservation_tmp`
--
ALTER TABLE `reservation_tmp`
MODIFY `reservation_id` int(11) NOT NULL AUTO_INCREMENT,
AUTO_INCREMENT=2;

--
-- AUTO_INCREMENT for table `schedules`
--
ALTER TABLE `schedules`
MODIFY `schedule_id` int(11) NOT NULL AUTO_INCREMENT,
AUTO_INCREMENT=2;

36
--
-- AUTO_INCREMENT for table `tables`
--
ALTER TABLE `tables`
MODIFY `table_id` int(11) NOT NULL AUTO_INCREMENT,
AUTO_INCREMENT=5;

--
-- AUTO_INCREMENT for table `users`
--
ALTER TABLE `users`
MODIFY `user_id` int(11) NOT NULL AUTO_INCREMENT,
AUTO_INCREMENT=2;
COMMIT;

/*!40101 SET CHARACTER_SET_CLIENT=@OLD_CHARACTER_SET_CLIENT */;

/*!40101 SET CHARACTER_SET_RESULTS=@OLD_CHARACTER_SET_RESULTS */;
/*!40101 SET COLLATION_CONNECTION=@OLD_COLLATION_CONNECTION */;

37
7.2 – SCREENSHOTS:

38
39
40
41
42
43