ERD and Database Design

Johnnies Corner Store carries various products for neighborhood people to buy including homemade meals to go.

Example: Visualize you are hungry and call in an Order that contains two (2) Menu_Item:

French fries with ketchup and

Chicken sandwich on wheat pita bread with lettuce and tomatoes.

Both french fries and the chicken sandwich contain multiple Ingredient that can also be used with other Menu_Item such as a roast beef sandwich on wheat pita bread with tomato the wheat pita bread and the tomato are both used in the chicken and roast beef sandwiches. To keep Ingredient in stock, multiple Supplier are used to provide for example, tomato.

Part 1: Create an ERD that follows these rules:

An Order can contain 1 or many Menu_Item.

Similarly, a Menu_Item can be on 1 or many Order.

A Menu_Item contains 1 or many Ingredient and an Ingredient is on 1 or many Menu_Item.

An Ingredient can be provided by 1 or many Supplier and a Supplier can provide 1 or many Ingredient.

Each entity should have a minimum of 3 attributes that makes sense.

Identify the primary keys (underline or use the abbreviation PK).

Draw the cardinalities (relationships) between the entities. Hint: all relationships have a minimum and maximum cardinality.

You can hand draw your ERD

Part 2: Now convert your ERD to a Database Design

All tables must have at least three fields.

Please identify all primary keys (underline or use the abbreviation PK).

For intermediately table(s), please identify the primary key(s) and any ADDITIONAL foreign keys that make sense label foreign keys as FK.

In the intermediary table you must add at least one additional new field that make sense for tracking, reporting and analysis purposes.

You can hand draw your Database Design