1 / 26

RESTAURANT AUTOMATION

RESTAURANT AUTOMATION. BILAL AHMAD STEVEN CARVELLAS GOURI DONGAONKAR NAVEEN GAVINI BRIAN KASZYK. BREAK DOWN . REQUIREMENTS AND OBJECT-ORIENTED ANALYSIS. REQUIREMENTS. What users will be able to do with the product?. What the developers need to build?.

ulf
Télécharger la présentation

RESTAURANT AUTOMATION

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. RESTAURANT AUTOMATION BILAL AHMAD STEVEN CARVELLAS GOURI DONGAONKAR NAVEEN GAVINI BRIAN KASZYK

  2. BREAK DOWN

  3. REQUIREMENTS AND OBJECT-ORIENTED ANALYSIS

  4. REQUIREMENTS What users will be able to do with the product? What the developers need to build? Why the project is being undertaken?

  5. 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

  6. REQUIREMENTS • Software Requirements: • User Role Permissions • Create Order • Retrieve Order Information • Manage Restaurant • Clear and Complete UI • Real time / Reliable

  7. OBJECT-ORIENTED ANALYSIS • Use Cases: • Seat Customer • Manage Order • Kitchen Queue • Order Completion • Restaurant Summary • Use Case Diagram • Sequence Diagram • Domain-Level Class Diagram

  8. OBJECT-ORIENTED ANALYSIS Use Case Use Case Diagram

  9. OBJECT-ORIENTED ANALYSIS Sequence Diagram

  10. OBJECT-ORIENTED ANALYSIS Domain Level Diagram

  11. DOMAIN FIELDWORK - Interview Transcripts: Interview Question • Name: David Gumpert • Job Position: Waiter • 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) • Food Type: American casual? • Size of location (max occupancy): 250-275ish • Size considered – small, medium, large: I would say that this is a fairly large restaurant • Time Worked: 4 years • 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 running 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 software/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 if 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 interface, and ‘upgrading’ to something else to handle ordering. I don’t remember what it was called. Trying to optimize ordering/minimize waste. • 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. • 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.

  12. ARCHITECTURE AND SYSTEM DESIGN

  13. ARCHITECTURE AND SYSTEM DESIGN System Components • Model • View • Controller

  14. ARCHITECTURE AND SYSTEM DESIGN Subsystem Breakdown • View: • Broken down to two Category • Tables Menu items/users

  15. ARCHITECTURE AND SYSTEM DESIGN Subsystem Breakdown • Controller: • Broken down to two Category • Menu items and users Customer and tables

  16. ARCHITECTURE AND SYSTEM DESIGN Subsystem Breakdown • Model: • Table • User • Customer • Menuitems • Waitqueue • Orders • Hours • News

  17. ARCHITECTURE AND SYSTEM DESIGN Control Flow:

  18. ARCHITECTURE AND SYSTEM DESIGN Mapping Subsystems to Hardware & Software

  19. ARCHITECTURE AND SYSTEM DESIGN Persistent Data Management:

  20. ARCHITECTURE AND SYSTEM DESIGN Access Control and Security: • 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 Boundary Conditions:

  21. Implementation

  22. IMPLANTIATION Languages: • PHP • HTML/CSS • mySQL Database:

  23. Testing

  24. TESTING Unit Testing Frameworks: • xUnit framework compliant test tool SimpleTest • TestofTesting • TestofWebpage • EmployeeManagement • SeatCustomer • TestDatabase • MenuItems • http://sourceforge.net/projects/simpletest/

  25. Demo

  26. Feedback

More Related