USING HAND WRITING (((( ER DATA MODEL )))

Given the following Requirements Restaurant Menu & Ordering System The Restaurant Menu and Ordering System is a software package to facilitate ordering within a traditional restaurant. The customer is able to view the menu, place orders, call the waiter, and organize the final bill through the surface computer interface built into their table. Waiters are able to initialize a table for customers, control table functions remotely to assist customers, confirm orders, send orders to food preparation staff and finalize the customer's bill - all through their wireless tablet PC. The food staff, with their touch-display interfaces to the system, are able to view orders sent to the kitchen by waiters. During preparation, they are able to let the waiter know the status of each item, and can send notifications when items are completed, again through the touch- display. The system contains full accountability and logging systems, and supports supervisor actions to account for exceptional circumstances, such as a meal being refunded or walked out on. Customers are presented with an attractive and easy-to-use surface computer GUI with a drag-and-drop 'object' metaphor in their menus. Waiters are able to perform all actions that the table system normally handles via their tablet PCs, so in the event of a customer being unable to operate the surface computer, the waiter can handle orders traditionally while using retaining the accountability and logging functions of the system, and retaining the same channel of communication with food staff. Project Duties: Part I: Study and analyze the given system requirement then do the following: A: Illustrate by hand Drawing 1) Identify the possible Entities and draw the initial conceptual schema (Level 0) using ER data model. 2) Identify the possible attributes for each entity and refine the initial conceptual schema (Level 1). 3) Identify the possible Relationships between entities and refine the conceptual schema (Level 2). 4) Identify the possible constraints (Cardinality and Participation) for each Relationship and refine the conceptual schema (Level 3). 5) Remove any redundant attribute and refine the conceptual schema (Level 3)