1. The scenario involves storing information related to a warehouse. We will store information about the warehouse regardless of the state of any other entities in our database a. We need to store the name of the warehouse, its location and a business license number. b. The warehouse contains many items of merchandise. c. Each item has a name and bar-code. d. Only items in the warehouse will be stored in the database e. Items must be made by a manufacturer; however each item may be made by more than one manufacturer. f. Only manufactures with items in the warehouse will be stored in the database. g. Each manufacture may manufacture multiple items. h. We need to know the manufactures, name, address (street, city, state and zip) and phone number. We would like to be able to sort the manufactures by city and state as needed. i. Due to union rules, we use one trucking company to ship our merchandise to customers. We will not store any data on j. We need our trucking company's business number, phone number and name. I. Draw an Entity Relationship diagram depicting this scenario. Include entities, attributes and relationships as well as structural constraints (cardinality and participation). Denote any primary or candidate keys. Remember to review specific requirements denoted in the scenario above, however, if you make any assumptions not covered in the scenario, note and explain them. Only submit the final diagram there is no need to submit multiple diagrams that show the iteration of the ER process. Treat this as your final submission to the development team. (20 Points) II. Write the structure English for one entity, include the English for two and only two attributes of different types (atomic, composite, multi-valued or derived) and a key. Additionally write the structured English for every relationship in your diagram (13 points) III. Map the Entities and the relationships to a relational database. Remember mapping must include showing the relationships. There is not need to show any data just table name and field names. example Employee(empid, empname