In Chapter 4, you developed a domain model class diagram. Using your previous solution, update your domain model class diagram with any additional problem domain classes, new associations, or additional attributes that you have discovered as you worked toward your solutions in the previous chapters. Finalize this comprehensive domain model and then turn it in as part of your solution. Using this comprehensive domain model class diagram, develop a relational database schema. In the schema, identify the foreign keys that are required. Also, identify a key attribute for each table. You may need to add a key field if there isn’t an attribute that could logically serve as the key. Remember that a candidate key for an association class is the combination of the keys of the connected classes. However, it may make sense to define a shorter, more concise key field. 1) Verify that each table is in first, second, and third form. 2) Discuss any discrepancies you had to fix from your first solution. 3) Discuss any tables that aren’t in third normal form and why you are leaving them as non-normalized. (For example, in the United States, city and state are functionally dependent on zip code, but you might leave all here fields in the same table. Why? )