E/R and UML Diagram

Cruise Ship management database system
The following data model is designed to hold customer ordering information relating to a restaurant chain. For this scenario we need to define the following facts:
These facts define the requirements which the Database must meet and should be agreed between the Database User and the Database Designer prior to physical creation. Assuming that the restaurant chain has restaurants in many locations throughout the United States and each restaurant has employees and food items to offer:
 Restaurants – A restaurant may have location information, phone number, etc.
 Employees - An Employee may have information such as address, phone, DOB, etc.
 Menu items – name, price. e.g. Hamburger, $3.50
 Customers – Name, address (for delivery purpose), payment method. etc.
A customer may visit multiple restaurants in the chain.
The Entities are related as follows:
 Customers may order menu items from various restaurant locations.
 Restaurants can have various kinds of menu items.
 A customer may write feedback to a restaurant

When asking questions of the database we may need to know:
1. Which customer ordered which items in which location?

a) Create an E/R diagram capturing the objects and relationships described
above. Describe all your design choices and constraints.


THEN


b) Create an UML diagram capturing the objects and relationships described
above. Describe all your design choices and constraints.