1 / 35

Enhanced Entity-Relationship Modeling

Enhanced Entity-Relationship Modeling. Strong and Weak Entity Types. Strong entity: Each object is uniquely identifiable using primary key of that entity type. Weak entity: Each object cannot be uniquely identified using only the attributes associated with that entity type.

idola
Download Presentation

Enhanced Entity-Relationship Modeling

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  1. Enhanced Entity-Relationship Modeling

  2. Strong and Weak Entity Types • Strong entity: Each object is uniquely identifiable using primary key of that entity type. • Weak entity: Each object cannot be uniquely identified using only the attributes associated with that entity type. • Entities that cannot exist in the database unless another entity also exists.

  3. Weak Entity Examples • Course: CID, Cname, Credits • Section: Section#, Room • MedicalBldg: BuilidngID, Bname, Address • Office: Room# • Web page and placeholders

  4. Course 1 M Section Has Has Course Section CID {PK} Cname credits Section# Room#

  5. Supertypes and Subtypes • Supertype:A generic entity type that has a relationship with one or more subtypes • An entity type that includes one or more distinct subgroups which require to be represented in a data model. • Subtype:A subgrouping of the entities in an entity type that has attributes distinct from those in other subgroupings • Attribute Inheritance: • Subtype entities inherit values of all attributes of the supertype • An instance of a subtype is also an instance of the supertype

  6. Figure 4-1 Basic notation for supertype/subtype notation a) EER notation

  7. 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

  8. Employee: • EID, Ename, Salary, Position, TypingSpeed, ManagerBonus, SalesArea, CarAllowance • Employee:EID, Ename, Salary, Position • Manager: managerBonus • SalesPerson: SalesArea, CarAllowance • Secretary: TypingSpeed

  9. Faculty • Professor • Lecturer • GraduateAssistant

  10. 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

  11. 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

  12. Generalization and Specialization • 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

  13. Figure 4-4 Example of generalization a) Three entity types: CAR, TRUCK, and MOTORCYCLE All these types of vehicles have common attributes

  14. Figure 4-4 Example of generalization (cont.) b) Generalization to VEHICLE supertype So we put the shared attributes in a supertype Note: no subtype for motorcycle, since it has no unique attributes

  15. Figure 4-5 Example of specialization Only applies to manufactured parts Applies only to purchased parts a) Entity type PART

  16. Note: multivalued attribute was replaced by an associative entity relationship to another entity Figure 4-5 Example of specialization (cont.) b) Specialization to MANUFACTURED PART and PURCHASED PART Created 2 subtypes

  17. Constraints in Supertype/ Completeness Constraint • 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)

  18. Figure 4-6 Examples of completeness constraints A patient must be either an outpatient or a resident patient a) Total specialization rule

  19. A vehicle could be a car, a truck, or neither Figure 4-6 Examples of completeness constraints (cont.) b) Partial specialization rule

  20. Constraints in Supertype/ Disjointness constraint • 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

  21. Figure 4-7 Examples of disjointness constraints A patient can either be outpatient or resident, but not both a) Disjoint rule

  22. A part may be both purchased and manufactured Figure 4-7 Examples of disjointness constraints (cont.) b) Overlap rule

  23. Figure 4-10 Example of supertype/subtype hierarchy

  24. Entity Clusters • 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

  25. Figure 4-13a Possible entity clusters for Pine Valley Furniture in Microsoft Visio Related groups of entities could become clusters

  26. Figure 4-13b EER diagram of PVF entity clusters More readable, isn’t it?

  27. Packaged data models provide generic models that can be customized for a particular organization’s business rules

  28. Business rules • Statements that define or constrain some aspect of the business • Classification of business rules: • 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 • Action assertion–rule expressing constraints/control of organizational actions

  29. Corresponding object In this case, the action assertion is a Restriction Corresponding object Figure 4-20 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

  30. Figure 4-21 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 In this case, the action assertion is an Upper LIMit Corresponding object Action assertion Anchor object

  31. Introduction to Relational Model • Data is logically structured within relations. • Each relation is a table (file) with named columns (attributes, fields) and rows (records).

  32. Properties of a Relation • Simple attribute • No composite, no multivalued attribute • Each relation must have a primary key: • Simple or composite key • May have other keys (candidate keys) • Key cannot be null • Cannot be duplicated

  33. Integrity Constraints • Domain constraints • Entity integrity: • Primary key cannot be null, cannot be duplicated • Referential integrity • Other constraints

  34. Relational Database Design • Strong entity: Create a table that includes all simple attributes • Composite • Weak entity: add owner primary key • Multi-valued attribute: Create a table for each multi-valued attribute • Key + attribute • Relationship: • 1:1, 1:M • Relationship table: for partial participation to avoid null • Foreign key • M:M: relationship table • N-ary relationship: relationship table • Recursive relationship • Attribute of relationship • Superclass and subclass

  35. Online Shopping Cart EmailAddr CartID Date CID Cname Has M ShoppingCart Customer 1 M Qty Has M Product Price PID Pname

More Related