1. CHAPTER 3: THE ENHANCED E-R MODEL © 2013 Pearson Education, Inc. Publishing as Prentice Hall 1 Modern Database Management 11 th Edition Jeffrey A. Hoffer, V. Ramesh, Heikki Topi

2. Chapter 3 © 2013 Pearson Education, Inc. Publishing as Prentice Hall OBJECTIVES  Define terms  Understand use of supertype/subtype relationships  Understand use of specialization and generalization techniques  Specify completeness and disjointness constraints  Develop supertype/subtype hierarchies for realistic business situations  Develop entity clusters  Explain universal (packaged) data model  Describe special features of data modeling project using packaged data model 2

3. Chapter 3 © 2013 Pearson Education, Inc. Publishing as Prentice Hall  Basic E-R Model  pushing 40 years old  complex data relationships and new database technology have outgrown it in some respects  Enhanced E-R Model  a response to the shortcomings of the basic E-R model  not universally agreed upon in some respects  introduced the supertype/subtype relationship

4. Chapter 3 © 2013 Pearson Education, Inc. Publishing as Prentice Hall SUPERTYPES AND SUBTYPES  Enhanced ER model: extends original ER model with new modeling constructs  Subtype: A subgrouping of the entities in an entity type that has attributes distinct from those in other subgroupings  Supertype: A generic entity type that has a relationship with one or more subtypes  Attribute Inheritance:  Subtype entities inherit values of all attributes of the supertype  An instance of a subtype is also an instance of the supertype 4

5. 5 Figure 3-1 Basic notation for supertype/subtype notation a) EER notation 5 Chapter 3 © 2013 Pearson Education, Inc. Publishing as Prentice Hall

6. 6 Different modeling tools may have different notation for the same modeling constructs. b) Microsoft Visio Notation Figure 3-1 Basic notation for supertype/subtype notation (cont.) 6 Chapter 3 © 2013 Pearson Education, Inc. Publishing as Prentice Hall

7. 7 Figure 3-2 Employee supertype with three subtypes All employee subtypes will have employee number, name, address, and date hired Each employee subtype will also have its own attributes 7 Chapter 3 © 2013 Pearson Education, Inc. Publishing as Prentice Hall

8. Chapter 3 © 2013 Pearson Education, Inc. Publishing as Prentice Hall RELATIONSHIPS AND SUBTYPES  Relationships at the supertype level indicate that all subtypes will participate in the relationship  The instances of a subtype may participate in a relationship unique to that subtype. In this situation, the relationship is shown at the subtype level 8

9. Chapter 3 © 2013 Pearson Education, Inc. Publishing as Prentice Hall  Use this type of relationship when either (or both) of the following are present:  When there are attributes that apply to some (but not all) of the instances of an entity type  When the instances of a subtype participate in a relationship unique to that subtype

10. Chapter 3 © 2013 Pearson Education, Inc. Publishing as Prentice Hall  The property by which subtype entities inherit values of all attributes of the supertype.  This important property makes it unnecessary to include supertype attributes redundantly with the subtypes.

11. 11 Figure 3-3 Supertype/subtype relationships in a hospital 11 Chapter 3 © 2013 Pearson Education, Inc. Publishing as Prentice Hall

12. Chapter 3 © 2013 Pearson Education, Inc. Publishing as Prentice Hall  Generalization: The process of defining a more general entity type from a set of more specialized entity types. BOTTOM-UP  Specialization: The process of defining one or more subtypes of the supertype and forming supertype/subtype relationships. TOP-DOWN 12

13. 13 Figure 3-4 Example of generalization a) Three entity types: CAR, TRUCK, and MOTORCYCLE All these types of vehicles have common attributes 13 Chapter 3 © 2013 Pearson Education, Inc. Publishing as Prentice Hall

14. 14 Figure 3-4 Example of generalization (cont.) So we put the shared attributes in a supertype Note: no subtype for motorcycle, since it has no unique attributes b) Generalization to VEHICLE supertype 14 Chapter 3 © 2013 Pearson Education, Inc. Publishing as Prentice Hall

15. 15 Figure 3-5 Example of specialization a) Entity type PART Only applies to manufactured parts Applies only to purchased parts 15 Chapter 3 © 2013 Pearson Education, Inc. Publishing as Prentice Hall

16. 16 b) Specialization to MANUFACTURED PART and PURCHASED PART Note: multivalued composite attribute was replaced by an associative entity relationship to another entity Created 2 subtypes Figure 3-5 Example of specialization (cont.) 16 Chapter 3 © 2013 Pearson Education, Inc. Publishing as Prentice Hall

17. Chapter 3 © 2013 Pearson Education, Inc. Publishing as Prentice Hall  Completeness Constraints: Whether an instance of a supertype must also be a member of at least one subtype  Total Specialization Rule: Yes (double line)  Partial Specialization Rule: No (single line) 17

18. Figure 3-6 Examples of completeness constraints a) Total specialization rule 18 Chapter 3 © 2013 Pearson Education, Inc. Publishing as Prentice Hall

19. 19 b) Partial specialization rule Figure 3-6 Examples of completeness constraints (cont.) 19 Chapter 3 © 2013 Pearson Education, Inc. Publishing as Prentice Hall

20. Chapter 3 © 2013 Pearson Education, Inc. Publishing as Prentice Hall  Disjointness Constraints: Whether an instance of a supertype may simultaneously be a member of two (or more) subtypes  Disjoint Rule: An instance of the supertype can be only ONE of the subtypes  Overlap Rule: An instance of the supertype could be more than one of the subtypes 20 Chapter 3 © 2013 Pearson Education, Inc. Publishing as Prentice Hall

21. 21 a) Disjoint rule Figure 3-7 Examples of disjointness constraints 21 Chapter 3 © 2013 Pearson Education, Inc. Publishing as Prentice Hall

22. 22 b) Overlap rule Figure 3-7 Examples of disjointness constraints (cont.) 22 Chapter 3 © 2013 Pearson Education, Inc. Publishing as Prentice Hall

23. Chapter 3 © 2013 Pearson Education, Inc. Publishing as Prentice Hall  Subtype Discriminator: An attribute of the supertype whose values determine the target subtype(s)  Disjoint – a simple attribute with alternative values to indicate the possible subtypes  Overlapping – a composite attribute whose subparts pertain to different subtypes. Each subpart contains a Boolean value to indicate whether or not the instance belongs to the associated subtype 23 Chapter 3 © 2013 Pearson Education, Inc. Publishing as Prentice Hall

24. Chapter 3 © 2013 Pearson Education, Inc. Publishing as Prentice Hall Attribute of the supertype whose value determines to which subtype an instance belongs

25. 25 Figure 3-8 Introducing a subtype discriminator ( disjoint rule) 25 Chapter 3 © 2013 Pearson Education, Inc. Publishing as Prentice Hall

26. 26 Figure 3-9 Subtype discriminator ( overlap rule) 26 Chapter 3 © 2013 Pearson Education, Inc. Publishing as Prentice Hall

27. 27 Figure 3-10 Example of supertype/subtype hierarchy 27 Chapter 3 © 2013 Pearson Education, Inc. Publishing as Prentice Hall

28. Chapter 3 © 2013 Pearson Education, Inc. Publishing as Prentice Hall  EER diagrams are difficult to read when there are too many entities and relationships.  Solution: Group entities and relationships into entity clusters.  Entity cluster: Set of one or more entity types and associated relationships grouped into a single abstract entity type 28

29. Chapter 3 © 2013 Pearson Education, Inc. Publishing as Prentice Hall 29 Figure 3-13a Possible entity clusters for Pine Valley Furniture in Microsoft Visio Related groups of entities could become clusters

30. 30 Figure 3-13b EER diagram of PVF entity clusters More readable, isn’t it? 30 Chapter 3 © 2013 Pearson Education, Inc. Publishing as Prentice Hall

31. 31 Figure 3-14 Manufacturing entity cluster Detail for a single cluster 31 Chapter 3 © 2013 Pearson Education, Inc. Publishing as Prentice Hall

32. Chapter 3 © 2013 Pearson Education, Inc. Publishing as Prentice Hall  Predefined data models  Could be universal or industry-specific  Universal data model = a generic or template data model that can be reused as a starting point for a data modeling project (also called a “pattern”) 32

33. Chapter 3 © 2013 Pearson Education, Inc. Publishing as Prentice Hall ADVANTAGES OF PACKAGED DATA MODELS  Use proven model components  Save time and cost  Less likelihood of data model errors  Easier to evolve and modify over time  Aid in requirements determination  Easier to read  Supertype/subtype hierarchies promote reuse  Many-to-many relationships enhance model flexibility  Vendor-supplied data model fosters integration with vendor’s applications  Universal models support inter-organizational systems 33

34. 34 Packaged data models are generic models that can be customized for a particular organization’s business rules. Figure 3-15 PARTY, PARTY ROLE, and ROLE TYPE in a universal data model (a) Basic PARTY universal data model 34 Chapter 3 © 2013 Pearson Education, Inc. Publishing as Prentice Hall

35. 35 Figure 3-15 PARTY, PARTY ROLE, and ROLE TYPE in a universal data model (b) PARTY supertype/subtype hierarchy 35 Chapter 3 © 2013 Pearson Education, Inc. Publishing as Prentice Hall

36. 36 Copyright © 2013 Pearson Education, Inc. Publishing as Prentice Hall