Loading presentation...

Present Remotely

Send the link below via email or IM

Copy

Present to your audience

Start remote presentation

  • Invited audience members will follow you as you navigate and present
  • People invited to a presentation do not need a Prezi account
  • This link expires 10 minutes after you close the presentation
  • A maximum of 30 users can follow your presentation
  • Learn more about this feature in our knowledge base article

Do you really want to delete this prezi?

Neither you, nor the coeditors you shared it with will be able to recover it again.

DeleteCancel

Make your likes visible on Facebook?

Connect your Facebook account to Prezi and let your likes appear on your timeline.
You can change this under Settings & Account at any time.

No, thanks

Restaurant Order Management system

No description
by

Farnaz Ansari

on 23 December 2013

Comments (0)

Please log in to add your comment.

Report abuse

Transcript of Restaurant Order Management system

A replacement for paper format menu.
Including friendly touch screen, a credit/debit card reader, and software for completing the process .
The system includes data receiving,storage,display and analysis.
Customers will know the price ,taste & some sample pictures of the food.

Restaurant Order Management system
Conclusion
Introduction
Lack of applications of technology in restuarants daily operations.Increasing labor rates and difficulties of finding employees.
KFC
By Farnaz
Javad
Qilong
Sepid

Functional Requirements:Functional requirements are necessary for developing systems. Table-1 discusses the functional requirements of our system with descriptions and priority weights of each requirement. These requirements state what the system should be able to accomplish. Subset to these requirements is non-functional requirements that are discussed next.
Subway
Burger King

Mc Donald
DFD Diagram:
Non-functional requirements are also essential in system development. There is not a significant distinction between functional and non-functional requirements. Non-functional requirements relates to the superficial conditions needed for the system, such as number of clicks needed to complete a task for individual actors. Table 2-discusses the non-functional requirements of our system.
Glossary of Terms
Manager – Controls and oversees all of the business. In charge of editing the menu items available to the
customers. The manager is also responsible for assessing restaurant performance.

Customer – Orders Food and services from the restaurant.

Chef – Cooks food ordered by the customer.

Waiter – Assists customer upon request. Waiter is responsible for serving food.

Hostess - Receives customers and handles reservations.
Clock In/Clock Out – A system function that allows employees to enter their hours for manager to run payrolls.

Reservation System – Customers can reserve a table using an android application.
Payroll – The amount of money each employee will receive for their services. The payroll differs for each employee.

Menu – List of dishes available in the restaurant. Will be displayed on an android tablet.

Floor Layout – Shows all tables in the restaurant along with their respective status.(ex: Occupied, Reserved etc.)

User Interface – The visual on the computer and tablet that allows user interaction with the system. Allows touch screen interaction to order, pay bill, call waiter and view order.

Table Status – Shows the availability of a table as well as the waiter in charge of serving that table.

Order Status – Shows whether the order of a particular table is ready to be “served” or “cooking”.

Payment – Customers have the option of payment through cash or credit.

Ads – Appear on the menu when idle. Manager has options to edit the slides.

Wireless Access Point – Access points used in home or small business networks are generally small, dedicated hardware devices featuring a built-in network adapter, antenna, and radio transmitter. Access points support Wi-Fi wireless communication standards.

Terminals – These are terminals used by hostess, manager, chef and waiter running Windows 7.

POS – Point of Sale System









Client Server communication process
Problem Statement
This will minimize the number of employees at the back of the counter.
The system will help to reduce the cost of labor.
The system will be less probable to make mistake, since it?s a machine.
This will avoid long queues at the counter due to the speed of execution and number of optimum screens to accommodate the maximum throughput.
The system will be available 24 hours for 365 days, because the machine is not going to take any sick or vacation leave.



In this project, we designed an intelligent restaurant self-service ordering information system , this system can improve the management level of traditional catering enterprises, can reduce the cost of catering enterprises in financial accounting. It also can improve human resource utilization, and dramatically speed up the serving speed, speed up the checkout speed. This system can real-time receive, store, analyze, display and analysis data for each user. It’s flexibility and portability which have very broad application prospects.

Activity diagram for this use case is given as below:
Verification and Validation : techniques and plans, methods and strategies


Usability testing
We will ask staff test the new system first .Try to order a set of food and then check the system processor is working or not .

System running testing
We will use the new system in real business two days first ,then record it running good or not .Such as it is faster than before or more popular in customers .If it not good ,we will stop it and go to" Plan B".

Functional testing
we will test the stability for new system .Modify the algorithm ,and try to avoid system data crash . Then we will consider the OS or Tool is suitable or not .

Installation testing
We try to install the system is some new call phones ,ipads and laptops. Checking the compatibility .
Full transcript