Chapter 3 Data Modeling Using the Entity-Relationship Model
FIGURE 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 e 1  and company c 1 , 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 EMPLOY...
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  subord...
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.
Upcoming SlideShare
Loading in …5
×

En Ch03 Figs

1,196 views
993 views

Published on

1 Comment
0 Likes
Statistics
Notes
  • Be the first to like this

No Downloads
Views
Total views
1,196
On SlideShare
0
From Embeds
0
Number of Embeds
18
Actions
Shares
0
Downloads
28
Comments
1
Likes
0
Embeds 0
No embeds

No notes for slide

En Ch03 Figs

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

×