1. 1 Chapter 4 Logical Database Design and the Relational Model Jason C. H. Chen, Ph.D. Professor of MIS School of Business Administration Gonzaga University Spokane, WA 99258 chen@gonzaga.edu

2. 2 #1-I(a), p.193 #1-I(b)

3. Fig. 2-11: An associative entity (p. 78) (a) Attribute on a relationship (Link Attribute/Associative) #1-I (c)

4. 4 EmployeeiDEmployeeName EMPLOYEE EmployeeIDCourseID DateCompleted CERTIFICATE COURSE CourseIDCourseTitle #1-I (c) BirthDate

5. Answer to: #1- I (c)

6. 6 #1-III(c) 3NF

7. 7 #2-III-a (p.193) – from Fig3-6b (p. 121)

8. 8 #2-III-b (p.193) from Fig. 3-7a (p.122)

9. 9 #2-III-c (p.193) – from Fig.3-9 (p.124)

10. 10 #2-III-d (p.193) – from Fig. 3-10 (p.125)

11. 11 b. 3NF c. 2NF CLASS (CourseNo, SectionNo, Room) ROOM (Room, Capacity) d. 1NF COURSE (CourseNo, CourseName) CLASS (CourseNo, SectionNo, Room) ROOM (Room, Capacity) a. 3NF 3. The normal form for the relations are: (make sure that you know why and how to transform it to 3NF)

12. 12 7. Transforming Table 4-3 to relations: (p194) Part_No Description 1234 5678 Logic Chip Memory Chip Vendor_Name Fast Chips Smart Chips Fast Chips Quality Chips Smart Chips Cupertino Phoenix Cupertino Austin Phoenix Unit_CostAddress 10.00 8.00 3.00 2.00 5.00 a) PART SUPPLIER b) Part_No Vendor_Name Part_No, Vendor_Name Description Address Unit_Cost Insert anomaly: we cannot insert a new vendor unless we also include a part number. Delete anomaly: if we delete part information, we also lose information about a vendor who supplies that part. Modification anomaly: if a vendor address changes, we have to modify all records (or rows) for that vendor. c)

13. 13 7. d) Part_NoDescriptionVendor_NameAddressUnit_Cost e) 1NF f) Part_NoDescription Part_NoVendor_NameUnit_Cost Vendor_NameAddress PART SUPPLIER

14. 14 7. g)

15. 15 8. a) b) 1NF partial dep. transitive dep.

16. 16 8. c) 3NF after remove partial & transitive dep.

17. 17 8. d) 3NF after remove partial & transitive dep.

18. 18 8. e) Using MS/Visio