The following incomplete list of business rules describe the relationships between some of the different types of food businesses available.

Restaurants can be diners, pizzerias, delis, or none of these.

Restaurants and grocery stores are food businesses, but not all food businesses are restaurants or grocery stores.

Some delis and pizzerias are take-out restaurants.

Some restaurants are sit-down only restaurants, but not all restaurants are sit-down only.

Supermarkets and supercenters are grocery stores, but not all grocery stores are supermarkets or supercenters.

Food manufacturers are food businesses, and can be canneries, packaging plants, both or neither.

All relationships described in these rules are specialization-generalization relationships. These rules also reflect the entities and relationships that exist in the real-world.

1. Create a complete list of business rules that are consistent with the incomplete list given above. Try to order the rules logically, either starting at the bottom of the hierarchy working upward, or from the top of the hierarchy working downward. This list should make provision for all entities and relationships given in the above list, and there can be many solutions that do so correctly.

2. Develop an extended entity-relationship diagram (EERD) that illustrates the relational database design described by the business rules in #1. The diagram should include the primary key of each table in order to demonstrate correct implementation of specialization-generalization. While EERDs may well contain other attributes, in this assignment you need not include them because they are not described in the business rules. You should use legal database identifiers such as Sit_Down_Restaurants or Food_Manufacturers in your EERD. you need to make the EERD please