PowerPoint PresentationChapter 3FIGURE 3.1 A simplified diagram to illustrate the main phases of database design.FIGURE 3.2 An ER schema diagram for the COMPANY database.FIGURE 3.3 Two entities, employee e1 and company c1, and their attributes.FIGURE 3.4 A hierarchy of composite attributes.FIGURE 3.5 A complex attribute: AddressPhone.FIGURE 3.6 Two entity types, EMPLOYEE and COMPANY, and some member entities of each.FIGURE 3.7 The CAR entity type with two key attributes, Registration and VehicleID.FIGURE 3.8 Preliminary design of entity types for the COMPANY database.FIGURE 3.9 Some instances in the WORKS_FOR relationship set, which represents a relationship type WORKS_FOR between EMPLOYEE and DEPARTMENT.FIGURE 3.10 Some relationship instances in the SUPPLY ternary relationship set.FIGURE 3.11 A recursive relationship SUPERVISION between EMPLOYEE in the supervisor role (1) and EMPLOYEE in the subordinate role (2).FIGURE 3.12 A 1:1 relationship, MANAGES.FIGURE 3.13 An M:N relationship, WORKS_ON.FIGURE 3.14 Summary of the notation for ER diagrams.FIGURE 3.15 ER diagrams for the COMPANY schema, with structural constraints specific using (min, max) notation.FIGURE 3.16 The COMPANY conceptual scheme in UML class diagram notation.FIGURE 3.17 An ER diagram for an AIRLINE database schema.FIGURE 3.18 An ER diagram for a BANK database schema.FIGURE 3.19 Part of an ER diagram for a COMPANY database.FIGURE 3.20 Part of an ER diagram for a COURSES database.Copyright © 2004 Pearson Education, Inc.Copyright © 2004 Pearson Education, Inc.Chapter 3Data Modeling Using the Entity-Relationship ModelSlide 3-3Elmasri and Navathe, Fundamentals of Database Systems, Fourth EditionCopyright © 2004 Pearson Education, Inc. FIGURE 3.1A simplified diagram to illustrate the main phases of database design.Slide 3-4Elmasri and Navathe, Fundamentals of Database Systems, Fourth EditionCopyright © 2004 Pearson Education, Inc. FIGURE 3.2An ER schema diagram for the COMPANY database.Slide 3-5Elmasri and Navathe, Fundamentals of Database Systems, Fourth EditionCopyright © 2004 Pearson Education, Inc. FIGURE 3.3Two entities, employee e1 and company c1, and their attributes.Slide 3-6Elmasri and Navathe, Fundamentals of Database Systems, Fourth EditionCopyright © 2004 Pearson Education, Inc. FIGURE 3.4A hierarchy of composite attributes.Slide 3-7Elmasri and Navathe, Fundamentals of Database Systems, Fourth EditionCopyright © 2004 Pearson Education, Inc. FIGURE 3.5A complex attribute: AddressPhone.Slide 3-8Elmasri and Navathe, Fundamentals of Database Systems, Fourth EditionCopyright © 2004 Pearson Education, Inc. FIGURE 3.6Two entity types, EMPLOYEE and COMPANY, and some member entities of each.Slide 3-9Elmasri and Navathe, Fundamentals of Database Systems, Fourth EditionCopyright © 2004 Pearson Education, Inc. FIGURE 3.7The CAR entity type with two key attributes, Registration and VehicleID.Slide 3-10Elmasri and Navathe, Fundamentals of Database Systems, Fourth EditionCopyright © 2004 Pearson Education, Inc. FIGURE 3.8Preliminary design of entity types for the COMPANY database.Slide 3-11Elmasri and Navathe, Fundamentals of Database Systems, Fourth EditionCopyright © 2004 Pearson Education, Inc. FIGURE 3.9Some instances in the WORKS_FOR relationship set, which represents a relationship type WORKS_FOR between EMPLOYEE and DEPARTMENT.Slide 3-12Elmasri and Navathe, Fundamentals of Database Systems, Fourth EditionCopyright © 2004 Pearson Education, Inc. FIGURE 3.10Some relationship instances in the SUPPLY ternary relationship set.Slide 3-13Elmasri and Navathe, Fundamentals of Database Systems, Fourth EditionCopyright © 2004 Pearson Education, Inc. FIGURE 3.11A recursive relationship SUPERVISION between EMPLOYEE in the supervisor role (1) and EMPLOYEE in the subordinate role (2).Slide 3-14Elmasri and Navathe, Fundamentals of Database Systems, Fourth EditionCopyright © 2004 Pearson Education, Inc. FIGURE 3.12A 1:1 relationship, MANAGES.Slide 3-15Elmasri and Navathe, Fundamentals of Database Systems, Fourth EditionCopyright © 2004 Pearson Education, Inc. FIGURE 3.13An M:N relationship, WORKS_ON.Slide 3-16Elmasri and Navathe, Fundamentals of Database Systems, Fourth EditionCopyright © 2004 Pearson Education, Inc. FIGURE 3.14Summary of the notation for ER diagrams.Slide 3-17Elmasri and Navathe, Fundamentals of Database Systems, Fourth EditionCopyright © 2004 Pearson Education, Inc. FIGURE 3.15ER diagrams for the COMPANY schema, with structural constraints specific using (min, max) notation.Slide 3-18Elmasri and Navathe, Fundamentals of Database Systems, Fourth EditionCopyright © 2004 Pearson Education, Inc. FIGURE 3.16The COMPANY conceptual scheme in UML class diagram notation.Slide 3-19Elmasri and Navathe, Fundamentals of Database Systems, Fourth EditionCopyright © 2004 Pearson Education, Inc. FIGURE 3.17An ER diagram for an AIRLINE database schema.Slide 3-20Elmasri and Navathe, Fundamentals of Database Systems, Fourth EditionCopyright © 2004 Pearson Education, Inc. FIGURE 3.18An ER diagram for a BANK database schema.Slide 3-21Elmasri and Navathe, Fundamentals of Database Systems, Fourth EditionCopyright © 2004 Pearson Education, Inc. FIGURE 3.19Part of an ER diagram for a COMPANY database.Slide 3-22Elmasri and Navathe, Fundamentals of Database Systems, Fourth EditionCopyright © 2004 Pearson Education, Inc. FIGURE 3.20Part of an ER diagram for a COURSES
View Full Document