Instructions Data Models: create a logical and relational Data Model for McDonald's Restaurant a. Identify entities and attributes of each entity to support the database solution. Must include a MANAGER

and at least 7 fully normalized entities (appropriate relationships, primary keys, foreign keys, data types, comments on each attribute, proper naming conventions etc.). THERE MUST NOT BE ANY CLOSE LOOP AND MANY-TO-MANY RELATIONSHIPS. b. Create Logical Data Model and convert it to Relational Data Model. c. Assumption made about business rules to support your data model. d. Generate DDL code. Format: 1. 2. 3. The initial for each table name is CK_ follow by the table/entity name. Provide Tables relationship details Screenshots of Logical Model and Relational model. Student note : This project is ongoing. The design will be updated as we go Using Oracle Data Modeler create a logical and relational Data Model check the Design Rules and make sure there is no error/n Assignment Instructions: Data Models: create a logical and relational Data Model for McDonald's Restaurant. Please verify the design against DB DESIGN CHEKLIST below: Instructions: CHECKLIST FOR OLTP DATABASE DESIGN 1 Composite Attribute(s) resolved 2 Derived Attributes(s) resolved 3 Multivalued Attributes(s) resolved 4 Primary Key defined for each table 5 Primary Key guarantees uniqueness 6 Foreign Key column(s) are matching referring PK column(s) [foreign key columns are renamed to match corresponding PK column] 7 Relationships are appropriately defined among entities 8 Many to Many relationship are resolved 9 For One-to-One relationship, only one table is Parent table, and one reverse relationship is manually deleted 10 For all attributes proper datatype and their sizes are defined 11 Attributes are marked Optional or Mandatory per the business case or appropriately to business 12 Name of tables are not repeating, and attribute names within same table are not repeating 13 Table names and Colum names are less than 30 characters, not the reserved words, and not multiple words 14 There is no close loop in one direction. 15 PK are properly marked for intersect tables 16 All table names are having your initial as prefix 17 Comments are created for each attributes 18 While generating DDL, if errors are about FK constraint length, FK constraint name is edited to be less than 30 characters 19 DDL generated from relational model has no errors. 20 Logical and Relational are fully expanded to depict full details 21 Supertype should have at least two subtypes. If only one subtype, then it is the part of supertype itself. Meaning, a single table itself. 22 Subtypes should have at least one differentiating attribute in each subtype. 23 There cannot be a subtype with just the primary key and no other differentiating attribute(s) Data Models: create a logical and relational Data Model for McDonald's Restaurant a. Identify entities and attributes of each entity to support the database solution. Must include a MANAGER and at least 7 fully normalized entities (appropriate relationships, primary keys, foreign keys, data types, comments on each attribute, proper naming conventions etc.). THERE MUST NOT BE ANY CLOSE LOOP AND MANY-TO- MANY RELATIONSHIPS. b. Create Logical Data Model and convert it to Relational Data Model. c. Assumption made about business rules to support your data model. d. Generate DDL code. Format: 1. The initial for each table name is CK_ follow by the table/entity name. 2. Provide Tables relationship details 3. Screenshots of Logical Model and Relational model. Entities and Attributes: 1. CK_Restaurant: (Represents a physical McDonald's location) Restaurant_ID (Primary Key): Unique identifier о О ○ Restaurant_Name: e.g., "McDonald's Times Square" Restaurant Address: Street address О Restaurant City: O O O O Restaurant State: Restaurant Zip: Manager_ID (Foreign Key): Links to the managing manager Open 24 Hours: (Boolean, indicates 24/7 operation) 2. CK_Manager: (Represents restaurant managers) O 00 о Manager_ID (Primary Key): Unique identifier Manager_Name: Manager_Email: Manager Phone: 3. CK_Employee: (Represents all restaurant staff) О о ○ O O O Employee_ID (Primary Key): Unique identifier Employee_Name: Employee_Email: Employee_Phone: Manager_ID (Foreign Key): Links to their manager Job Title: e.g., "Cashier", "Cook" 4. CK_Customer: (Represents patrons of McDonald's) Customer_ID (Primary Key): Unique identifier Customer_Name: Customer Email: Customer Phone: 5. CK_Menu Item: (Represents food and beverage items) Menu_Item_ID (Primary Key): Unique identifier О ○ Menu Item Name: e.g., "Big Mac" ○ Menu Item Description: ○ Menu Item Price: ○ Menu Item Category: e.g., "Burgers", "Drinks" 6. CK_Order: (Represents a customer's order) ○ Order ID (Primary Key): Unique identifier ○ O O O Restaurant_ID (Foreign Key): References the restaurant Customer ID (Foreign Key): References the customer Order Date: Datetime of order placement Order Total: 7. CK_Order_Item: (Represents items within an order) Order_Item_ID (Primary Key): Unique identifier Order ID (Foreign Key): References the order ○ Menu Item ID (Foreign Key): References the menu item Quantity: Relationships: • • One-to-Many (Restaurant to Manager): A restaurant has one manager; a manager can manage multiple restaurants. One-to-Many (Manager to Employee): A manager oversees multiple employees; an employee reports to one manager. One-to-Many (Customer to Order): A customer can place multiple orders; an order is placed by a single customer. Many-to-Many (Order to Menu_Item): An order can have multiple menu items; a menu item can be part of multiple orders. This is resolved through the CK_Order_Item table.