Authorized Learning Center (Code: - 1537)

Collage for Professional Studies

Opp. Maitidevi Temple, Kathmandu Nepal

Restaurant Management System

By
Sonam Bomjan Tamang
Roll no: 1308007018
A project report under the guidance of Ravi Rauniyars submitted in the partial
fulfillment of the
Requirements of the B.Sc.IT 3rd Semester of Sikkim Manipal University, DDE
INDIA
Sikkim Manipal University
Directorate of Distance Education
Manipal, India
Date of Submission: 19th July 2016

Contents
INTRODUCTION.................................................................................................................1
Specific and Scope................................................................................................................2
Theoretical Background........................................................................................................3
Statement about the problem.................................................................................................4
Feasibility Study....................................................................................................................6
System Planning....................................................................................................................7
Methodology Adopted...........................................................................................................8
Hardware and Software.......................................................................................................10
Life cycle of the Project.....................................................................................................11
ER-Diagram:.......................................................................................................................12
DFD (Data flow Diagram)..................................................................................................13
Flow Chart...........................................................................................................................15
Testing.................................................................................................................................16
Data Dictionary...................................................................................................................18
Conclusion...........................................................................................................................20

INTRODUCTION
A Restaurant management system is a application to manage restaurant data. Restaurant
Management system deals with all kind of restaurant details, menu details, order details and
other resource related details too. It tracks all the details of a restaurant from the day to day
which can be used for all reporting purpose, tracking and all these will be available for
future references too . Restaurant Management System is an initiation to keep the tracking
of order, new product, users, contact and members. In traditional periods to till date in
some Restaurants, there is or has been no proper method/mechanism to keep the records of
data. So, with this project, it will help small restaurants to manage the records and track the
employees. In the present context, details and tracking of orders and new members are
recorded. However, lots of improvements are still in approach but still are good initiation
for the cause of small restaurants in regards of feasibility
Restaurant Management System is done in PHP and Web Services Technologies,
allowing the system to be run locally or in distributed mode. Its just an initiation on the
subject of Restaurant management System but the scope of the project is very large and lots
of features can be added to the project.

Specific and Scope

The objectives of the project can be highlighted in the following points:
1.

To provide easy to keep the record of employee and members

2.

To provide an easy to use environment that can be used by employee or members

with or without any technical skills

3.

To automate the system of restaurant management

4.

To provide a structured classification of information along with effective navigation

5.

To provide consistent and easily managed security and authentication

The software developed during the course of this project, has a wide scope keeping in mind
the benefit users can obtain from it. The software is a concise and complete application that meets
the demands of users for whom maintaining and managing of restaurant record is importance.
This software provides that platform to the user, enabling them to maintain their information and
members in a simple yet efficient manner. Also, since this software is not client-centric, almost
any small restaurant can adapt it to their own workflow and use it to their benefits

Theoretical Background
2

Before developing the application itself, the essential elements, designs and table structures were
all theoretically designed on paper
The application has 8 main tables which are:
1. Admin
2. Members Info
3. Product
4. Order
5. Contact
6. Category
7. Menu
8. Register
It also has two mapping tables which are:
1. Posts-Tags Map
2. Users-Roles Map
The application has two main sections viz. the Admin section and the visitor section. The admin
section contains all the management aspects of the application while the visitor section is the portal
through which student view the profile created with the help of this application
The admin section consists of modules for managingmembers info, order info, add product, add
catogary and add admin.

Statement about the problem

In the current context, an increasing number of restaurants have web sites which they use to
display information and content regarding their organizational activities. As the amount of
content increases, the problem also increases and so the requirement of an effective tool to
manage and facilitate the work is necessary. Some websites such as news sites and blogs
may require updating their content frequently and it is not possible for a web developer to
do so manually each time a certain content needs to be updated or a new one is to be added.
Also, the content generators might be people who have little or no technical knowledge and
an effective platform is required for them to focus on the content of the website rather than
the coding aspects. Thus, the need of an effective student management system is evident.

Technical Problem
The design is simple but on testing, there are software problems and on designing, code problems.
Cost Problem
It might take budget than I expected.
Performance Problem
It also does not fulfill the needs of all customers as they have desired.
Schedule Problem
Project cannot be completed within the specified time.
Limitations
The Restaurant Management System is a huge field so all the aspects of field cannot be included
in the software. It has some limitations and they are listed below:

The automated system doesnt hold record of multiple restaurants.

There can be a limit in the size of the store according to the available space.

The hardware and software specification other than provided can cause improper functioning of
the system.

Feasibility Study
The feasibility study is done when the final decision is taken about the development of the system.
Once we finish the decision analysis phase we do feasibility study to determine whether at the
given condition the project will be successful or not. Both the parties, the user of the system and
the developer do the feasibility analysis.
Operational feasibility
It generally defines the whether the solution will fulfill the requirements of the user. The proposed
software is easy to operate. There is not much training required for the operation of the software.
It will change the working style of the user completely to a larger extent.
Economic feasibility
It is related with the issue of the costeffectiveness of the system. It includes all the cost that will
be incurred for the resources that is used to develop the system. For the purpose of economic
feasibility we have used cost benefit analysis techniques. The required resources such as hardware
(CPU, storage devices, printer, floppy disks, etc) are already present with the user as well as with
the company so the cost of computer usage is minimum. Only the overhead cost associated with
maintenance can be incurred. In consideration with these factors the project is economically
feasible.
Risk Management
Risk analysis and Management are the series of steps that help a software development team to
understand and manage the uncertainty. A risk is a potential problem that might occur or might not
occur. It is always nice to identify it, assess its probability of occurrence, estimate its impact and
establish a contingency. We do risk management because we want our software project to be
successful.

System Planning
The Gantt chart followed during the development of this project is given below
Timeline in weeks
Totalweeks
Tasks

july

August

Proposal
presentatio
n
Feasibility study
System
requiremen
ts
specificatio
ns
Design
Coding
Testing
Documentation

September

Methodology Adopted
To achieve the functional requirement there are many methodologies that can be used like the
waterfall, rational prototype, increment development, and rapid application development and spiral
models. The methodologies to be used depend on the kind of software to be developed.
This project follows the rules of the waterfall model. Simple image of classic waterfall model is
given below:
Waterfall
The waterfall model is a sequential development approach, in which development is seen as
flowing downwards (like a waterfall) through the phase of requirement analysis, design,
implementation, testing (validation), integration and maintainance.

Feasibility study
Requirement

analysis
Design

Coding
Testing

Feasibility
This is the first stage of project development. In this stage I decided whether the project would
proceed or not. If project is to proceed, I had to study and produce plan and budget estimates for
the further stages of development.

Analysis
During this phase I did research regarding the project which included brainstorming about the
software, what it is going to be and what purpose it is going to fulfill.

Design
During this phase I defined the overall structure of the software. Logically I had to design the
whole project and see its effect.

Implementation
In this phase I translated the design into code. I used the and C# programming language for the
frontend and the Microsoft SQL Server database for the backend.

Testing
During this phase, to ensure the completeness and proper functioning of project I tested the
application using several testing techniques.

Maintenance
Maintenance and management is needed to ensure that the system will continue to perform as
desired.

Hardware and Software

Hardware
Processor Name:

Pentium 4 or Above

Processor Speed:

3.2 GHz

RAM:

512 MB

Hard Disk Capacity: 250 GB

Display Device:

14 to 19 Inch Monitor

Keyboard Type:

PS2 or USB

Mouse Type:

PS2 or USB

Software

Windows 7/8/10(operating system)

Apache Server
Xampp
MySQL
Google Chrome (browser)
PHP (Hypertext Preprosessor)

10

Life cycle of the Project

ER Diagram
Entity Relationship(ER) Diagrams illustrate the logical structure of databases. An Entity
Relationship Diagram is a piece of data-an object or concept about which data is stored.
Relationship

Entity

Attribute

Data Flow

There are three types of relationships between entities:

One-to-one (1 to 1): one instance of an entity (A) is associated with one other instance of another
entity (B).
One-to-many (1 to n): one instance of an entity (A) is associated with zero, one or many instances
of another entity (B), but for one instance of entity B there is only one instance of entity A.
For example, a single post can have more than one comments associated with it but a
comment can belong to only one post.
Many-to-many (n to n): one instance of an entity (A) is associated with one, zero or many
instances of another entity (B), and one instance of entity B is associated with one, zero or
many instances of entity A. For example, a post can have more than one tags associated
with it. Similarly, a tag can be associated with more than one post.

11

ER-Diagram:
catogory
name

des

catogory

Image location
id

location

12

DFD (Data flow Diagram)

Data Flow Diagram
A Data Flow Diagram (DFD) is a diagram that describes the flow of data and the processes that
change or transform data throughout a system. Its a structured analysis and design tool that can be
used for flowcharting in place of, or in association with, information oriented and process oriented
system flowcharts. When analysts prepare the Data Flow Diagram, they specify the user needs at a
level of detail that virtually determines the information flow into and out of the system and the
required data resources. This network is constructed by using a set of symbols that do not imply a
physical implementation. The Data Flow Diagram reviews the current physical system, prepares
input and output specification, specifies the implementation plan etc.
Four basic symbols are used to construct data flow diagrams. They are symbols that represent data
source, data flows, and data transformations and data storage. The points at which data are
transformed are represented by enclosed figures, usually circles, which are called nodes.

Data Flow Diagram Symbols:Process

Data Flow

Input/output

Decision Making

13

Register new
members

Member Form
(Submit/Reset)

Member Log In

Admin Log In

Username and
password

Insert/update/delete
Add new records etc.

Fig: DFD diagram of the project.

14

Database

Flow Chart

Start

Username

Password

User type

No

Verify

User management

Product

Yes

Admin portal

Catogory

15

Contact
Members prtal
Order

Manu

Log out

Testing
Testing Techniques
The following two testing techniques were used during the course of the project:
Black Box Testing:
In this method, the internal workings of the item being tested are not known. It is also known as
functional testing because it only concerns with testing if the application functions as expected
rather than how it does so. The tester does not ever examine the programming code and does not
need any further knowledge of the program other than its specifications.
White Box Testing:
In this method, an explicit knowledge of the internal workings of the item being tested are used
to select the test data. Unlike black box testing, white box testing uses specific knowledge of
programming code to examine outputs. The test is accurate only if the tester knows what the
program is supposed to do. It is also known as glass-box testing.

16

Testing Cases
Following are the test cases plan for this software:
Test for data acceptance
Data sampling
Test for the compatibility
(a)Test case 1:
Test objectives:
Output :

Test for valid credentials

Valid: Allowed access to the system

Invalid: program terminates

Result :

Valid: enter the system

Invalid: Program terminates

Conclusion

Valid input gives output

(b)Test case 2:
Test objectives: Test for acceptance of data
Test Data

Valid: Entered some valid data in the key fields

Invalid: Display error messages

Output :

Valid: Entry accepted

Invalid: Entry discarded

Result :

Valid: Valid data entered easily into the database

Invalid: Invalid data could not be entered

Conclusion

Both the valid and invalid data gave desired result

(c)Test case 3:
Test objectives: Testing the system using sample data
Test data

Valid: Prepared 10 sets of valid posts

Output :

The valid data is easily processed as expected but

the invalid data is rejected by the system.

(d)Test case 4:
17

The application should be compatible across all the systems and environment as originally
planned during the development of the application

Data Dictionary
The following tables give the description of all the tables that are used to hold the data in
the application:

Table for register and login

Field Name
ID
Name
Password
usertype
Phone
Email
Address

Data type
varchar(50)
varchar(50)
varchar(50)
varchar(50)
Int(32)
varchar(50)
Varchar(50)

Table for order:

18

Field Name
ID
UserID
ProdutId
quantity
Delivered

Data type
varchar(50)
varchar(50)
varchar(50)
Int(45)
varchar(32)

Table for product :

Field Name
Id
Product name
description
Image location
Price
category

Data type
int(32)
varchar(50)
varchar(50)
Varchar(50)
Int(50)
varchar(50)

Table for contact:

Field Name
Id
Name
Email
message

Data type
int(32)
cahr(32)
Char(50)
Char(250)

Table for category:

19

Field Name
Id
Name
Description

Data type
int(32)
Char(50)
Char(50)

Conclusion
The project aims to develop a simple and easy-to-use restaurant management system for
easy-to-use web based administration panel. It can be used by an individual or an
organization that provides produect, orders, members etc. Its main purpose is to automate
the process of restaurant management. This application is primarily focused on the easiness
of managing records pf restaurant so that the users can focus primarily on their members,
procduct or in the orders without having to worry about the technical aspects of
maintaining a website.From a proper analysis of positive points and constraints on the
component, it can be safely concluded that the product is a highly efficient GUI based

20

component. This application is working properly and meeting to all user requirements. This
component can be easily plugged in many other systems.

21