Restaurant management system

Restaurant Management

1
 Restaurant management system

Phase 1:
Feasibility Study

2
 Restaurant management system

FEASIBILITY STUDY

 MOTIVATION
Taking the scenario of “ coffee shop” . In this particular situation first customer
have to stand in queue to place his order, second they to checkout menu to choose
and order and have to wait till it get delivered. Incase if he needs anything else or
and have to order again he/she have to repeat the whole process of placing it order
again. So chain of huge coffee house “ TEA –HALT” all over country having
few errors in their system, while billing , providing services, in placing orders,
showing latest offers and coupons. They proposed a new idea to develop a new
and better version of their system with new features and developing into an
application for smartphones and tablets.

 INPUT AND ASSUMPTION

This system takes the following input

 Experienced workers, chefs.

 Best quality material.
 Project management system
 Budgeting
 Costing and forecasting
 Production
 Technology:

3
 Restaurant management system

 PROBLEM DEFINATION

Under this, following are the various problems that are faced so often-

 Many a times, we have to wait in long queues for the orders, which in
return waste a lot of time and greater level of patience.
 Can miss some offers etc.
 There are many human errors while dealing with the information manually.
 There could be various types of intangible benefits on account of
automation. These could include increased customer satisfaction,
improvement in product quality better decision making timeliness of
information, expediting activities, improved accuracy of operations.

 OBJECTIVE

The software we are proposing have many enhance features then

previous software, as going through pervious software lack of many features
are their which cause lacking behind for providing good services.

 Menu Structure

 Membership Levels

 Point

 Metric Types
 Qualification Metrics
 Points Allocation

 Points Purchase
 Rewards on every purchase

4
 Restaurant management system

 Food items display

 Order placement
 Billing

5
 Restaurant management system

Phase 2:
Software
Requirement
Specifications
(SRS)

6
 Restaurant management system

Index

1. Introduction……………………………………………………...8

1.1 Purpose…………………………………………………….8
1.2 Scope………………………………………………………8
1.3 Definitions, Abbreviations, and Acronyms……………….8
1.4 References…………………………………………………9
1.5 Overview………………………………………………….9

2. Overall Description………………………………………………9

2.1 Product Perspective………………………………………..9

2.2 Product Function…………………………………………..10
2.3 User Characteristics……………………………………….11
2.4 Principal Actor…………………………………………….12
2.5 General Constraints……………………………………….12

3. Specific Requirements…………………………………………..12

3.1 Functional Requirement…………………………………..12

3.2 Performance……………………………………………….15
3.3 Design Constraint………………………………………….15

4. Future Extensions…………………………………………………….16











7
 Restaurant management system

1. INTRODUCTION

1.1 Purpose
The purpose of the project is to manage a restaurant or coffee house
process for better and accurate alignment. It takes less human efforts. Reduce
paper usage. It also reduces billing mistakes. This software will not only save time
but is very easy to use.

1.2 Scope
In-scope

 Information regarding food menu.

 Online ordering
 Digital payment system
 Personal account facility
 Seat availability
 Statement
 Fire alarms

Out-scope

 Confusion regarding menu

 Cash payment

1.3 Definitions, Abbreviations and Acronyms

Definitions-

 Ordering- selecting required food from given choices.

 Alignment- deal or setup that is fixed.

8
 Restaurant management system

Abbreviation-

 Coffee house- ch
 Restaurant - restro
 Information- info

1.4 Reference-

www.studyhospitality.com

www.tradingfundas.com

1.5 Overview-

The rest of the SRS is organized as follows:

Section 2 gives an overall description of the software. It determines the level of

proficiency which is expected from the user, some general constraint while
making this software and making some assumptions and dependencies.

Section 3 gives specific requirements which the software is expected to deliver.

Functional requirements, performance requirements and some design constraints
are also given.

Section 4 gives some possible future extensions of the system.

9
 Restaurant management system

2. Overall description
2.1 Product perspective

Restaurant management software is aimed towards providing the clients

the best facilities possible which is free from all sorts of formalities and time
consuming methodology as it is the stand-alone product which gives all the
required information and solutions regarding the problems at a place. It provides
high quality work regarding all aspects related to the Hospitality work and follow
one’s requirements.

2.2 Product functions

Classes of use case Use case Description
Installation It installs the software.
use case related to
installation

 Login id/Guest Login into the website.

use case related to system
authorization.
 Create password Create your account password.

Information about the employees

 Employee. like their names, contact details,
etc.

 Time period. Time required for the completion

of the project.

10
 Restaurant management system

 Material quality quality test of the materials

and quantity. provided by the clients by
themselves.
Use case related to menu
and offers. Quantity of the food supplements
required.

 Overview 3D model of the project to show

the proper design forum to the
clients.

 Contact details Contact details of the company.

Use case of the

information related to Raw materials Name and contact details of the
placing order seller who provides high quality
food supplements.

Use case related to online Payment  Payment through :-

payment  Online bank transfer
 Debit card/Credit card
 Cash card
 Mobile payment

11
 Restaurant management system

2.3 User Characteristics

 User should know how to operate a computer system.

 User/ Admin should have a proper internet connection.
 He should beware of malwares, virus and others aspects which can harm
the computer system.
 User should be familiar with user interfaces of whole registration process.

2.4 Principal actor

 For Database :- system administration

 For using the software:- client

2.5 General Constraints

 We require a computer system with internet connection .

3. Specific Requirements

3.1 Functional requirements

Functional requirements focus on what the system does geared towards the
production of a business result or deliverable, we describe the function
requirements using the various use cases:

12
 Restaurant management system

Use case related to installation :

Use case 1 :Installation

Primary actor : Administrator

Pre requisites : Computer system, internet connection

Purpose : for installing the CMS software

Function installation input : software installation play store or any

other means.

Function installation operation : describes the process involved in

the installation.

Function installation output : he CMS software will be installed

in the machine.

Main scenario :

o Begin with the installation process by double clicking on the

setup.
o Read the license agreement, accept it to continue with the setup.
o Select the location where the software is to be installed.
o Finally install the software by clicking the INSTALL and then
click FINISH.

Use case related to system authorization (optional)

Use case 2: login id and password

Primary actor : administrator and client

Re requisites : internet connection, computer system

Purpose : for providing access to the client.

Function authorization input and operation : describes the

process involved in the checking the login id and password.

13
 Restaurant management system

Function authorization output : the user will get access to use the
software.

Main scenario :

o Enter the login id and password.

o Click ok button.
o If the login id and password are correct then will enter into the
CMS software.

Use case related to information of menu and offers

Use case 3 : information

Primary actor : administrator

Pre requisites : internet connection, user can have a valid account

or can access through guest account.

Purpose : providing menu and offer regarding food and beverages.

Function information input : offers and coupons, food quantity

and cost.

Function information operation : provides the information related

to all the aspects of the menu.

Function information output : the client will get desired

information.

Main scenario:

o Open the tablets.

o Sign in by the verified user’s account/ guest user.
o Get the required information.

14
 Restaurant management system

Use case related to placing order

Use case 4: place order

Primary actor : customer

Pre requisites : internet connection, client’s account or guest

account.

Purpose : placing order

Function placing order input : desired order will be placed.

Function placing order operation : placing of the order is done by

the customer.

Function placing order output : order has been placed and is

delivered.

Main scenario

o Open the tablets.

o Sign in by the user account or guest account.
o Click on the food beverages section and place order.

Use case for online payment

Use case 5 : online payment

Primary actor : administrator

Pre requisites : client’s bank account

Purpose : providing online payment facilities

Function online payment input : clients account details

Function online payment operation :

Function online payment output : receipt for paid money.

Main scenario :

o Open the tablets.

15
 Restaurant management system

o Sign in by the verified user’s account.

o Select the payment option on the tab.
o Select the option for payment accordingly.

3.2 Performance Requirements

 Requires internet connection
 JAVA or C++ enabled web browser
 JAVA or C++ runtime environmental
 MS-SQL Server
 ODBC Connectivity Driver
 80 GB Hard Disk at server
 Minimum 2 GB RAM

3.3 Design Constraint

 JAVA or C++ as front-end
 MS-SQL Server at back level
 ODBC Connectivity Driver
 JAVA or C++ enabled web browser
 UML for designing

4. Future Extentions

 Mobile application- Customer can havebetter useage more handy for

people and more market of the firm.
 Minimal use of humans resources- We can make less human power at any
retro.
 Cash -taking cash by the system itself.

16
 Restaurant management system



Phase 3
Data Flow Diagram

17