First go to File Make a Copy The following is a small sample of the Hogle Zoo file system that they use to track data for the program. Hogle Zoo Sample File System Scenario: Hogle Zoo wants to maintain information about its animals, the enclosures in which they live (all animals must be in an enclosure), its zookeepers, and the services they perform for the animals. Each time a zookeeper performs a specific, significant service for an animal the service type, date, and time are recorded. The zoo would also like to keep track of all zookeeper certifications. 1. - Using the scenario and file system create a Conceptual Data Relation Diagram similar to the one created in the try it out. The conceptual diagram should include all entities identified in the scenario. Your conceptual diagram should be drawn electronically (preferred) or by hand (take a photo and embed the readable images). - Make sure to use a star for the attribute that will uniquely identify the data. - A description of the relationship between the entities should be included. - Here are two entities and their attributes that will help you get started: Remember, each relation model (Entity Set) should be independent and store data for only one type of (thing, person, place, object, etc). Further, each of the data entities should include the attributes that will be the data stored in that entity. Attributes should store only one value (although that value can change over time). For example, in the sample image, the Data Relation called "Student" stores only facts about a particular student and nothing else. Its attributes hold only one fact (imagine you had a paper form and asked the student to fill out their data where they gave one answer to each attribute - like "What is your FirstName? (single answer only)", "What is your Date of Birth?", etc. Store data (not information). For instance, do not store age as data, but rather DateofBirth, because age is information that can be calculated or derived from raw data being stored. Focus on attributes for data storage only. When diagramming, make sure you follow proper naming conventions (singular names, and no spaces), and property identify () the unique attribute(s) used to identify each row in the relation. Connect the relation models, and use verbs to describe their associations (relationships). Using the Entity Relationship Diagram on the following page answer the following questions: 2. Describe what an ERD is and how it is helpful. ANSWER 3. What is the primary key in the Flight table? ANSWER 4. What Foreign Keys are in the Schedule table? ANSWER 5. Describe the relationship reading it both ways between Airport and Gate. ANSWER 6. Describe the relationship reading it both ways between Seat and Seat Type. AN SWER 7. What field(s) is not required in the Seat table? ANSWER First go to File Make a Copy The following is a small sample of the Hogle Zoo file system that they use to track data for the program. Hogle Zoo Sample File System Scenario: Hogle Zoo wants to maintain information about its animals, the enclosures in which they live (all animals must be in an enclosure), its zookeepers, and the services they perform for the animals. Each time a zookeeper performs a specific, significant service for an animal the service type, date, and time are recorded. The zoo would also like to keep track of all zookeeper certifications. 1. - Using the scenario and file system create a Conceptual Data Relation Diagram similar to the one created in the try it out. The conceptual diagram should include all entities identified in the scenario. Your conceptual diagram should be drawn electronically (preferred) or by hand (take a photo and embed the readable images). - Make sure to use a star for the attribute that will uniquely identify the data. - A description of the relationship between the entities should be included. - Here are two entities and their attributes that will help you get started: Remember, each relation model (Entity Set) should be independent and store data for only one type of (thing, person, place, object, etc). Further, each of the data entities should include the attributes that will be the data stored in that entity. Attributes should store only one value (although that value can change over time). For example, in the sample image, the Data Relation called "Student" stores only facts about a particular student and nothing else. Its attributes hold only one fact (imagine you had a paper form and asked the student to fill out their data where they gave one answer to each attribute - like "What is your FirstName? (single answer only)", "What is your Date of Birth?", etc. Store data (not information). For instance, do not store age as data, but rather DateofBirth, because age is information that can be calculated or derived from raw data being stored. Focus on attributes for data storage only. When diagramming, make sure you follow proper naming conventions (singular names, and no spaces), and property identify () the unique attribute(s) used to identify each row in the relation. Connect the relation models, and use verbs to describe their associations (relationships). Using the Entity Relationship Diagram on the following page answer the following questions: 2. Describe what an ERD is and how it is helpful. ANSWER 3. What is the primary key in the Flight table? ANSWER 4. What Foreign Keys are in the Schedule table? ANSWER 5. Describe the relationship reading it both ways between Airport and Gate. ANSWER 6. Describe the relationship reading it both ways between Seat and Seat Type. AN SWER 7. What field(s) is not required in the Seat table
