A1 analysis design


Published on

  • Be the first to comment

  • Be the first to like this

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide
  • Use case diagram mainly illustrates;Who are users?Main functions operated by user.
  • Class diagram mainly illustrates;Relationships between each class or entityAttributes in each class or entityExample of methods in each class or entity
  • ER diagram mainly illustrates;EntitiesRelationshipsAttributesPrimary keys and foreign keys
  • ER diagram mainly illustrates;EntitiesRelationshipsAttributesPrimary keys and foreign keys
  • Drinks and Sweet are served at different times.Drinks are served immediately.Sweet is served finally.
  • The diagram explains all processes;From customers come into the restaurantTo customers leave from the restaurant
  • This diagram was used to develop the e-menu application.It shows all processes of e-menu application (on iPad)It shows how the data are input into the database.
  • A1 analysis design

    1. 1. ANALYSIS AND DESIGN DOCUMENTS FOR DEVELOPMENT OF RESTAURANT E - MENU PROTOTYPE Created by Traitet Th.Project: E-menu on iPad for Thai restaurant Created Date 31 July 2012Subject: Research outcome#1 Revised Date 6 Sep 2012 Revision No. 1.0Content: Functional Requirements, UML Use case and Class Document Name O01-001 Diagrams, and Workflow and Process diagrams.
    3. 3. 3 1) FUNCTIONAL REQUIREMENTS E-menu system consists of 1. E-menu application on iPad for restaurant customers Main features • Ordering food & drinks • Confirm and view orders • Request services 2. E-menu web application for restaurant staff • Manage table • Open & Close table • Operate order • Drinks, Starter, Main course, and Sweet Operate services requested • Call waiter, main course and bill
    4. 4. 4 1) FUNCTIONAL REQUIREMENTS Functional Requirements (E-menu application on iPad)Restaurant Customers E-menu on iPad for  Restaurant customers can order food and drinks on e-menu.  Restaurant customers can search menu items by menu categories such as appetisers, main course, sweets and drinks.  Restaurant customers can check ordered items before confirming.  Restaurant customers can cancel ordered items before confirming.  Restaurant customers can request waiting staff on e-menu  Restaurant customers can request billing on e-menu.  Restaurant customers can request delivery of main course on e-menu after they have finished their appetisers.  Restaurant customers can check status of ordered items, such as queuing, cooking, serving and served, on e-menu.  Restaurant customers can select different languages to make their order.
    5. 5. 1) FUNCTIONAL REQUIREMENTS 5 ( CONT.)Restaurant Customers Functional Requirements (E-menu application on iPad) E-menu on iPad for  E-menu can provide basic information for customers, such as pictures, names and prices of each menu item.  E-menu can provide additional information, such as menu descriptions, levels of spic and recommended items.  E-menu can summarise list of order including total price and number of items ordered.  The system can transfer information from iPad e-menu to a kitchen and bar for preparation of food and drinks.  The system can transfer information from iPad e-menu to a cashier to prepare for payment.  The system can transfer information from iPad e-menu to show list of services requested by restaurant customers.
    6. 6. 1) FUNCTIONAL REQUIREMENTS 6 ( CONT.) Functional Requirements (E-menu application on Web)E-menu on iPad for Restaurant Staff  The system can operate table for a new customer groups such as opening or closing a new table and Ordering.  Waiting staff can monitor and operate services requested by customers such as a request of main course, waiter and billing.  Chef and waiting staff can view and maintain orders transferred from iPad e-menus to prepare food and drinks for customers.  Chef and waiting staff can record ordering status for preparing, cooking and serving.  Waiting staff can check order list requested by customers
    8. 8. 8 2) NON-FUNCTIONAL REQUIREMENTS Non-functional Requirements  Real-time Information can be transferred from iPad e-menu to a kitchen, cashier, and bar though wireless connection.  User interfaces’ e-menu should be user-friendly and easy to use.  E-menu should provide useful information including authentic images of food and drinks so restaurant customers can easily understand menu description.  E-menu on iPad can consume web services provided by a external server through internet connection.
    9. 9. 2) NON-FUNCTIONAL REQUIREMENTS9 (CONT.) Non-functional Requirements  E-menu system must provide web services to integrate data between iPad e-menu, back office application and a database.  E-menu system must have adequate security to access system information such as Web service authentication.  E-menu system should record log of each transaction including transaction, user name and time to make analytics reports in the future.  E-menu system must provide real-time information with quick response. All transactions must take less than 2 seconds.
    10. 10. 3) USE CASE DIAGRAM 10
    11. 11. 3) USE CASE DIAGRAM
    12. 12. 4) CLASS DIAGRAM 12
    13. 13. 4) CLASS DIAGRAMFor developing the e-menu prototype
    14. 14. 5) ER DIAGRAM 14
    15. 15. 5.1) ER-DIAGRAMFor developing the e-menu prototype
    16. 16. 5.2) REVISED ER-DIAGRAM(To develop a real e-menu application in the future)
    18. 18. Food ordering processes 6.1) DESIGN OF RESTAURANT SERVICE PROCESS18 Simple Current Restaurant System (As-it system) Order from CustomerDrinks Starters Main Dishes Sweet 1. Kitchen 2. Bar 3. Front-bar Taken Order (3 copies) Post on board in Prepare Main front of the Cook Starters Give to bar Dishes kitchen Request to eat Cook Main Main Dish Dishes Serve Main Serve Drinks and Serve Starter Dishes Sweet
    19. 19. 6.2) DESIGN OF RESTAURANT SERVICE PROCESSFor developing the e-menu prototype (To-be system)
    20. 20. 7) E-MENU WORKFLOW DIAGRAM (E-MENU) 20
    21. 21. 7) WORKFLOW DIAGRAMFor developing the e-menu prototype