• Create an ERD that includes the tables, fields, and relationships identified at the end of the database normalization process.
• Include appropriate metadata about the database components in the ERD, including primary and foreign keys, data types, and nullability of individual fields.

For the scenario outlined below:

1. Identify at least two major entities and their initial attributes. (Some scenarios may require more entities in the first step.)

2. Normalize all entities to 3NF.

3. Identify places in the design that may not meet 3NF requirements and justify your choice for those places.

4. Create a final, normalized ERD that includes:

   • All tables and fields you identified in the normalization process
   • Primary and foreign key identification
   • Required fields for each table
   • General data type for each field

5. Use a standard naming convention. You are encouraged to use the naming conventions used elsewhere in this module, but you should be consistent across tables and fields in the final version of the ERD.

SCENARIO:

Design a database for a pet shop. It must include:

• Information about the doctors in the practice, including name, types of pets they treat, and when they joined the practice.
• Pet owner information, including name, mailing address, phone number, and email address.
• Pet information, including the name of the pet, who owns the pet, what kind of pet it is, its birthdate, and its vaccination records.