RESAURANT AUTOMATION - Steven Carvellas

possehastyMechanics

Nov 5, 2013 (3 years and 9 months ago)

66 views

RESTAURANT
AUTOMATION

BILAL AHMAD

STEVEN CARVELLAS

GOURI DONGAONKAR

NAVEEN GAVINI

BRIAN KASZYK

BREAK DOWN

REQUIREMENTS AND OBJECT
-
ORIENTED
ANALYSIS

ARCHITECTURE AND SYSTEM DESIGN

IMPLEMENTATION

TESTING

DEMO

FEEDBACK

REQUIREMENTS AND
OBJECT
-
ORIENTED ANALYSIS


REQUIREMENTS

BUSINESS
REQUIREMENTS

USER
REQUIREME
NTS

SOFTWARE
REQUIREMEN
TS

What the developers
need to build?

What users will be
able to do with the
product?

Why the project is
being undertaken?

REQUIREMENTS


Business Requirements:


Increased Productivity


Increase in Profits and Reduce in operating costs


Data Analysis


User Requirements:


More Co
-
coordinated


Order filling and Billing Calculation


FURPS


U
-
Usability


R
-
Reliability


P
-
Performance


S
-
Supportability


REQUIREMENTS


Software Requirements:


User Role Permissions


Create Order


Retrieve Order Information


Manage Restaurant


Clear and Complete UI


Real time / Reliable



OBJECT
-
ORIENTED
ANALYSIS


Use Cases:


Seat Customer


Manage Order


Kitchen Queue


Order Completion


Restaurant Summary


Use Case Diagram


Sequence Diagram


Domain
-
Level Class Diagram



OBJECT
-
ORIENTED
ANALYSIS

Use Case UC
-
1: SeatCustomer

Related
Requirements:

REQ 6

Initiating Actor:

Host/Hostess

Actor’s Goal:

To⁳ 慴 愠捵s瑯me爠慴⁡n 慶慩污b汥 瑡b汥 慮d p牯v楤e⁡⁷慩瑥

偡牴楣楰慴楮朠慣ao牳:

䑡D慢慳a, Hos琠U䤬⁗慩aer

偲散ond楴楯ns:

GU䤠shou汤 be⁵sed⁴o⁩ 瑥牡捴tw楴i⁴he⁤慴慢慳a.

偯s瑣tnd楴楯ns:

The 瑡b汥 楳⁡ss楧湥i 慮d 瑨e w慩ae爠楳o瑩晩ed 瑯⁴慫e
捵s瑯me爧s o牤er

䙡楬Fd⁅nd
䍯Cd楴楯n:

No⁴慢汥s⁡nd⽯/ w慩ae牳⁡牥⁡v慩污b汥

Flow of events for main success scenario:


ㄮ⁈os琠楳⁰牯v楤ed⁡ m慰⁷楴 ⁡v慩污b汥 se慴楮朠op瑩tns


2
.
Host assigns customer to appropriate seat as well as a waiter




Table is entered into database by UI



㐮⁁4p汩l慴楯i no瑩晩es⁷慩瑥爠 f⁴慢汥 慳a楧湭int

Flow of events for Extensions (Alternate Scenario
):


No seating is available


Enter customer into wait queue.


Application notifies host of available seat as well as waiting customers.

3
.

Storage to database fails.


← 1. Application cancels task.




2.

Application notifies user of failure.

OBJECT
-
ORIENTED
ANALYSIS

OBJECT
-
ORIENTED
ANALYSIS

DOMAIN
FIELDWORK
-

Interview Transcripts:


1.
Name
:

David Gumpert

2.
Job Position:

Waiter

3.
Restaurant Name:

TGI Fridays (owned by the Briad Group


we’re a franchise, but your average guest wouldn’t know that.
Our software is different than a typical Fridays, but Briad is a large franchise with 110ish stores)

4.
Food Type:

American casual?

5.
Size of location (max occupancy):

250
-
275ish

6.
Size considered


small, medium, large:

I would say that this is a fairly large restaurant

7.
Time Worked:

4 years

8.
Current Billing and Ordering System:


This is a loaded question. When we started, we used Micros POS (I’m not sure which version) in the store, with something else

ru
nning the back end (ordering, etc) and third
party software/hardware to interface with the kitchen.


We “upgraded” to aloha somewhere along the line, which ran the back end (ordering) and the store, but we still used another s
oft
ware/hardware package to interface with the
kitchen.


Then we upgraded the kitchen interface to KMS somewhere along the line to try to optimize things like food timing, etc. Now i
f a

grilled cheese and well done steak are
ordered, the cooks will get the steak 10 or so minutes before they get the grilled cheese. The idea is that both things will
be
finished at the same time. It can also guess which
stations in the kitchen are behind and delay other food accordingly.


When I left, they were leaving the aloha front end in place (what people in the restaurant use), as well as the kitchen inter
fac
e, and ‘upgrading’ to something else to handle
ordering. I don’t remember what it was called. Trying to optimize ordering/minimize waste.

9.
Do
you think an automated system would be better? If so why?

Everything is already more or less as automated as it
can possibly be, but human input is still needed for things like ordering food (raw food to be cooked, not food for a table)
because of weird things that are hard to quantify like people’s buying habits, holidays, pictures of food in the menu, new
menus/menu changes, events at the store or in the area (football games, band events), etc. One reason why they switched
to aloha was because it could do a lot of trending and what not. I believe whatever they’re upgrading to does this even
better and has inputs for some of the other inputs I mentioned.

10.
Who will benefit from this system:

management who will hopefully run out of things less often. Try explaining to a table
that we ran out of flower so we can’t bread anything until one of our managers gets back from the grocery store. The new
system will also theoretically cut down on waste by not ordering too much food.


ARCHITECTURE AND SYSTEM
DESIGN

ARCHITECTURE AND
SYSTEM DESIGN


Model


View


Controller

ARCHITECTURE AND
SYSTEM DESIGN


View:


Broken down to two Category


Tables




Menu items/users



ARCHITECTURE AND
SYSTEM DESIGN


Controller:


Broken down to two Category


Menu items and users



Customer and tables


ARCHITECTURE AND
SYSTEM DESIGN


Model:


Table


User


Customer


Menuitems


Waitqueue


Orders


Hours


News



ARCHITECTURE AND
SYSTEM DESIGN

The actor interacts with the GUI
by logging into the webpage and
accessing their respective View.

The controller handles the input
event from the GUI and converts
the event into an appropriate user
action for the model.

The controller notifies the model
of the user action, possibly
resulting in a change in the
model's state.

The actor's view queries the
Model in order to generate an
appropriate GUI view. The view
gets its own data from the model.
The controller then issues a
general instruction to the view to
render itself.

The user interface waits for
further actor interactions, which
restarts the cycle.

ARCHITECTURE AND
SYSTEM DESIGN

ARCHITECTURE AND
SYSTEM DESIGN

ARCHITECTURE AND
SYSTEM DESIGN


Startup:


Before any clients can login, the main server must be turned on and loaded.


Shutdown:


If
at any time the main server is shut down, the clients will be automatically be
disconnected
.


Error Handling:


built into the controllers for each type of action



IMPLEMENTATION

IMPLANTIATION


PHP


HTML/CSS



mySQL


TESTING

TESTING


xUnit
framework compliant test tool SimpleTest


TestofTesting


TestofWebpage


EmployeeManagement


SeatCustomer


TestDatabase


MenuItems


http
://sourceforge.net/projects/simpletest/


DEMO

FEEDBACK