1. The scenario involves storing information related to a Real Estate Office. The database will store information about completed sales only a. Stored information about each real estate agent including name (First, MI, Last), home address, phone and SSN b. Each agent must handle many sellers c. Stored information about the seller includes name, address and phone number d. Each seller will own only one piece of real estate and be represented by one agent e. Each piece of real estate will have an address, county lot number and sale price f. Each piece of real estate will be one of two types, private home or condominium g. For each piece of real estate that is a private home we will store lot size, pool (yes or no) h. For each piece of real estate that is a condominium will store association name and management company name i. We need to store information about the commission the house sold for j. The commission is based on the sale price of the piece of real estate along with an agreement made between the seller and the agent I. The company wants to store information about hobbies that the real estate agents have m. Dependent information includes name (first last and MI), DOB and relationship n. An agent may have an infinite number for dependents; however each dependent must be related to only one existing agent o. The customer does not what extensive null or use of flags when mapping the Real Estate information. (hint don't use Mapping rule 17 or 18) I. Draw an Entity Relationship diagram depicting this scenario. ONLY map the entities and relationship having to do with the sale of a home and dependents of Agents. 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 II. Write the structure English for the real estate entity(the piece of property), include the English for a one of the attributes and the key. Additionally write the structured English for every relationship in your diagram including any relational attributes III. Map the Entities and the relationships to a relational database. There is not need to show any data just table name and field names ER Mapping Rules Steps 1. Map the strong entities 2. Map the weak entities 3. Map the binary M:N relationships 4. Map the binary 1:1 relationships the primary Key/foreign key method 5. Map the binary 1:N relationships 6. Map recursive relationships 7. Map the n-ary relationships 8. Map generalizations/specializations 9. Mapping rule 17 and 18 address mapping the generalize/specialize data in one table with the possibility of many nulls