1. MIS 385/MBA 664 Systems Implementation with DBMS/ Database Management Dave Salisbury salisbury@udayton.edusalisbury@udayton.edu (email) http://www.davesalisbury.com/http://www.davesalisbury.com/ (web site)

2. Entity Clusters EER diagrams are difficult to read when there are too many entities and relationships “Chunking” (Miller, 1956) 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

3. Possible entity clusters for Pine Valley Furniture Related groups of entities could become clusters

4. Possible entity clusters for Pine Valley Furniture in Microsoft Visio Related groups of entities could become clusters

5. EER diagram of PVF entity clusters More readable, isn’t it?

6. EER diagram of PVF entity clusters More readable, isn’t it?

7. Figure 4-14 Manufacturing entity cluster Detail for a single cluster

8. Universal Data Models Generic/template data model Can be reused as starting point a.k.a. data model patterns

9. Universal Data Models Can leverage previous experience Less time and effort (think object-oriented programming) Less likely to miss stuff common across organization – holistic view Good starting point for new requirements Extensive use of supertype/subtype Reusing data Holistic view (there’s that word again) Extensive use of M:N Greater flexibility Implied handling of time-stamp and history data Capture best practices (even those outside your organization)

10. Packaged data models provide generic models that can be customized for a particular organization’s business rules Universal Data Models

11. Business rules Statements that define or constrain some aspect of the business. Constraints can impact: Structure (definition, domain, relationship) Behavior (operational constraints) Classification of business rules: Derivation – rule derived from other knowledge Structural assertion – rule expressing static structure Action assertion – rule expressing constraints/control of organizational actions

12. EER depiction of business rules classification

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

14. Stating an Action Assertion Action Assertion Action assertion will identify corresponding objects that constrain the ability to perform actions on anchor objects Anchor Object an object on which actions are limited Action creation, deletion, update, or read Corresponding Objects an object influencing the ability to perform an action on another business rule

15. Data model segment for class scheduling

16. 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 In this case, the action assertion is a restriction

17. 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 assertion Anchor object Corresponding object In this case, the action assertion is an upper limit.