VISVESVARAYA TECHNOLOGICAL UNIVERSITY

Jnana Sangama, Santhibastawad Road, Machhe

Belagavi – 590018, Karnataka, India

DBMS MINI Project Report on

ONLINE RESTAURANT MANAGMENT

Submitted in partial fulfillment of the requirements for the award of the degree
of
BACHELOR OF ENGINEERING
in
INFORMATION SCIENCE AND ENGINEERING
For the academic year 2018-2019

Submitted by Under the guidance of

SUSHMITHA S Mrs. Apasara M B
1JS16IS081 Asst. Prof, Dept. of ISE
T S THANYA GOWDA Mrs.Mamatha G
1JS16IS003 Asst. Prof, Dept. of ISE

JSS Academy of Technical Education

(Affiliated to VTU Belagavi and Approved by AICTE New Delhi)
JSSATEB Campus, Dr Vishnuvardhan Road, Bengaluru- 560060
www.jssateb.ac.in, 080-2861 2425 / 2861 2565

Department of Information Science and Engineering

2018 – 2019

Page | 1
JSS Academy of Technical Education
(Affiliated to VTU Belagavi and Approved by AICTE New Delhi)
JSSATEB Campus, Dr Vishnuvardhan Road, Bengaluru- 60
www.jssateb.ac.in, 080-2861 2425 / 2861 2565

DEPARTMENT OF INFORMATION SCIENCE AND ENGINEERING

CERTIFICATE

This is to certify that the DBMS Mini Project entitled ONLINE RESTAURANT
MANAGMENT carried out by, SUSHMITHA S with University seat number
1JS16IS081 and T S THANYA GOWDA with University seat number
1JS16IS083, are bonafide students of V Semester BE, JSS Academy of Technical
Education in partial fulfilment for the Bachelor of Engineering in INFORMATION
SCIENCE AND ENGINEERING of the Visvesvaraya Technological University,
Belagavi during the year 2018-19. It is certified that all corrections / suggestions indicated
for Internal Assessment have been incorporated in the report. The Project report has been
approved as it satisfies the academic requirements in respect of Database Management
System with Mini Project Laboratory prescribed for the said Degree.

Signature of the Guide Signature of the HOD

Mrs. APASARA M B Dr. DAYANANDA P

Asst. Prof, Dept. of ISE, HOD & Assoc. Prof, Dept. of ISE
Mrs. Mamatha G JSSATE, BANGLORE
Asst. Prof, Dept. of ISE,
JSSATE, BANGLORE

Signature of Examiners
1.

2.

Page | 2
ABSTRACT

"Online Restaurant Management System" is web application to restaurant management. This

system provides service facility to restaurant and also to the customer. The services that are
provided is food ordering, table reservation by the customer through the system online,
customer information management and waiter information management, menu information
management and report. Main objective of the system 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 paper. Furthermore, this system is applicable at any time and anywhere for the
customer. During the development of Online Restaurant Management System, the language
being used is PHP. Software and hardware used are 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.
The Restaurant Management System is implemented to reduce the manual work and
enhances the accuracy of work in a restaurant.
This software has been made in a user-friendly interface. So that normal person can add and
delete the entries of customers and handle all the transactions easily.
The menu card consists of various food varieties available in the restaurant. Through the
ordering form, the customer can simply click and order the food. The messaging system tells
the supplier to supply the particular food. The billing system prepares the bill according to
the delivered food.

Page | 3
ACKNOWLEDGEMENT
The satisfaction and euphoria that accompany the successful completion of any task would be
incomplete without the mention of the people who made it possible. So, with gratitude, I
acknowledge all those whose guidance and encouragement crowned my effort with success.
First and foremost, I would like to express my sincere gratitude to His Holiness Jagadguru Sri
Sri Shivaratri Deshikendra Mahaswamiji for his divine blessings,without ehich the work
wouldn’t have been possible.
It’s my pleasure in thanking my principal Dr. Mrityunjaya V Latte, JSSATE, Bangalore, for
providing an opportunity to [resent this Project as a part of my curriculum in the partial
fulfillment of the degree.
I express my sincere gratitude to Dr. Dayananda, Assoc. Professor and Head of Department,
Information Science and Engineering for his cooperation and encouragement at all moments
of my approach.
It is my pleasant duty to place on record my deepest sense of gratitude to my guide
Mrs.Apsara M B, Asst. Professor, for the constant encouragement, valuable help and
assistance in every way possible.
I would like to thank all my teachers and non-teaching staff of ISE department for providing
me with their valuable guidance and for being there with me at all stages of my work.

SUSHMITHA S

T S THANYA GOWDA

Page | 4
Table of Contents
Chapter Title Page No.

Abstract……………………………………………………….…... 3

Acknowledgment……………………………………………....…. 4

Contents…………………………………………………….…...... 5

List of Figures…………………………………………………….. 7

Chapter 1 Introduction

1.1 Introduction of DBMS…………………………………………...…...8

1.2 History of DBMS……………….……………………………….

1.3 Problem Statement……………………………………….………. 9

Chapter 2

2.1 My SQL ………………………………………….. 10

2.2 PHP………………………………………... ………10
2.3 CSS………………………………………….………10
2.4 HTML…………………………………………... …11
2.5 Normalization……………………………………….11
2.5 Objectives…………………………………………...13
2.6Summary…………………………………………... 14

Page | 5
Chapter 3RequirementsSpecification

3.1 Software Specification………………………………………………….15

3.2 Hardware Specification………………………………………………….15

Chapter 4 System Design

4.1 Introduction……………………………………………. 16
4.2ER diagram…………………………………………….. 16
4.3Schema diagram………………………………………… 18
4.2 System flow diagram………………………………….. 20

Chapter 5 results and discussions…………

5.1 Create tables…………………………………………………….21

5.2 Snapshots of front end…………………………………………..24

5.3 Pseudo code……………………………………………………..28

5.4 Snapshots of Queries…………………………………………...29

5.5 Snapshots of Stored procedure…………………………………33

5.6 Snapshots of Triggers…………………………………………..34

Chapter6
Conclusion & Future Enhancements……………………35

References

Page | 6
LIST OFFIGURES
Figure No. Name of Figure Page No

1.1 Java Application Flow 03

3.1 ER Diagram 07

3.2 Schema Diagram 08

5.1-5.9 Frontend snap shots 19

5.10-5.16 Queries snapshots 29

5.17-5.18 Stored procedure snapshots 33

5.19-5.20 triggers snapshot 34

Page | 7
Chapter 1

1.1 Introduction of DBMS

A database management system (DBMS) refers to the technology for creating and
managing databases. Basically, DBMS is a software tool to organize (create, retrieve,
update and manage) data in a database.The main aim of a DBMS is to supply a way to
store up and retrieve database information that is both convenient and efficient. By
data, we mean known facts that can be recorded and that have embedded meaning.
Normally people use software such as DBASE IV or V, Microsoft ACCESS, or
EXCEL to store data in the form of database. A datum is a unit of data. Meaningful
data combined to form information. Hence, information is interpreted data – data
provided with semantics. MS. ACCESS is one of the most common examples of
database management software.The name indicates what database is. Database is one of
the important components for many applications and is used for storing a series of data
in a single set. In other words, it is a group / package of information that is put in order
so that it can be easily access, manage and update.

1.2 A History of Database Management Systems

The history of database management systems begins around the time that computers
began taking off.In the 1960's the first DBMS was developed at IBM and was
originally called IMS, written for the Apollo program.

Charles Bachman was an industrial researcher who developed a DBMS known as

the Integrated Database Store (IDS). The system was standardized by CODASYL.

Not to be left out, IBM created their own database system, known IMS, for that
of NASA's Apollo space program.Both of these are now known as the precursors of
navigational databases then in the 1970s, another change was coming.

Page | 8
1.3PROBLEM STATEMENT
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. In many popular restaurants,
waiters/waitresses tend to miss out on tables or customers’ calls during busy hours potentially
decreasing one’s clientele. While this is an ongoing issue, there is still no product that
drastically improves the communication between the servers and the customers in the current
market.
Since there are many drawbacks in maintaining the customers record manually Online
Restaurant Management System is developed to overcome the above drawbacks. This
project aims at providing quality food at affordable price and develops a user-friendly
portal so that the customers can order for food, reserve tables at any time. It also allows
the Restaurant’s staff to main customers details in a easy manner, and control all the
transaction process.
The system processes transaction and stores the resulting data. Reports will be
generated from these data which help the manager to make appropriate business
decisions for the restaurant. Online restaurant management system will develop to help
the restaurant administrator to manage restaurant management and for customer make
their online ordering and reservation table.
Nowadays, many restaurants manage their business by manual especially take customer
ordering. In traditional booking system, a customer has to go to restaurant or make a
phone call in order to get his meal reserved. Today, restaurant staff takes the customer
ordering by manual system with using paper.Restaurant management system puts the
order in a queue with specific priority according to time and quantity, and then a cook
is assigned for the specific order to complete it. Besides, the restaurant staff
information also by manual system kept use paper and this is difficult for restaurant
administrator to find staff information, probability missing the paper and difficult to
arrange the schedule.
This restaurant menu and management system will replace the paper waste, is more
maintainable, and allows for greater customer engagement. The problem confronting
the research is to determine the Documentation for online restaurant management
system.

Page | 9
Chapter 2

2.1 MySQL

MySQL is a fast, easy-to-use RDBMS being used for many small and big businesses. It
is developed, marketed and supported by MySQL AB, which is a Swedish company.
MySQL is becoming so popular because of many good reasons −It is released under an
open-source license.So, you have nothing to pay to use it, it is a very powerful program
in its own right and handles a large subset of the functionality of the most expensive
and powerful database packages.MySQL uses a standard form of the well-known SQL
data language. It works on many operating systems and with many languages including
PHP, PERL, C, C++, JAVA, etc and works very quickly and works well even with
large data sets.

2.2 PHP
PHP Hypertext Pre-processor is a scripting language that helps people make web pages more
interactive by allowing them to do more things. PHP code is run on the web server.
A website programmed with PHP can have pages that are password protected. A website with
no programming cannot do this without other complex things. Standard PHP file
extensions are: .php .php3 or .phtml, but a web server can be set up to use any extension.
Its structure was influenced by many languages like C, Perl, Java, C++, and even Python. It is
considered to be free software by the Free Software Foundation.

2.3 CSS

Cascading Style Sheets (CSS) is a style sheet language used for describing the presentation of
a document written in a mark-up language like HTML.CSS is a cornerstone technology of
the World Wide Web, alongside HTML and JavaScript.

CSS is designed to enable the separation of presentation and content,

including layout, colours, and fonts. This separation can improve content accessibility,
provide more flexibility and control in the specification of presentation characteristics, enable

Page | 10
multiple web pages to share formatting by specifying the relevant CSS in a separate CSS file,
and reduce complexity and repetition in the structural content.

Separation of formatting and content also makes it feasible to present the same markup page
in different styles for different rendering methods, such as on-screen, in print, by voice (via
speech-based browser or screen reader), and on Braille-basedtactile devices. CSS also has
rules for alternate formatting if the content is accessed on a mobile device.

The name cascading comes from the specified priority scheme to determine which style rule
applies if more than one rule matches a element. This cascading priority scheme is
predictable.

2.4 HTML

Hypertext Mark-up Language (HTML) is the standard mark-up language for creating web
pages and web applications. With Cascading Style Sheets (CSS) and Java Scripts, it forms a
triad of cornerstone technologies for the World Wide Web.

Web browser receives HTML documents from a web server or from local storage
and renders the documents into multimedia web pages. HTML describes the structure of a
web page semantically and originally included cues for the appearance of the document.

HTML can embed programs written in a scripting language such as JavaScript, which affects
the behaviour and content of web pages. Inclusion of CSS defines the look and layout of
content.

2.5 Normalization
Database normalization is a database schema design technique, by which an existing
schema is modified to minimize redundancy and dependency of data. Normalization
split a large table into smaller tables and define relationships between them to increases
the clarity in organizing data.

Database normalization types

First Normal Form (1NF)

Page | 11
 First normal form (1NF) deals with the `shape' of the record type
 A relation is in 1NF if, and only if, it contains no repeating attributes or groups of
attributes.
 Example:The Student table with the repeating group is not in 1NF

Second Normal Form (2NF)

 A relation is in 2NF if, and only if, it is in 1NF and every non-key attribute is
fully functionally dependent on the whole key.

Third Normal Form (3NF)

 A relation is in 3NF if, and only if, it is in 2NF and there are no transitive functional
dependencies
 Transitive functional dependencies arise:
 when one non-key attribute is functionally dependent on another non-key attribute:
 FD: non-key attribute -> non-key attribute
 and when there is redundancy in the database

Boyce-Codd Normal Form (BCNF)

 When a relation has more than one candidate key, anomalies may result even though
the relation is in 3NF.
 3NF does not deal satisfactorily with the case of a relation with overlapping candidate
keys
 i.e. composite candidate keys with at least one attribute in common.
 BCNF is based on the concept of a determinant.

Fourth Normal Form (4NF)

 Itis a normal form used in database normalization. Introduced by Ronald

Fagin in 1977, 4NF is the next level of normalization after Boyce–Codd
normal form (BCNF). Whereas the second, third, and Boyce–Codd normal

Page | 12
forms are concerned with functional dependencies, 4NF is concerned with a
more general type of dependency known as a multivalued dependencies

Fifth Normal Form (5NF)

 It is also known as project-join normal form (PJ/NF) is a level of database

normalization designed to reduce redundancy in relational databases
recording multi-valued facts by isolating semantically related multiple
relationships. A table is said to be in the 5NF if and only if every non-
trivial join dependency in that table is implied by the candidate keys.

2.6 Objectives
The general objectives of the systems to develop a reliable, convenient and accurate Ordering
System.

Online Restaurant Management has following specific objectives

 To develop a system that will surely satisfy the customer service.

 To design a system that is able to accommodate huge amount of orders at a time.

 To evaluate system’s performance and acceptability in terms of security, user-

friendliness, accuracy and reliability.

 To improve the communication between the client and the server and minimize the
time of ordering.

One of the main objectives of a Restaurant Management System is to ensure customer’s

satisfaction.Manual listing of orders by the waiters/waitresses may result to slow response in
customer’s service. Hence, if the restaurant uses the proposed system, manipulation of orders
to the customers would be so easy and quick and helps in choosing the desired menu.

 To automatically compute the bill.

The system will also automatically calculate and displays the final bill, so the bills will ready
to print without having any error because the information for that item is already inserted.

Page | 13
2.6 Summary

The chapter discussed before is an overview about the PHP, CSS and HTML
Application and MySQL, DBMS and its history. The scope of study and objectives of
the project are mentioned clearly. The organization of the report is been pictured to
increase the readability. Further, coming up chapters depicts the built-in functions used
in project source code and snapshots of the project.

Page | 14
Chapter 3

Requirement Specifications

2.1 SOFTWARE SPECIFICATION

• Operating System: Windows Vista/7/8/10

• Front End: PHP 5.6
• Rear End: MySQL
• Server: Apache server

2.2 HARDWARE SPECIFICATION

• Processor: x64 compatible processor with 2.00 GHz Clock Speed

• RAM: 512 MB or greater
• Hard Disk: 20 GB or grater
• Monitor: VGA/SVGA
• Keyboard: 104 keys standard
• Mouse: 2/3 button. Optical/Mechanical.

Page | 15
Chapter 4
System Design

4.1 Introduction

Systems design is the process or art of defining the architecture, components, modules,
interfaces, and data for a system to satisfy specified requirements. One could see it as
the application of systems theory to product development.

This Project is implemented using PHP, CSS and HTML which is proven to be a very
efficient tool in the field of programming. It is done under Windows7 platform. PHP is
used to implement the entire code. Interface to the program is provided with the help of
MySQL Database.

4.2 ER Diagram

An entity–relationship model or the ER Diagram describes inter-related things of interest in a

specific domain of knowledge. An ER model is composed of entity types and specifies
relationships that can exist between instances of those entity types

In software engineeringan ER model is commonly formed to represent things that a business

needs to remember in order to perform business processes. Consequently, the ER model
becomes an abstract data modelthat defines a data or information structure that can be
implemented in a database, typically a relational database.

Page | 16
Page | 17
4.3 Schema Diagram

The schema diagram of a database systemis its structure described in a formal

languagesupported by the database management system(DBMS). The formal definition
of a databaseschema is a set of formulas called integrity constraintsimposed on a
database.

The term "schema" refers to the organization of data as a blueprint of how the database
is constructed. These integrity constraints ensure compatibility between parts of the
schema. All constraints are expressible in the same language. A database can be
considered a structure in realization of the database language. The states of a created
conceptual schemaare transformed into an explicit mapping, the database schema. This
describes how real-world entities are modelledin the database.

Page | 18
Page | 19
4.4 System Flow Diagram

Login

Admin Customer

Staff information Order food

Order view View cart

Log out
Bill

Log out

Page | 20
Chapter 5
Results and Discussion
5.1 Create tables:

1. Table structure for table `billing_details`

CREATE TABLE `billing_details` (

`billing_id` int(10) NOT NULL primary key,
`member_id` int(15) NOT NULL,
`Street_Address` varchar(100) NOT NULL,
`P_O_Box_No` varchar(15) NOT NULL,
`City` text NOT NULL,
Foreign key(`member_id`),
Foreign key( `member_id’) references member(`member_id’),
`Mobile_No` varchar(15) NOT NULL)
ENGINE=MyISAM DEFAULT CHARSET=latin1;

2. Table structure for table `cart_details`

CREATE TABLE `cart_details` (

`cart_id` int(15) NOT NULL primary key,
`member_id` int(15) NOT NULL,
Foreign key(`member_id`,`quantity_id`),
Foreign key( `member_id’) references member(`member_id’),
`food_id` int(15) NOT NULL,
`quantity_id` int(15) NOT NULL,
Foreign key(`quantity_id`) references quantities(‘quantity_id’),
`total` float NOT NULL,
`flag` int(1) NOT NULL
) ENGINE=InnoDB DEFAULT CHARSET=latin1;

3. Table structure for table `categories`

CREATE TABLE `categories` (

`category_id` int(15) NOT NULL primary key,
`category_name` varchar(45) NOT NULL

Page | 21
) ENGINE=InnoDB DEFAULT CHARSET=latin1;

4.Table structure for table `food_details`

CREATE TABLE `food_details` (

`food_id` int(15) NOT NULL primary key,
`food_name` varchar(45) NOT NULL,
`food_description` text NOT NULL,
`food_price` float NOT NULL,
`food_category` int(15) NOT NULL
) ENGINE=InnoDB DEFAULT CHARSET=latin1;

5.Table structure for table `members`

CREATE TABLE `members` (

`member_id` int(11) UNSIGNED NOT NULL primary key,
`firstname` varchar(100) DEFAULT NULL,
`lastname` varchar(100) DEFAULT NULL,
`login` varchar(100) NOT NULL DEFAULT '',
`passwd` varchar(32) NOT NULL DEFAULT ''
) ENGINE=MyISAM DEFAULT CHARSET=latin1;

6. Table structure for table `orders_details`

CREATE TABLE `orders_details` (

`order_id` int(10) NOT NULL primary key,
`member_id` int(10) NOT NULL,
`billing_id` int(10) NOT NULL,
`cart_id` int(15) NOT NULL,
`delivery_date` date NOT NULL,
`StaffID` int(15) NOT NULL,
`flag` int(1) NOT NULL,
`time_stamp` time NOT NULL
Foreign key( `member_id`,`billing_id`,`cart_id`,`StaffID`),
Foreign key( `member_id’) references member(`member_id’),
Foreign key( `billing_id’) references billing_details(`billing_id’),
Foreign key( `cart_id’) references cart_details(`cart_id’),

Page | 22
Foreign key( `StaffID’) references staff(`staffID’)
) ENGINE=MyISAM DEFAULT CHARSET=latin1;

7.Table structure for table `pizza_admin`

CREATE TABLE `pizza_admin` (

`Admin_ID` int(45) NOT NULL primary key,
`Username` varchar(45) NOT NULL,
`Password` varchar(45) NOT NULL
) ENGINE=MyISAM DEFAULT CHARSET=latin1;

8. Table structure for table `quantities`

CREATE TABLE `quantities` (

`quantity_id` int(5) NOT NULL primary key,
`quantity_value` int(5) NOT NULL
) ENGINE=InnoDB DEFAULT CHARSET=latin1;

9. Table structure for table `reservations_details`

CREATE TABLE `reservations_details` (

`ReservationID` int(15) NOT NULL primary key,
`member_id` int(15) NOT NULL,
`table_id` int(5) NOT NULL,
Foreign key(`member_id`,`table_id`),
Foreign key( `member_id’) references member(`member_id’),
Foreign key( `table_id`) references tables(`table_id`),
`Reserve_Date` date NOT NULL,
`Reserve_Time` time NOT NULL,
`StaffID` int(15) NOT NULL,
`flag` int(1) NOT NULL,
`table_flag` int(1) NOT NULL
) ENGINE=MyISAM DEFAULT CHARSET=latin1;

10. Table structure for table `staff`

Page | 23
CREATE TABLE `staff` (
`StaffID` int(15) NOT NULL primary key,
`firstname` varchar(25) NOT NULL,
`lastname` varchar(25) NOT NULL,
`Street_Address` text NOT NULL,
`Mobile_Tel` varchar(20) NOT NULL
) ENGINE=MyISAM DEFAULT CHARSET=latin1;

11. Table structure for table `tables`

CREATE TABLE `tables` (

`table_id` int(5) NOT NULL primary key,
`table_name` varchar(45) NOT NULL
) ENGINE=InnoDB DEFAULT CHARSET=latin1;
5.2 Snapshots:

Loginpage

Login pageFig 5.1

Page | 24
Foodmenu:

Food menu Fig 5.2

CONTACT PAGE:

Contact PageFig 5.3

ADMINLOGIN:

Page | 25
Adminlogin Fig5.5

ADMINISTROR CONTROL PANEL:

Admin control panel Fig 5.5

ORDER HISTORY:

Orderhistory Fig5.6

Page | 26
SHOPPINF CART:

Shoppingcart fig5.7

RESERVIATION:

Reservingtable Fig5.8

LOGIN FAILED:

Loginfailed Fig5.9

Page | 27
5.3 Pseudo Code
Customer login
GET Email
GETPassword
IF (Email == EnteredEmail&&Password == EnteredPassword)THEN
Login Successful
ELSE
Login Failed
ENDIF

Admin Login Page

GET Username
IF (Username == EnteredUsername &&Password == EnteredPassword)THEN
Login Successful
ELSE
Login Failed
ENDIF

Customer Registration Page

CLASS Registration_form
Form_Entry()
GET Firstname
GET Lastname
GET Email
GET Password
GET Securityanswer
IF sumbitted
IF Email already exists in database THEN
Prompt customer for another email
ELSE
IF fields validated THEN
Create the account
Save the record to database

Page | 28
Call Form_Show() method
ELSE
Call Form_Entry() method
END IF
END IF
END IF
5.2 Snapshots of queries
FOOD MENU:

foodmenu fig 5.10

CART:

Cart fig5.11

Page | 29
UPDATE QUANTITY:

Update-quantity fig 5.12

ORDER:

Order fig 5.13

Page | 30
MEMBER :

Member fig 5.14

BILLING:

Billing fig5.15

Page | 31
RESERVATION:

Reservation fig 5.16

5.3 Snapshots of stored procedure

Figure 5.17

Page | 32
Fig 5.18

5.3 Snapshots of triggers

Fig 5.19

Page | 33
Fig 5.20

Page | 34
CHAPTER 6
Conclusion and References

6.1 Conclusion
The Project entitled “Online Restaurant Management System” has been proposed to be
implemneting to replace manual system.
The developed system accomplish all the objectives stated for the to change the
system.The customers can add any number of items to the cart from any of the available
food categories by simply clicking the add to cart button for each item. Once item is
added to cart, customer is presented with detailed order to review or continue shopping.
Outputs produced seem to satisfy all the customers but it will definitely take ato look
forwarded for the real consequences the new system could produce.
This projet is made user friendly by the use of visual basics enabling the customers to
interact easily with the database.
It also enables the platform to serve the needs of emerging information technology
trends and needs.

Page | 35
6.2 References
Book References
1. Database systems Models , Languags, Design and Application Programming,
RamezElmasri and Shamkant B .Navathe, 7th Edition , 2017, Pearson.
2. Database management systems,Ramkrsihnan, and Gehrke, 3rd Edition ,2014,
McGraw Hill.

Web References

1.w3 schools
2.stack overflow

Page | 36