For this assignment, we are going to design a database for a company that sells dog food online. This company already has a sales component, but really wants to track recommendations and preferences for its customers. Currently, they are trying to do this with 2 spreadsheets with the following columns: Customer (CID, C Name, C Address, C Phone#, C Email, Dog Name, Dog Gender, Dog Height, Dog Weight, Breed Name, Max Height, Min Height, Max Weight, Min Weight) Food (Food Name, Package weight, Manufacturer Name, M Phone#, Good For Breed Name, Ranking) There are many problems with these spreadsheets; here are a few I have been told about already. There is much repetition of data-several customers have more than one dog, also a food may be good" for more than one dog: the Breed Max/Min values are gender specific; this goes on. Also, they have told me they would like to track which food a customer has ordered for his/her dog in the past and also what is their current choice of food as well as to record if a customer has a favorite manufacturer I asked if it was OK for me to have you take a look at it and they agreed. I told them you would need to rearrange the data into more than 2 tables and you may need to add some new columns in the end. They said this was permissible to an extent, but they are adamantly opposed to adding any type of number to a dog -they believe every dog should be known only by its name Your task is to build a database for this enterprise using the Entity Relationship Model. Specifically, upon completion of this design, I want you to turn in the following: . A list of entities (with their attributes) and a list of relationships. You will need to write a short paragraph describing each entity (be sure to be specific about what attributes are unique). A brief description of each relationship is required as well 2. An E-R Diagram for your system, complete with the mapping labels. 3. A set of tables derived from your E-R Diagram. Give the name of each table along with its columns. Make SURE the set of attributes of your tables is a separate listing from your list of entity attributes. Also, make sure you describe how the set of tables was derived from the E-R diagram, if it is not part of the normal algorithm. Highlight the primary key and any foreign