This assignment will allow you to apply the knowledge you have learned about Entity Relationship Diagrams in this class. Before attempting this assignment, make sure you have read and understood how to draw a basic Entity-Relationship diagram on pp 179- 186 in your textbook, and also read the content I generated which is included in this week's submodule, CP: Some NOTES On Entity. Relationship Diagrams. Please draw an Entity Relationship Diagrams as described in the problem below, and submit the diagram in electronic form in CANVAS in a standard image form (jpg, gif, etc.) or pdf. You may create the diagram by hand or using a standard drawing software (e.g. MS Word, Powerpoint). NOTE: Please make sure to follow the drawing methods described in the book and in this week's module. If you use another drawing method, you will not receive credit. If you have any questions, please let me know and I will be most happy to assist you. I hope you enjoy this activity! PROBLEM: You are asked to design a data model for Burma Grotto, a new restaurant featuring Burmese cuisine, including delicious versions of Tea Leaf Salad, Samusas, and other traditional Burmese dishes. Burma Grotto has a "rewards card" program where customers can get 10% off every 5th time they eat at the restaurant. To signup for the rewards program, customers must fill out an online application that collects key information about the customer. You want to keep track of four entities: (1) the menu items that the restaurant sells, (2) customers who place the orders, (3) the orders that are placed, and (4) the servers who take the orders and serve the food. Draw an ERD diagram and use the following information to help guide your drawing: The database should keep track of all menu items that the restaurant offers for sale The database should keep track of all customers who have joined the rewards card program The database should keep track of all restaurant orders the database should keep track of all servers employed by the restaurant Each order may have at most one rewards card program customer associated with it Each order must have one server associated with it On slow days servers may serve no customers, and on busy days servers may serve many customers An order must consist of at least one menu item, and may consist of multiple menu item Popular menu items can be ordered a lot, and unpopular menu items may not be ordered at all Each entity must have a unique identifier within its table. This is the Entity's/table's Primary Key. Each entity needs to keep track of specific attributes. The attributes are listed below, but you must determine which entity they belong to: Popular menu items can be ordered a lot, and unpopular menu items may not be ordered at all Each entity must have a unique identifier within its table. This is the Entity's/table's Primary Key. Each entity needs to keep track of specific attributes. The attributes are listed below, but you must determine which entity they belong to: o You want to keep track of the cost of the menu item to the restaurant, and the price that the restaurant sells that menu item to the customer o You want to be able to contact customers via phone and email address o You want to be able to send a digital birthday card to your customers on their birthday. o You want to keep track of the number of visits that a rewards program customer has visited the restaurant so that you can give them the appropriate discount. o You want to keep track of the date that each order occurred, as well as the subtotal, tax, and total dollar amount of the order Your drawing should include the following: 1. The entities you wish to model 2. The required/important attributes for each entity (refer to the instructions above for guidance on what is required/important) 3. The relationships between the entities 4. The correct MAX and MIN Cardinalities for each relationship (remember for each relationship, or line, there are MAX/MIN cardinalities on each side of the relationship) 5. One-to-Many and Many-to-Many relationships, graphically represented in ERDs as a line between entities, can also be represented using Primary and Foreign Keys, i.e. listing a Primary Key from one table and including it as an attribute in a table that you wish to connect to. Choose a One-to-Many relationship in your diagram (a line that connects two entities), and represent that relationship, using a Primary and Foreign Key to do so. Clearly label the "1:N" relationship you are doing this for. Do NOT attempt this for any Many-to-Many relationships you may have in your diagram. Please let me know if you have any questions or need any assistance. Happy Drawing!