1. Jessica Johnson, Louie Livon-Bemel

2. Question 1 When converting a narrative requirements document into an ERD, which of the following would potentially be converted into an entity type? D. All of the above, because entity types are converted from nouns, which are things, places, and events. Ex. Thing: Dog, Student. Places: Building, Room, City. Events: Transactions, Purchases.

3. Question 2 When converting a narrative requirements document into an ERD, which of the following would potentially be converted into a relationship type: B. Verbs and prepositions. A relationship type is how two things relate. For example, Customer purchases Car, Owner feeds Dog. The relationships are purchases and feeds, which are verbs.

4. Question 3 When converting a narrative requirements document into an ERD: C. You can usually derive both relationships and cardinalities. However, it may only be possible to derive the maximum cardinality from a narrative requirements document.

5. Question 4 In data modeling, which is true? D. All of the above. More than one alternative may exist, because there are different ways to represent data. Additional information may be needed, however, before deciding whether an alternative is the best choice or not. We discussed that the process is either iterative or repetitive.

6. Question 5 Redundant relationships in a database design: C. Should always be removed from the database design. This is due to the fact that redundant relationships can complicate your database and can cause errors when attempting to delete data from your database. For example, when deleting a year from a car and from the owner of the car, but not the year of the car in the dealership.

7. Question 6 How can you reduce the number of relationships in an initial ERD? Create a central entity that all other entities relate to and depend on. This removes relationships between non- primary entities and simplifies the table.