PROJECT TITLE:

RESTAURANT MANAGEMENT SYSTEM

FROM GROUP 4

SECTION “A”
CHAPTER ONE CHAPTR TWO
• Introduction ANALYSIS
• Background Requirement gathering analysis…
• Mission Problem description/analysis
• Vision Requirement analysis
• Goal Requirement modeling
• Statements of the problem Essential use case diagram
• Objectives Description of essential use case diagram
• Limitation of the project Proposed solution
• Methodology Alternative solution
• data collection Feasibility study
• System development tools Requirement analysis for new system
• Requirement analysis System use case diagram for new system
Description of system use case diagram for
Con’t CHAPTER THREE
• Sequence diagram for new system DESIGN
• Activity diagram for new system Collaboration diagram
Deployment diagram
INTRODUCTION
BACKGROUND TO THE STUDY
• RMS Restaurant Management Systems are the crucial technology
components that enable a single outlet or enterprise to better serve its
customers and aid employees with food and beverage transactions and
controls.
• Since the emergence of electronic computer, decision making and
processing of information has been very easy.
• Data can now be stored on computer in a considerable
low space and retrieved
within a short period of time compared with the manual method which is
tedious and time-consuming as the size of the file increases.
• Restaurant Management System is a software system where the
management of entire hotel is computerized.
Con’t
• The application stores customer record and daily activities performed
in the hotel such as customer details, reservation details, creating a
new room, vacating the rooms, etc.
Mission
shall provide an access to increase customers productivity
Increase informational management for the user in the future.
• The restaurant is established for:-
• In order to give best access for the community.
• Enabling customers to get full access when they used..
 Vision
• To create an environment that will promote a competitive restaurant
management skills that will initiate corporate hospitality experience
sustainable for tourism operation and customer relations.
• To Coordinate work activities that will have various actors – Host, Waiter,
Cook, Busboy and Manager.
Goal
The main goal of the project is:-
o To decrease service time, kitchen bar, office, host stand, order accuracy e.t.c.
o To provide facility to give order.
o Users can have many choices of fast foods, softdrinks, milk shake, and bevangers of
their prizes and at their finger tips.
 STATEMENT OF PROBLEM
• There are many inherent problems with using the old method of
recording restaurant check-in information.
• Such problems can occur as check papers and information sent to the
wrong place.
Difficulty in location of guest files
Calculation is difficulty
Large storage space the physical files occupies too much space
Human and computational errors
Difficulty in data searching
Difficulty in data entry
Unnecessary duplication of data
Retrieval of guest records is extremely difficult
Guest records are extremely difficult to modify
 Objectives:
• Restaurant Management System is one of the leading software for
complete management of your restaurant; it can manage the reception,
restaurant, inventory and accounts excellently.
• The hotel management software provides all kinds of record keeping
feature required in a hotel like day books, daily business book,
Preparation of profit/loss and many more automatically.
General Objectives
The System helps to increase productivity and informational management
for the user.
Computerize data management in the restaurant
Enable fast and easy retrieval of guest records and data for fast reference
activities
con’t
• The system is developed specially to meet the needs of restaurant
companies:-
Room activities
Admission of a New Customer
Creating an account for new staff
Delete existing account
Lodge in / Lodge Out
Check room if it is currently in use
Assign properties to room according to new update of the room
Assign a room according to customers demand
Checkout of a computer and releasing the room
 Specific Objectives
To be able to get work faster
To be able to manage fast access to the guest files
To be able to provides better data management facilities
To be able to easy update of the guest records
To be able to provides security measures to access to the hotel’s information
lowering data security threats
To be able to reduction of data entry and processing errors
To be able to reduce paper use at the restaurant
Significant of the project
• The proposed system is to facilitate easy management and administration of
restaurant with capabilities to do Booking or reservations of the rooms,
Cancellation of the rooms, Cash billing, ordering of food, Adding new staff,
Generate bill, Review of report, etc. using the computerized restaurant
management software
 Limitation of project
• They are not allowed to change data information such as:-
 Room types
 Discount type and
 Administrator password

Methodology
 To ensure that our project is in par with our client needs, we used the
waterfall model approach in developing the systems.
 The first process of the model is data gathering.
 We designed the questionnaire what we should ask our clients.
 We also prepared other requirements in order toget permission to
interview our clients.
 Con’t
 After gathering all of the information from our clientswe proceeded with
the next step which is analyzing of data and problem solving.
 In here we began conceptualizing the components our system needed
such as inputting name and creating log in log out system.
 After conceptualizing all of the elements we need in creating our system
we proceed to the next step which is implementing requirements.
 In here we decide what applications we need in developing the system.
Data Collection Method
Data collection methods or fact gathering techniques which are used
while gathering the information about Hotel Management System (HMS),
they are:-
Interviewing
Record inspection and observation
 REQUIREMENT ANALYSIS
• HARDWARE REQUIREMENT
PIV 2.8 GHz Processor and Above
RAM 512MB and Above
HDD 40 GB Hard Disk Space and Above
• SOFTWARE REQUIREMENT
WINDOWS OS (XP / 2000 / 2000 Server / 2003 Server)
Visual Studio .Net 2008 Enterprise Edition
Internet Information Server 5.0 (IIS)
Visual Studio .Net Framework (Minimal for Deployment
 CHAPTER TWO
ANALYSIS
• Requirement gathering and analysis
Analysis of the existing system and requirement gathering are the main activities that
must be undertaken to have a clear idea of the existing system.
Requirements are gathered using the traditional methods such as interview, document
analysis, and physical observation.
Interview questions with diversified of seven questions have been used to gather
information (see appendix A: Interview questions) with the department manager,
different staff and customers to know the problem of the existing system as well as its
strong side.
Document analysis: we analysis their document or forms that contains different
information about housing that filled by customers for rent and sell.
Observation: the team will conduct observation around the offices area to know the
overall activities of the agencies.
Problem Description or Analysis for Existing
System
• It is limited to a single system.
• It is less user-friendly.
• The present system is very less secure.
• It is unable to generate different kinds of report.
• It doesn’t have the mail and file upload feature.
Requirement analysis
Functional requirements
o Computer hardware, Software and
o Skilled human power to create fast, accurate, efficient and effective
information system
Non Functional requirements
• Non-functional requirement means necessities of the new system
that are not directly related to the functionality of the new system.
a) Performance characteristics
 At this time customer needs fast and efficient service.
 So our performance takes into consideration all needs of the clients.
 the system run on a personal computer and it is available until there is electric power.
b) Quality issues
 The system is reliable.
 System portability: ability to move the software to different computer.
 Compatibility: compatible with standard Ms.
c) Documentation
 The system has to be well documented so that it calls service as a good guide one for
further references to manage it.
 Requirement Modeling
• A requirements model helps us for the project:
Focus on the system's external behavior, separately from its internal design.
Describe the users' and stakeholders' needs.
Reduce gaps and inconsistencies in the requirements.
Reduce the work needed to respond to requirements changes.
Plan the order in which features will be developed.
Common Tasks
• You can create several different views of the users' requirements. Each view
provides a particular type of information. When you create these views, it is best
to move frequently from one to another.
 Con’t
Diagram or document What it describes in a requirements
model

Who uses the system and what they do with it.

Use case diagram

Glossary of types that are used to describe the

Conceptual class diagram
requirements; the types visible at the system's interface.

Flow of work and information between activities

Activity diagram performed by users and system or its parts.

Sequence of interactions between users and system or its

Sequence diagram
parts. An alternative view to the activity diagram.
 Describing how your system is used
• Create use case diagrams to describe who uses the system, and what they
use it for.
• A use case represents a goal of a user of the system
• As an example, an online meal selling system must allow customers to
choose items from a menu, and must allow the providing restaurants to
update the menu. You can summarize this in a use case diagram:
• You can also show how a use case is composed of smaller cases. For
example, ordering a meal is part of buying a meal, which also includes
payment and delivery:

<<sub system>>
update menu

order a meal

buy a meal pay for meal *

* *
*
customer deliver meal restaurant
*
 Essential use case diagram
• A use case describes a sequence of actions that provide something of
measurable value to an actor. A use case is made up of a set of scenarios.
• Each scenario is a sequence of steps that encompass an interaction between a
user/actor and a system.
• The use case brings scenarios together that accomplish a specific goal of the
user.
 Use case diagrams contain one of the following artifacts:
• Use cases: describes a sequence of actions that provide something of
measurable value to an actor.
• Actors: an actor is a person, organization, or external system that plays a role
in one or more interactions with your system.
Con’t
• Associations: associations between actors and use cases are indicated in
use case diagrams by solid lines.
• System boundary boxes (optional): you can draw a rectangle around the
use cases, called the system boundary box, used to indicate the scope of
our system.
• Packages (optional): packages are UML constructs that enable you to
organize model elements such as use cases into groups.
 System
-
receive order << extend >>
* * order food order wine
* - *
place order
waiter *
-
confirm order
* *
serve food cook food * *

<< extend >> { if wine was ordered }

chef
serve wine steal food
*

steal wine *
** *
* *

extend steal clients *

- pay << >> { if wine was served } cook

*
*
* Eat food *

client * - facilitate payment steal payment

* << extend >>
- accept payment * pay for food
*
pay for wine

cashier
 Description Of Essential Use Case Diagram
• Use Case diagram for Management System is shown above. The various
participants of the same are detailed below:-
Actors: -waiter, clients’, cashier and staff
The corresponding use cases for these actors are:-
Reception(waiter): Check Room Availability, Book The Room, , Receive
Order
Client(Customer): Ask For Room, Make Payment, Check-In, Check-,
Place Order For Food/Tea
Chef(staff): confirm order, cook food
cashier: Maintain Accounts, Generate Reports, accept payment
 PROPOSED SYSTEM SOLUTION:-
• The development of the new system contains the following activities, which
try to automate the entire process keeping in view of the integration
approach.
User friendliness is provided in the application with various controls.
The system makes the overall project management much easier and flexible.
It can be accessed over the Internet.
Various classes have been used to provide file upload and mail features.
There is no risk of data mismanagement at any level while the project development is
under process.
MODULES:-
o Hotel Master
o Account Master
o Inventory Master
 Alternative Solution
• The main thing is to identify the main features that involved in the
alternative system. The advantages of the proposed or current system
over the existing system are as follows:-
User friendly interface
Less error
More capacity to customers
More quick facility
Feasibility study
 Feasibility of the project aim is to objectively and really uncover the
strength and weakness of the existing business.
 TECHNICAL FEASIBILITY:
• The system developers understand the scope, objectives including
specific objectives and limitations of the proposed system well and the
users have technical capability to use this system. As a result the owner
of the restaurant develop the computerized system successfully within
proposed resources (budget, time, etc.), so the project is technically
feasible.
Economic feasibility
 The system to be developed is economically feasible and the benefit is
outweighing the cost. Since this project already computerizes the existing
system, by now the reduction of cost for materials used in manual
operation becomes beneficiary to the organization.
 SCHEDULE FEASIBILITY:
• Our project to prepare or completed in a given time of period property
using some methods like payback period.
Requirement analysis of new system
Functional requirement
Stakeholders
The following are the stakeholders in the application.
 Owner of the restaurant.
Employees (Manager, Host, Waiters, Busboy, and Cook).
Programmers.
Nonfunctional requirement
Usability:-
The system’s user interface will be very simple and self-explanatory.
Con’t
• The manager and the cook will interact with the system through touch-
screen LCDs.
• They are very easy to adapt to and use.
Reliability:-
The system is guaranteed to be reliable.
All inputs to the system will be selections from Options that the system
will show on the screen.
Performance:-
• The system will be used by many employees of the restaurant at the
same time and can handle it without any errors.
• The restaurant should also have a high speed wireless connection for the
system to perform its best.
 Supportability:-
• The system will support changes that the restaurant might need to make in
future.
• The manager will have the ability to modify items from the menu.
Operations Requirements:-
 The restaurant manager will be the sole administrator of the system.
He/she can modify the database and add or delete users from the system.
The manager can also compile reports to analyze the restaurant performance
in general or to see the best selling item or to compare different waiters.
Legal Requirements:-
We will give each of our clients a license to use the software.
System use case diagram for new system
 Description of System Use Case Diagram For
New System
1. Admin login in to a system and the system request login from the database.
2. Admin update profile in to a system and the system add profile to the
database.
3. Admin manages food item details.
4. Admin manage post advertisement.
5. Admin manages report s and graphs to the system & the system request
data for report to the database.
6. Registered users give request for the system and the system response for it.
7. Successful order placed in to a system leads return details.
8. Successful table booking leads return detail for register user.
 Sequence diagram for new system
.
 SEQUENCE DIAGARAM :
Registered user side
: : database
registered user : system
1 . 1 .1 .
Registration request for registration
1 . 1 . 162. 1 1 . 1 .1 . response
success or un successful register
* *
2 . 2 . 1 . request for login
login * *

2 .1 .1 . 1 . 2 . 1 .1 . response for login

success or un success login
* *

3 . * 3 . 1 . request detail *
search for menu item
3 .1 .1 .1 . 3 .1 .1 .
view menu item return detail
* *
4 . add menu item in order * 4 . 1 . detail *

4 .1 . 1 .1 . 4 . 1 .1 . update detail
view added menu item
* *

5 . * 5 . 1 . order detail *
check out or place order
5 .1 . 1 .1 . successfully order placed 5 . 1 .1 . update detail
* *
6 . add hall booking detail * 6 . 1 . request for hall booking *

6 .1 .1 . 1 . 6 . 1 . 1 . return detail
successfully hall booking
*
7
logout * *
*

7 .1 logout succesusfully
*
*

*
*
 SEQUENCE DIAGARAM
Visitor side
Visitor :System :Database

1.search for menu 1.1.request detail

1.1.1.1.view for menuitem 1.1.1.return detail
* *
2.search arrival and offer * 2.1.request detail *

2.1.1.1.view offer and arrivals 2.1.1.return detail

* *

3.request for advertisment * 3.1.request detail *

3.1.1.view advertisment detail 3.1.1.response advertisment detail

* *
* *
*
* * *
* *
 Activity diagram for new system
• Activity diagram is basically a flow chart to represent the flow form one activity to
another activity.
 CHAPTER THREE

DESIGN

• Collaboration diagram
The collaboration diagram is an interaction diagram emphasized the
structural of the object that participate in an interaction.
It consists of a collection of object that work together to perform a task.
Collaboration diagram design to model the logic of implementation of major
user interface element.
 Deployment diagram
• Deployment diagrams are used to visualize the topology of the physical
(hardware) components of a system where the software components are
deployed. So deployment diagrams are used to describe the static
deployment view of a system.
• Deployment diagrams consist of nodes and their relationships.
client system

w3compliant browser

:apache server

login subsystem manager subsystem cook subsystem

waiter subsystem host subsystem

host subsystem

:database server

database subsystem
• Conclusion
• The proposed system is to facilitate easy management and
administration of a restaurant with capabilities to do Booking or
reservations of the rooms, Cancellation of the rooms.
• Finally, Our project on restaurant management system is very
important in order to facilitate computerized data management in the
restaurant and enables easy to retrieval of guest record and data for
fast reference activities, the system is developed especially to meet
the needs of restaurant companies and also to reduce the lack of
restaurant rooms and other constraints.
 FOR EVERYTHING
YOU'VE ASKED ME!!

Cr