1. © 2005 by Prentice Hall 1 Chapter 4: The Enhanced ER Model and Business Rules Modern Database Management 7 th Edition Jeffrey A. Hoffer, Mary B. Prescott, Fred R. McFadden

2. Chapter 4 © 2005 by Prentice Hall 2 Objectives Definition of terms Definition of terms Use of supertype/subtype relationships Use of supertype/subtype relationships Use of generalization and specialization techniques Use of generalization and specialization techniques Specification of completeness and disjointness constraings Specification of completeness and disjointness constraings Develop supertype/subtype hierarchies for common business situations Develop supertype/subtype hierarchies for common business situations Develop entity clusters Develop entity clusters Name categories of business rules Name categories of business rules Define operational constraints graphically and in English Define operational constraints graphically and in English

3. Chapter 4 © 2005 by Prentice Hall 3 Supertypes and Subtypes Subtype: A subgrouping of the entities in an entity type which has attributes that are distinct from those in other subgroupings Subtype: A subgrouping of the entities in an entity type which has attributes that are distinct from those in other subgroupings Supertype: An generic entity type that has a relationship with one or more subtypes Supertype: An generic entity type that has a relationship with one or more subtypes Attribute Inheritance: Attribute Inheritance: Subtype entities inherit values of all attributes of the supertype Subtype entities inherit values of all attributes of the supertype An instance of a subtype is also an instance of the supertype An instance of a subtype is also an instance of the supertype

4. Chapter 4 © 2005 by Prentice Hall 4

5. Chapter 4 © 2005 by Prentice Hall 5 Different modeling tools may have different notation for the same modeling constructs

6. Chapter 4 © 2005 by Prentice Hall 6 Figure 4-2 – Employee supertype with three subtypes All employee subtypes will have emp nbr, name, address, and date-hired Each employee subtype will also have its own attributes

7. Chapter 4 © 2005 by Prentice Hall 7 Relationships and Subtypes Relationships at the supertype level indicate that all subtypes will participate in the relationship 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 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. Chapter 4 © 2005 by Prentice Hall 8 Figure 4-3 – Supertype/subtype relationships in a hospital Both outpatients and resident patients are cared for by a responsible physician Only resident patients are assigned to a bed

9. Chapter 4 © 2005 by Prentice Hall 9 Generalization and Specialization Generalization: The process of defining a more general entity type from a set of more specialized entity types. BOTTOM-UP 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 Specialization: The process of defining one or more subtypes of the supertype, and forming supertype/subtype relationships. TOP-DOWN

10. Chapter 4 © 2005 by Prentice Hall 10 Figure 4-4a – Example of generalization Three entity types: CAR, TRUCK, and MOTORCYCLE All these types of vehicles have common attributes

11. Chapter 4 © 2005 by Prentice Hall 11 Figure 4-4b – Generalization to VEHICLE supertype So we put the shared attributes in a supertype Note: no subtype for motorcycle, since it has no unique attributes

12. Chapter 4 © 2005 by Prentice Hall 12 Figure 4-5a – Example of specialization Entity type PART Only applies to manufactured parts Applies only to purchased parts

13. Chapter 4 © 2005 by Prentice Hall 13 Figure 4-5b – Specialization to MANUFACTURED PART and PURCHASED PART Note: multivalued attribute was replaced by a relationship to another entity Created 2 subtypes

14. Chapter 4 © 2005 by Prentice Hall 14 Constraints in Supertype/ Completeness Constraint Completeness Constraints : Whether an instance of a supertype must also be a member of at least one subtype Completeness Constraints : Whether an instance of a supertype must also be a member of at least one subtype Total Specialization Rule: Yes (double line) Total Specialization Rule: Yes (double line) Partial Specialization Rule: No (single line) Partial Specialization Rule: No (single line)

15. Chapter 4 © 2005 by Prentice Hall 15 Figure 4-6a – Examples of completeness constraints Total specialization rule A patient must be either an outpatient or a resident patient

16. Chapter 4 © 2005 by Prentice Hall 16 Figure 4-6b – Partial specialization rule A vehicle could be a car, a truck, or neither

17. Chapter 4 © 2005 by Prentice Hall 17 Constraints in Supertype/ Disjointness constraint Disjointness Constraints : Whether an instance of a supertype may simultaneously be a member of two (or more) subtypes 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 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 Overlap Rule: An instance of the supertype could be more than one of the subtypes

18. Chapter 4 © 2005 by Prentice Hall 18 Disjoint rule Figure 4-7a – Examples of disjointness constraints A patient can either be outpatient or resident, but not both

19. Chapter 4 © 2005 by Prentice Hall 19 Figure 4-7b Overlap rule A part may be both purchased and manufactured

20. Chapter 4 © 2005 by Prentice Hall 20 Constraints in Supertype/ Subtype Discriminators Subtype Discriminator : An attribute of the supertype whose values determine the target subtype(s) 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 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 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

21. Chapter 4 © 2005 by Prentice Hall 21 Figure 4-8 – Introducing a subtype discriminator ( disjoint rule) A simple attribute with different possible values indicating the subtype

22. Chapter 4 © 2005 by Prentice Hall 22 Figure 4-9 – Subtype discriminator ( overlap rule) A composite attribute with sub-attributes indicating “yes” or “no” to determine whether it is of each subtype

23. Chapter 4 © 2005 by Prentice Hall 23

24. Chapter 4 © 2005 by Prentice Hall 24 Business rules Statements that define or constrain some aspect of the business. Statements that define or constrain some aspect of the business. Classification of business rules: Classification of business rules: Derivation – rule derived from other knowledge, often in the form of a formula using attribute values Derivation – rule derived from other knowledge, often in the form of a formula using attribute values Structural assertion – rule expressing static structure. Includes attributes, relationships, and definitions Structural assertion – rule expressing static structure. Includes attributes, relationships, and definitions Action assertion – rule expressing constraints/control of organizational actions Action assertion – rule expressing constraints/control of organizational actions

25. Chapter 4 © 2005 by Prentice Hall 25 Figure 4-16 – EER depiction of business rules classification

26. Chapter 4 © 2005 by Prentice Hall 26 Action Assertion Classifications Result Result Condition – IF/THEN rule Condition – IF/THEN rule Integrity constraint – must always be true Integrity constraint – must always be true Authorization – privilege statement Authorization – privilege statement Form Form Enabler – leads to creation of new object Enabler – leads to creation of new object Timer – allows or disallows an action Timer – allows or disallows an action Executive – executes one or more actions Executive – executes one or more actions Rigor Rigor Controlling – something must or must not happen Controlling – something must or must not happen Influencing – guideline for which a notification must occur Influencing – guideline for which a notification must occur

27. Chapter 4 © 2005 by Prentice Hall 27 Stating an Action Assertion Anchor Object – an object on which actions are limited Anchor Object – an object on which actions are limited Action – creation, deletion, update, or read Action – creation, deletion, update, or read Corresponding Objects – an object influencing the ability to perform an action on another business rule Corresponding Objects – an object influencing the ability to perform an action on another business rule Action assertions identify corresponding objects that constrain the ability to perform actions on anchor objects

28. Chapter 4 © 2005 by Prentice Hall 28 Figure 4-17 – Data model segment for class scheduling

29. Chapter 4 © 2005 by Prentice Hall 29 Figure 4-18 – Business Rule 1: For a faculty member to be assigned to teach a section of a course, the faculty member must be qualified to teach the course for which that section is scheduled Action assertion Anchor object Corresponding object R In this case, the action assertion is a R estriction

30. Chapter 4 © 2005 by Prentice Hall 30 Figure 4-19 – Business Rule 2: For a faculty member to be assigned to teach a section of a course, the faculty member must not be assigned to teach a total of more than three course sections Action assertionAnchor object Corresponding object In this case, the action assertion is an ULIM U pper LIM it