Presentation is loading. Please wait.

Presentation is loading. Please wait.

1 Session 2 Welcome: The sixth learning sequence “ Enhanced Entity-Relationship Model “ E-E-R Model Recap : In the previous learning sequence, we discussed.

Similar presentations


Presentation on theme: "1 Session 2 Welcome: The sixth learning sequence “ Enhanced Entity-Relationship Model “ E-E-R Model Recap : In the previous learning sequence, we discussed."— Presentation transcript:

1 1 Session 2 Welcome: The sixth learning sequence “ Enhanced Entity-Relationship Model “ E-E-R Model Recap : In the previous learning sequence, we discussed the introduction to E-R model. Present learning: We shall explore the following topics: - Specialization. - Generalization.

2 2 Enhanced Entity-Relationship Model

3 3 Enhanced-ER (EER) Model Concepts uIncludes all modeling concepts of basic ER. uAdditional concepts: subclasses/super classes, specialization/generalization, categories, attribute inheritance. uThe resulting model is called the enhanced-ER or Extended ER (E2R or EER) model. uIt is used to model applications more completely and accurately if needed. uIt includes some object-oriented concepts, such as inheritance.

4 4 Subclasses and Super classes (1) uAn entity type may have additional meaningful sub groupings of its entities. uExample: EMPLOYEE may be further grouped into SECRETARY, ENGINEER, MANAGER, TECHNICIAN, SALARIED_EMPLOYEE, HOURLY_EMPLOYEE,… wEach of these groupings is a subset of EMPLOYEE entities. wEach is called a subclass of EMPLOYEE. wEMPLOYEE is the superclass for each of these subclasses. uThese are called superclass/subclass relationships. uExample: EMPLOYEE/SECRETARY, EMPLOYEE/TECHNICIAN.

5 5 Subclasses and Super classes (2) uThese are also called IS-A relationships (SECRETARY IS-A EMPLOYEE, TECHNICIAN IS-A EMPLOYEE, …). uNote: An entity that is member of a subclass represents the same real-world entity as some member of the super class. wThe Subclass member is the same entity in a distinct specific role. wAn entity cannot exist in the database merely by being a member of a subclass; it must also be a member of the super class. wA member of the super class can be optionally included as a member of any number of its subclasses. uExample: A salaried employee who is also an engineer belongs to the two subclasses ENGINEER and SALARIED_EMPLOYEE. wIt is not necessary that every entity in a super class be a member of some subclass.

6 6 Example of a Specialization

7 Attribute Inheritance uAn entity that is member of a subclass inherits all attributes of the entity as a member of the super class. uIt also inherits all relationships.

8 8 Specialization uTop-down design process; we designate sub groupings within an entity set that are distinctive from other entities in the set. uThese sub groupings become lower-level entity sets that have attributes or participate in relationships that do not apply to the higher-level entity set. uIs the process of defining a set of subclasses of a super class. uThe set of subclasses is based upon some distinguishing characteristics of the entities in the super class.

9 9 Specialization uExample: {SECRETARY, ENGINEER, TECHNICIAN} is a specialization of EMPLOYEE based upon job type. wMay have several specializations of the same super class. uExample: Another specialization of EMPLOYEE based in method of pay is {SALARIED_EMPLOYEE, HOURLY_EMPLOYEE}. wSuper class/subclass relationships and specialization can be diagrammatically represented in EER diagrams. wAttributes of a subclass are called specific attributes. For example, TypingSpeed of SECRETARY. wThe subclass can participate in specific relationship types. For example, BELONGS_TO of HOURLY_EMPLOYEE.

10 10 Generalization uThe reverse of the specialization process. u Several classes with common features are generalized into a super class; original classes become its subclasses. uExample: CAR, TRUCK generalized into VEHICLE; both CAR, TRUCK become subclasses of the super class VEHICLE. wWe can view {CAR, TRUCK} as a specialization of VEHICLE. wAlternatively, we can view VEHICLE as a generalization of CAR and TRUCK.

11 11 Generalization and Specialization uDiagrammatic notation sometimes used to distinguish between generalization and specialization. wArrow pointing to the generalized super class represents a generalization. wArrows pointing to the specialized subclasses represent a specialization. wWe do not use this notation because it is often subjective as to which process is more appropriate for a particular situation. wWe advocate not drawing any arrows in these situations.

12 12 Generalization and Specialization uData Modeling with Specialization and Generalization wA super class or subclass represents a set of entities. wShown in rectangles in EER diagrams (as are entity types). wSometimes, all entity sets are simply called classes, whether they are entity types, super classes, or subclasses.

13

14 Constraints on Specialization and Generalization (1) uIf we can determine exactly those entities that will become members of each subclass by a condition, the subclasses are called predicate-defined (or condition-defined) subclasses. wCondition is a constraint that determines subclass members. wDisplay a predicate-defined subclass by writing the predicate condition next to the line attaching the subclass to its super class.

15 Constraints on Specialization and Generalization (2) uIf all subclasses in a specialization have membership condition on same attribute of the super class, specialization is called an attribute defined- specialization. wAttribute is called the defining attribute of the specialization. wExample: JobType is the defining attribute of the specialization {SECRETARY, TECHNICIAN, ENGINEER} of EMPLOYEE The discriminator (or partial key) of a weak entity set is the set of attributes that distinguishes among all the entities of a weak entity set.

16 Constraints on Specialization and Generalization (3) uIf no condition determines membership, the subclass is called user-defined. wMembership in a subclass is determined by the database users by applying an operation to add an entity to the subclass. wMembership in the subclass is specified individually for each entity in the super class by the user.

17 17

18 Constraints on Specialization and Generalization (4) uTwo other conditions apply to a specialization/generalization: uDisjointness Constraint: wSpecifies that the subclasses of the specialization must be disjointed (an entity can be a member of at most one of the subclasses of the specialization). wSpecified by d in EER diagram. wIf not disjointed, overlap; that is the same entity may be a member of more than one subclass of the specialization. wSpecified by o in EER diagram. uCompleteness Constraint: wTotal specifies that every entity in the super class must be a member of some subclass in the specialization/ generalization. wShown in EER diagrams by a double line. wPartial allows an entity not to belong to any of the subclasses. wShown in EER diagrams by a single line.

19 Constraints on Specialization and Generalization (5) uHence, we have four types of specialization/generalization: wDisjoint, total wDisjoint, partial wOverlapping, total wOverlapping, partial uNote: Generalization usually is total because the super class is derived from the subclasses.

20 Example of disjoint partial Specialization

21 21 Hierarchies, Lattices and Shared Subclasses uA subclass may itself have further subclasses specified on it. uForms a hierarchy or a lattice. uHierarchy has a constraint that every subclass has only one super class (called single inheritance). uIn a lattice, a subclass can be subclass of more than one super class (called multiple inheritance). uIn a lattice or hierarchy, a subclass inherits attributes not only of its direct super class, but also of all its predecessor super classes.

22 22 Hierarchies, Lattices and Shared Subclasses uA subclass with more than one super class is called a shared subclass. uCan have specialization hierarchies or lattices, or generalization hierarchies or lattices. uIn specialization, start with an entity type and then define subclasses of the entity type by successive specialization (top down conceptual refinement process). uIn generalization, start with many entity types and generalize those that have common properties (bottom up conceptual synthesis process). uIn practice, the combination of two processes is employed.

23 23

24 24 Categories (UNION TYPES) uAll of the super class/subclass relationships we have seen thus far have a single super class. uA shared subclass is subclass in more than one distinct super class/subclass relationships, where each relationships has a single super class (multiple inheritance). uIn some cases, need to model a single super class/subclass relationship with more than one super class. uSuper classes represent different entity types.

25 25 Categories (UNION TYPES) uSuch a subclass is called a category or UNION TYPE. uExample: Database for vehicle registration, vehicle owner can be a person, a bank (holding a lien on a vehicle) or a company. wCategory (subclass) OWNER is a subset of the union of the three super classes COMPANY, BANK, and PERSON. wA category member must exist in at least one of its super classes. uNote: The difference from shared subclass, which is subset of the intersection of its super classes (shared subclass member must exist in all of its super classes).

26 26 Example of categories (UNION TYPES)

27 27 Examples 1 At a weekend retreat, the entity type person has 3 sub-type: camber, biker, runner. Draw a separate EER diagram for the following situations: 1- at a given time, a person must be exactly one of these subtypes. 2- a person may or may not be a member of these subtypes. However, a person who is one of these subtypes, can’t at the same time be a member of other subtypes. 3- a person may or may not be a member of these subtypes. On another hand, a person may be any two or even three of these subtypes. 4- at a given time, a person must be at least one of these subtypes.

28 28 Examples 2 A bank has thee types of accounts: Checking, Saving and loan. Following are the attributes for each type of accounts: Checking: Acc_no, Date_Opened, Balance, Servic-_charge. Saving: Acc_no, Date_Opened, Balance, Interest_rate. Loan: Acc_no, Date_Opened, Balance, Interest_rate, Payment. Assume that each bank account must be a member of these types. Using generalization, develop an EER diagram to represent this situation using the EER notations.

29 29 END


Download ppt "1 Session 2 Welcome: The sixth learning sequence “ Enhanced Entity-Relationship Model “ E-E-R Model Recap : In the previous learning sequence, we discussed."

Similar presentations


Ads by Google