Create a logical ERD for each of the problems on the following pages using the crowsfoot notation discussed in class. Be sure that each entity has the entity name at the top of the box, the primary key attribute, or attributes in the middle of the box, and the non-key attributes in the bottom of the box. Lines should separate each part of the entity box. Follow these instructions about each ERD:

• The ERD should not have any many-to-many (M:N) relationships.
• All attributes should be placed within an entity.
• Each entity must have a primary key defined. A primary key may consist of one or more attributes.
• Each relationship must have a foreign key. Denote the foreign key(s) with the notation (FK) on the ERD. It is not necessary to number the foreign keys, but if you do that would be nice.
• Each relationship must include both a maximum and minimum cardinality for both sides of the relationship.
• Each relationship must have a relationship verb.
• Remember that 1:1 relationships are rare. Make sure that you carefully scrutinize any 1:1 relationships to ensure that they are actually 1:1.

Question #4. Use the business rules below to identify and write all appropriate relationships and cardinalities between the entities shown on the next page. Also include primary keys and foreign keys for each entity. Do not add any entities to the diagram.

The data model shown on the next page depicts the entities required for a customer ordering system at a pizza restaurant. A few of the attributes and primary keys have been included on this model to get you started.

This system accepts orders from customers for such menu items as pizza, ravioli, calzones, etc. This is a take-out or eat in restaurant. The restaurant keeps customer information in order to make deliveries of orders to the customer's home (or business).

1. An order is placed by only one customer. A customer is capable of placing many orders.
2. A customer is kept in the system whether or not an order for that customer is currently part of the system.
3. An employee accepts an order that is placed by a customer. An employee may accept zero or many orders, but an order is accepted by only one employee. It is possible that an order is placed directly by a customer over the phone but the customer and employee information is still stored with that order.
4. An employee delivers the order if the order is supposed to be delivere An employee may deliver zero or many orders. The employee who accepts the order may or may not be the same employee who delivers the order. The company wants to keep track of the employee who delivers an order.
5. A menu item is an item such as a pizza or an order of ravioli. An order may have more than one menu item and each menu item may be on more than one order, so the intersection between the two is an orderlin An order has at least one order line and may possibly have many order lines. An order line is composed of one and only one menu item. A given menu item may be on many order lines.
6. A menu item is made up of one or more ingredients. A menu item must use at least one ingredient.
7. An ingredient can be used in more than one menu item. An ingredient must be used on at least one menu item to be considered part of the system.

ZOOM + L Customer PK customer customername customerphone Order Orderline Menuitem PK menuitemID PK orderi orderdate quantityordered description price Employee PK employeel name Ingredient ItemIngredient PK ingredienti description cost quantityrequired Restawrant Delivery ERDI