Modern Restaurant System ACKNOWLEDGEMENT We wish to express our sincere thanks to our Honorable Principal Dr. P.Ram Mohan Rao for giving us permission for carrying out the project at COIGN Consultants Pvt Ltd, Hyderabad. We gratefully acknowledge the inspiring guidance, encouragement and continuous support of Mr.Karthik Reddy Senior Software Engineer, COIGN Consultants Pvt Ltd, Hyderabad. His helpful Suggestion and constant encouragement have gone a long way in the completion of this dissertation .It was a pleasure working under his alert, human and technical supervision. We express our deep gratitude towards our internal guide, Prof.Jayadev Gyani for his guidance, comments and encouragement during the course of present work. We are grateful to the Head, Department of Computer Science and Information Technology, Prof.Jayadev Gyani, for his valuable suggestions and encouragement during course of the work. We are greatly indebted to our college, Jayamukhi College of Engineering, which has provided us the healthy environment to drive us to achive our ambitions and goals. We owe our hearty regards to all other Proffesors and staff for their encouragement at each step and their assistance 1
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
Modern Restaurant System
ACKNOWLEDGEMENT
We wish to express our sincere thanks to our Honorable Principal Dr. P.Ram Mohan Rao for
giving us permission for carrying out the project at COIGN Consultants Pvt Ltd, Hyderabad.
We gratefully acknowledge the inspiring guidance, encouragement and continuous support
of Mr.Karthik Reddy Senior Software Engineer, COIGN Consultants Pvt Ltd, Hyderabad. His
helpful Suggestion and constant encouragement have gone a long way in the completion of this
dissertation .It was a pleasure working under his alert, human and technical supervision.
We express our deep gratitude towards our internal guide, Prof.Jayadev Gyani for his
guidance, comments and encouragement during the course of present work. We are grateful to the
Head, Department of Computer Science and Information Technology, Prof.Jayadev Gyani, for his
valuable suggestions and encouragement during course of the work.
We are greatly indebted to our college, Jayamukhi College of Engineering, which has
provided us the healthy environment to drive us to achive our ambitions and goals.
We owe our hearty regards to all other Proffesors and staff for their encouragement at each
step and their assistance in completion of the project work. Last but not the least; we would like
to thanks our friends for their co-operation and consistent support.
1
Modern Restaurant System
CONTENTS:
I COIGN Profile
1. INTRODUCTION
1.1 Purpose
1.2 Document conventions
1.3 Intended Audience and Reading Suggestions
1.4 Goal
1.5 Benefits
2. SYSTEM ANALYSIS
2.1 Existing System
2.2 Proposed System
3. ARCHITECTURE
4. SYSTEM DESIGN
4.1 Module Description
4.2 UML Diagrams
4.3 E-R Diagrams
4.4 Data Dictionary
4.5 Hardware and Software Requirements
2
Modern Restaurant System
5. ENVIRONMENT & TECHNOLOGY
6. TESTING
6.1 Testing objectives
6.2 Levels of testing
6.3 White box testing
6.4 Black box testing
6.5 Unit testing
6.6 Integration testing
7. TEST CASES
8. SCREEN SHOTS
9. CONCLUSIONS
10. REFERENCES
3
Modern Restaurant System
ABSTRACT
In this mechanical world, the most precious thing which no person can buy with money i
s “time”. So our effort is being laid out in an area where we can help people to save their valuable
time. When you have a restaurant spread on two floors, 30 tables each, 2 bar counter, 2 different
kitchens, 1 Dedicated beverages counter.
A single order can consist of Menu Items to be supplied from different kitchens and bar
counters, due to which there might be problems .Such as:
• Delay in serving
• Misconception of the order
• More requirement of manpower And many more...
Our Modern Restaurant System is a software application which can be implemented by
Providing touch screen facility that puts your business at your fingertips and makes it easy, too.
This software enables the customer to view the menu card on the touch screen and order the
items by himself with the touch of the finger on the screen. Also he can know the amount he need
s to pay. Orders entered by the customer at the client station automatically display at the cooks
station, increasing the speed with which orders can be prepared and decreasing the wasted
time of servers walking back and forth to the kitchen!
When the customer feels to receive the bill he can just close the session so that the bill will be
generated at the server end and also it will be displayed on the table screen.
It can be configured for Fine Dining Restaurants, Bars & Lounges, Discos & Nightclubs, and
Food Court with Prepaid System, Home Delivery, Quick Service / Fast Food and Cafeterias.
In this project we are going to deal with three modules:
Central Management System: This is the centralized location where the menu
is designed and relayed to all ordering terminals.
4
Modern Restaurant System
Ordering screen: You can place order here and can view the bill amount and
close the session.
Kitchen Production System: Customers order the items on the touch screen
and these items will be displayed on screen in the kitchen.
Features of Modern Restaurant System:
Regional language support
Easy capture of Customer Information
Display Customer's Last Visit & Billing Information
Touch Screen Interface / Cash Register Interface
This system attracts wide range of customers
Give customers what they want and improve your customer satisfaction
Reduce manpower cost
Fast billing counters & happy customers
5
Modern Restaurant System
6
Modern Restaurant System
1. INTRODUCTION
1.1 Purpose
Our Modern Restaurant System is a software application which can be implemented by
providing touch screen facility that puts your business at your fingertips and makes it easy, too.
This software enables the customer to view the menu card on the touch screen and order the items
by himself with the touch of the finger on the screen.
1.2 Document Conventions
In this SRS document, we have used the following format:
For Headings: Font: 16pt
Font-face : Times New Roman
Font-weight :Bold
For Sub Headings:
Font: 14pt
Font-face : Times New Roman
Font-weight :Bold
For Content : Font: 11pt
Font-face: Times New Roman
Font-weight: Normal
KPS: Kitchen Production System
SRS: Software Requirements Specification
DB: Database
OS: Operating System
Future scope for this project: Italics
7
Modern Restaurant System
1.3 Intended Audience and Reading Suggestions
This SRS is mainly intended for developers, testers, users and marketing staff. The suggested
sequence for reading SRS is:
1. Overall Description
2. System Features
3. External Interface Requirements
4. Non Functional Requirements.
1.4 Goal
To overcome the following consequences:
a. Delay in serving
b. Misconception of order
c. More requirement of manpower……..
1.5 Benefits
Increase your number of customers
Fastest implementation (just a snap!)
Increase the number of sales per customer
Give customers what they want and improve your customer satisfaction
Reduce manpower cost
Reduce the erroneous data entry
Fast billing counters & happy customers
8
Modern Restaurant System
2 SYSTEM ANALYSIS
2.1 Existing System:
In this system the customer is given a menu card from which he needs to select the items and
orders are noted down by the waiter manually. Then the waiter submits this order to the kitchen
head, who instructs the chefs. On the request of the customer for the bill, the waiter informs the
cashier to generate the bill and gets back the bill to the customer for payment. Due to this there
are many drawbacks such as :
a. Delay in serving
b. Misconception of order
c. More requirement of manpower……..
To avoid all these we will switch to Modern Restaurant System.
2.2 Proposed System:
Our MRS is an innovative solution for restaurants which can create craze among the youngsters.
MRS is a windows based application developed in .Net. This application is concerned with 3
modules:
Back Office
KPS
User Terminal
This software enables the customer to view the menu card on the touch screen and order the items
by himself with the touch of the finger on the screen. Also he can know the amount he
need to pay. When the customer feels to receive the bill he can just close the session so that the
bill will be generated at the server end and also it will be displayed on the table screen.
Orders entered by the customer at the client station automatically display at the
cooks station, increasing the speed with which orders can be prepared and decreasing the wasted
time of servers walking back and forth to the kitchen! When the customer closes the session, the
order information along with the bill details automatically send to the server where the bill is
generated avoiding misconceptions in the bill
9
Modern Restaurant System
3 ARCHITECTURE
BACK OFFICE
7777777777
6
4
1, 2, 3
USER TERMINALS 5
1: Signal send to Back Office when a table is occupied by customer
2: Signal send to Back Office when customer request for the bill
3:Signal send to Back Office when customer registers
4: Menu Card displayed on each terminal is updated by Back Office through this signal.
5: Ordered Items are send to Kitchen room.
6: Signal send to KPS when customer vacates table.
10
Kitchen production system
DB
Configuration update
Table 1
Table N
Modern Restaurant System
LIFE CYCLE MODEL USED
The life cycle model which we use in our application is RAD (Rapid Application Development)
model.
RAD (rapid application development) is a concept that products can be developed faster and of
higher quality through:
Gathering requirements using workshops or focus groups
Prototyping and early, reiterative user testing of designs
The re-use of software components
A rigidly paced schedule that defers design improvements to the next product version
Less formality in reviews and other team communication
CHARACTERISTICS OF RAD
A. RAD USES HYBRID TEAMS
Teams should consist of about 6 people, including both developers and full-time
users of the system plus anyone else who has a stake in the requirements
Developers chosen for RAD teams should be multi-talented "renaissance" people
who are analysts, designers and programmers all rolled into one
B. RAD USES SPECIALIZED TOOLS THAT SUPPORT
"visual" development
creation of fake prototypes (pure simulations)
creation of working prototypes
multiple languages
team scheduling
teamwork and collaboration
11
Modern Restaurant System
use of reusable components
use of standard APIs
C. RAD USES ITERATIVE, EVOLUTIONARY PROTOTYPING
ITERATE UNTIL DONE
a. Developers build / evolve prototype based on current requirements.
b. Designers review the prototype.
c. Customers try out the prototype, evolve their requirements.
d. FOCUS GROUP meeting
e. Customers and developers meet to review product together,
refine requirements, generate change requests.
Developers listen.
Customers talk.
f. Requirements and change requests are "time boxed".
Changes that cannot be accommodated within existing timeboxes are
eliminated.
If necessary to stay "in the box," secondary requirements are
dropped.
WHEN RAD WORKS AND WHEN IT DOESN'T
A. RAD TENDS TO WORK WHEN
The application will be run standalone.
Major use can be made of preexisting class libraries (APIs).
Performance is not critical.
Product distribution will be narrow (in-house or vertical market).
Project scope (macro-schedule) is constrained.
Reliability is not critical.
System can be split into several independent modules.
The product is aimed at a highly specialized IS (information systems) market.
12
Modern Restaurant System
The project has strong micro-schedule constraints (time boxes).
The required technology is more than a year old.
B. RAD TENDS TO FAIL WHEN
Application must interoperate with existing programs.
Few plug-in components are available.
Optimal performance is required.
Product development can't take advantage of high-end IS tools
(e.g., 4GLs).
Product distribution will be wide (horizontal or mass market).
RAD becomes QADAD (Quick And Dirty Application Development).
RAD methods are used to build operating systems (reliability target too high for
RAD), computer games (performance target too high for RAD).
Technical risks are high due to use of "bleeding" edge technology.
The product is mission - or life - critical.
The system cannot be modularized (defeats parallelism).
EVALUATION OF RAD:
1. ADVANTAGES OF RAD
Buying may save money compared to building
Deliverables sometimes easier to port (because they make greater use of high-level
abstractions, scripts, intermediate code)
Development conducted at a higher level of abstraction (because RAD tools operate at
that level)
Early visibility (because of prototyping)
Greater flexibility (because developers can redesign almost at will)