Subclasses and Superclasses

Slides:



Advertisements
Similar presentations
© Shamkant B. Navathe CC. © Shamkant B. Navathe CC Chapter 4 - Part I Enhanced Entity-Relationship and UML Modeling Copyright © 2004 Ramez Elmasri and.
Advertisements

Enhanced Entity-Relationship and Object Modeling (Ch 4) Jan R McFadyen1 Class/subclass relationships Inheritance Specialization Generalization.
Copyright © 2007 Ramez Elmasri and Shamkant B. Navathe Slide 4- 1.
Copyright © 2007 Ramez Elmasri and Shamkant B. Navathe Slide 4- 1.
Copyright © 2007 Ramez Elmasri and Shamkant B. Navathe Chapter 4 Enhanced Entity-Relationship (EER) Modeling.
1 Enhanced Entity Relationship Modelling EER Model Concepts Includes all basic ER modeling concepts Additional concepts: subclasses/superclasses specialization/generalization.
Copyright © 2011 Pearson Education, Inc. Publishing as Pearson Addison-Wesley Chapter 9 Relational Database Design by ER- and EER-to- Relational Mapping.
Copyright © 2011 Pearson Education, Inc. Publishing as Pearson Addison-Wesley Chapter 9 Relational Database Design by ER- and EER-to- Relational Mapping.
Chapter 7 Relational Database Design by ER- and EER-to-Relational Mapping Copyright © 2004 Pearson Education, Inc.
December 4, 2002 Data Modeling – James Cohen Enhanced Entity Relationship (EER) Model Presented by James Cohen.
Chapter 4 The Enhanced Entity-Relationship (EER) Model
© Shamkant B. Navathe CC METU Department of Computer Eng Ceng 302 Introduction to DBMS Enhanced Entity-Relationship (EER) Model by Pinar Senkul resources:
EXTENDED-ER (EER) MODEL CONCEPTS. Enhanced-ER (EER) Model Concepts  Basic ER diagram + more concepts =EER model  Additional concepts:  Subclasses/superclasses.
Specialization and generalization
Copyright © 2007 Ramez Elmasri and Shamkant B. Navathe Slide 4- 1 EER stands for Enhanced ER or Extended ER EER Model Concepts Includes all modeling concepts.
Enhanced Entity-Relationship and UML Modeling. Enhanced-ER (EER) Model Concepts Includes all modeling concepts of basic ER Additional concepts: subclasses/superclasses,
1 CSE 480: Database Systems Lecture 8: EER to Relational Mapping and DBDesigner Reference: Read Chapter 9 of the textbook.
1 CSE 880: Database Systems Lecture : EER to Relational Mapping Reference: Read Chapter 9 of the textbook.
Lecture4: Informal guidelines for good relational design Mapping ERD to Relation Ref. Chapter3 Lecture4 1.
1 CSE 480: Database Systems Lecture 4: Enhanced Entity-Relationship Modeling Reference: Read Chapter 8.1 – 8.5 of the textbook.
Switch off your Mobiles Phones or Change Profile to Silent Mode.
© Shamkant B. Navathe CC. © Shamkant B. Navathe CC Chapter 4 - Part I Enhanced Entity-Relationship and UML Modeling Copyright © 2004 Ramez Elmasri and.
Enhanced Entity – Relationship (EER) and Object Modeling (Based on Chapter 4 in Fundamentals of Database Systems by Elmasri and Navathe, Ed. 4)
THE ENHANCED ER (EER) MODEL CHAPTER 8 (6/E) CHAPTER 4 (5/E)
Mapping from conceptual model (EER-M)
Enhanced Entity-Relationship (EER) Modeling. Slide 4- 2 Chapter Outline EER stands for Enhanced ER or Extended ER EER Model Concepts Includes all modeling.
DatabaseIM ISU1 Chapter 7 ER- and EER-to-Relational Mapping Fundamentals of Database Systems.
1 CSBP430 – Database Systems Chapter 4: Enhanced Entity– Relationship and Object Modeling Elarbi Badidi College of Information Technology United Arab Emirates.
Copyright © 2007 Ramez Elmasri and Shamkant B. Navathe Slide 4- 1.
Elmasri and Navathe, Fundamentals of Database Systems, Fourth Edition Copyright © 2004 Ramez Elmasri and Shamkant Navathe Enhanced-ER (EER) Model Concepts.
Copyright © 2007 Ramez Elmasri and Shamkant B. Navathe Chapter 4 Enhanced Entity-Relationship (EER) Modeling.
Slide 4-1 Elmasri and Navathe, Fundamentals of Database Systems, Fourth Edition Revised by IB & SAM, Fasilkom UI, 2005 Exercise 1. a property or description.
© Shamkant B. Navathe CC Enhanced Entity-Relationship Copyright © 2004 Ramez Elmasri and Shamkant Navathe.
Topic 4 - Part I Enhanced Entity-Relationship and UML Modeling
Extended ER Modelling. Extended E-R Features: Specialization Top-down design process; we designate subgroupings within an entity set that are distinctive.
Lecture 3 A short revision of ER and EER modelling See R. Elmasri, S.B. Navathe. Fundamentals of Database Systems (third edition) Addison-wesley. Chapter.
Enhanced Entity-Relationship and UML Modeling. 2.
Copyright © 2007 Pearson Education, Inc. Publishing as Pearson Addison-Wesley Slide 4- 1.
Chapter 4_part2: The Enhanced Entity-Relationship (EER) Model.
Database Systems 主講人 : 陳建源 日期 :99/10/19 研究室 : 法 Chapter 4 Enhanced Entity-Relationship and Object Modeling.
Databases (CS507) CHAPTER 7.
Enhanced Entity-Relationship (EER) Model
Enhanced Entity-Relationship and Object Modeling Objectives
© Shamkant B. Navathe CC.
Relational Database Design by ER- and EER-to- Relational Mapping
Enhanced Entity-Relationship (EER) Modeling
The Enhanced Entity- Relationship (EER) Model
Enhanced Entity-Relationship (EER) Modeling
EER Model – Chapter
Session 2 Welcome: The sixth learning sequence
Enhanced Entity-Relationship (EER) Modeling
ER- and EER-to-Relational
© Shamkant B. Navathe CC.
Chapter 4+17 The Relational Model Pearson Education © 2014.
CSE2DBF – CSE4DBF EER Example 14/03/2017
© Shamkant B. Navathe CC.
EER to Relational Mapping
CS4222 Principles of Database System
Relational Database Design by ER- and EER-to- Relational Mapping
CS4222 Principles of Database System
Sampath Jayarathna Cal Poly Pomona
Database EER.
ENHANCED ENTITY-RELATIONSHIP (EER) MODEL
Sampath Jayarathna Cal Poly Pomona
© Shamkant B. Navathe CC.
Enhanced Entity-Relationship (EER) Modeling
Enhanced Entity-Relationship (EER) Modeling
Presentation transcript:

Subclasses and Superclasses Explain the cohort of the subject. Everyone has different pre-knowledge about some of the aspects. (Source: Elmasri and Navathe, Fundamentals of Database Systems, Figure 1, page 248)

Disjointed Constraint EmpID EmpID EName EName EAddress EMPLOYEE EAddress EMPLOYEE EDob EDob d o     TypingSpeed TypingSpeed EngType SECRETARY SECRETARY ENGINEER ENGINEER EngType TECHNICIAN TECHNICIAN TGrade TGrade An Employee, say with ID “001” is: a secretary, OR a technician OR an engineer. An Employee, say with ID “001” is: a secretary, OR a technician OR an engineer OR combination of the subclasses entities.

Completeness Constraint EmpID EmpID EName EName EAddress EMPLOYEE EAddress EMPLOYEE EDob EDob d d Salary PayScale Salary PayScale SALARIED EMPLOYEE HOURLY EMPLOYEE SALARIED EMPLOYEE HOURLY EMPLOYEE An Employee, say with ID “001” is: a salaried employee OR an hourly employee. An Employee, say with ID “001” is: a salaried employee OR an hourly employee OR none of them.

Transformation of Specialization/Generalization Option 8A: Multiple relations-Superclass and subclasses Option 8B: Multiple relations-Subclass relations only Option 8C: Single relation with one type attribute Option 8D: Single relation with multiple type attributes Disjointed Completeness Remarks “d” “o” “p” “t” 8A  8B *  *Redundancy of values of superclass entity’s attributes in all subclasses tables. 8C Can generate many NULL values if many local attributes exist in the subclasses entities. 8D Explain the cohort of the subject. Everyone has different pre-knowledge about some of the aspects. The selection of option is affected by variety of reasons, including the constraints of the relationships, the attributes of the entities and the cost to process the queries.

Specialization vs Union* Is-a SUB-CLASS SUPER-CLASS * See problem on the previous lecture. Jaime (owns Veh. ABC) Bank of Stark (owns Veh. DEF) Cersei & Bank of Lannister (own Veh. XYZ) Jaime (owns Veh. ABC) Bank of Stark (owns Veh. DEF) Cersei & Bank of Lannister (own Veh. XYZ) o PERSON BANK OWNER OWNER BANK PERSON U Jaime, 40 y/o Cersei, 40 y/o Tyrion, 38 y/o Bank of Lannister Bank of Stark Bank of Targaryen Jaime, 40 y/o Cersei, 40 y/o Tyrion, 38 y/o Bank of Lannister Bank of Stark Bank of Targaryen