Basic ER modeling was adequate for simpler databases, but in the 1980’s more demanding databases required more extensive modeling requirements. Some such.

Slides:



Advertisements
Similar presentations
Chapter 12 Enhanced Entity-Relationship Modeling Transparencies © Pearson Education Limited 1995, 2005.
Advertisements

1 Pertemuan Perluasan E-R Matakuliah: >/ > Tahun: > Versi: >
Copyright © 2007 Ramez Elmasri and Shamkant B. Navathe Slide 4- 1.
Copyright © 2011 Pearson Education, Inc. Publishing as Pearson Addison-Wesley Chapter 8 The Enhanced Entity- Relationship (EER) Model.
Copyright © 2007 Ramez Elmasri and Shamkant B. Navathe Chapter 4 Enhanced Entity-Relationship (EER) Modeling.
1 Database Systems: A Practical Approach to Design, Implementation and Management International Computer Science S. Carolyn Begg, Thomas Connolly Lecture.
1 Enhanced Entity Relationship Modelling EER Model Concepts Includes all basic ER modeling concepts Additional concepts: subclasses/superclasses specialization/generalization.
Enhanced ER modeling techniques Transparencies
Entity-Relationship (E-R) Model
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:
Chapter 41 Enhanced Entity-Relationship and Object Modeling.
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.
Copyright © 2011 Pearson Education, Inc. Publishing as Pearson Addison-Wesley Chapter 8 The Enhanced Entity- Relationship (EER) Model.
Enhanced Entity-Relationship and UML Modeling. Enhanced-ER (EER) Model Concepts Includes all modeling concepts of basic ER Additional concepts: subclasses/superclasses,
Enhanced Entity-Relationship Model (EER) 1. Enhanced-ER (EER) Model Concepts Includes all modeling concepts of basic ER Additional concepts: subclasses/superclasses,
Entities and Attributes
Entity Relationship Modeling
© 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)
Database Systems: Enhanced Entity-Relationship Modeling Dr. Taysir Hassan Abdel Hamid.
CSC271 Database Systems Lecture # 25. Summary: Previous Lecture  Structural constraints  Multiplicity  Cardinality  Participation  Connection traps.
Chapter 11 & 12 Entity-Relationship (E-R) Model Characteristics of E-R Model Components of E-R Model Example of E-R Model Enhanced E-R Model.
Enhanced Entity-Relationship (EER) Modeling. Slide 4- 2 Chapter Outline EER stands for Enhanced ER or Extended ER EER Model Concepts Includes all modeling.
ICOM 5016 – Introduction to Database Systems Lecture 5 Dr. Manuel Rodriguez Department of Electrical and Computer Engineering University of Puerto Rico,
Enhanced Entity-Relationship Modeling
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.
Chapter 4 Extended Entity-Relationship (EER)Model Incorporates Set-subset Relationships Incorporates Generalization Hierarchies Constraints: Coverage Constraints:
CST203-2 Database Management Systems Lecture 4. Student entity NIDFNameLNameRegNoExamIdBirthdate.
© Shamkant B. Navathe CC Enhanced Entity-Relationship Copyright © 2004 Ramez Elmasri and Shamkant Navathe.
Topic 4 - Part I Enhanced Entity-Relationship and UML Modeling
April 20022/CS/3X EER 1 Database Design Enhanced entity-relationship modelling John Wordsworth Department of Computer Science The University of Reading.
Extended ER Modelling. Extended E-R Features: Specialization Top-down design process; we designate subgroupings within an entity set that are distinctive.
Enhanced Entity-Relationship and UML Modeling. 2.
Copyright © 2007 Pearson Education, Inc. Publishing as Pearson Addison-Wesley Slide 4- 1.
Enhanced Entity-Relationship (EER) Model
The Enhanced Entity- Relationship (EER) Model
Enhanced Entity-Relationship Modeling
Enhanced Entity-Relationship Modeling
Enhanced Entity-Relationship and Object Modeling Objectives
© Shamkant B. Navathe CC.
Conceptual Design & ERD Modelling
The Enhanced Entity- Relationship (EER) Model
Enhanced Entity-Relationship (EER) Modeling
EER Model – Chapter
Session 2 Welcome: The sixth learning sequence
Enhanced ER Modeling Transparencies
Chapter 13 Enhanced Entity-Relationship Modeling
Software Engineering Lecture #11.
© Shamkant B. Navathe CC.
Enhanced Entity-Relationship Modeling
Chapter Entity-Relationship Modeling & Enhanced Entity- Relationship Modeling.
© Shamkant B. Navathe CC.
CS4222 Principles of Database System
Enhanced Entity-Relationship Modeling Transparencies
Enhanced Entity-Relationship Modeling Transparencies
Enhanced Entity-Relationship Modeling
Sampath Jayarathna Cal Poly Pomona
Database EER.
ENHANCED ENTITY-RELATIONSHIP (EER) MODEL
© Shamkant B. Navathe CC.
Enhanced Entity-Relationship (EER) Modeling
Enhanced Entity-Relationship Modeling
Enhanced Entity-Relationship Modeling
Presentation transcript:

Basic ER modeling was adequate for simpler databases, but in the 1980’s more demanding databases required more extensive modeling requirements. Some such applications:  CAD - Computer Aided Design  CAM – Computer Aided Manufacturing  CASE – Computer Assisted Software Engineering  OIS – Office Information Systems  GIS – Geographical Information Systems

EER adds 3 main additional semantic concepts for visual modeling of databases using UML(Unified Modeling Language). 1. Specialization/Generalization 1. Superclass 2. Subclass 3. Inheritance 2. Aggregation 3. Composition

 Very similar to Object Oriented programming superclass, subclass and inheritance.  Superclass: An entity type that includes one ore more subgroupings of its occurrences, which require to be represented in a data model.  Subclass: A distinct subgrouping of occurrences of an entity type, which require to be represented in a data model.  Superclass/Subclass relation is a 1:1 relation  Superclass may contain overlapping subclasses  Helps avoid multiple copies of the same data and null entries

 Subclasses inherit Superclasses attributes  Subclass is its own entity  Subclass may have its own subclasses  Shared Subclass: Entity with more than 1 Superclass : (Multiple Inheritance)  An entity and its Sublasses are called:  Type Hierarchy  Specialization Hierarchy  Generalization Hierarchy  Is-A Hierarchy

 Specialization: The process of maximizing the differences between members of an entity by identifying their distinguishing characteristics.  Specialization is a Top-Down approach  Generalization: The process of minimizing the differences between entities by identifying their common characteristics.  Generalization is a Bottom-Up approach

 Use an open triangle on the Superclass side to denote a SuperClass/Subclass relation.

 Participation Constraint: Determines whether every member of a superclass must participate as a member of a subclass.  Mandatory  Optional  Disjoint Constraint: Describes the relationship between members of the subclasses and indicates whether it is possible for a member of a superclass to be a member of one or more subclasses.  Disjoint: Or  Nondisjoint: And

4 Possibilities {Mandatory, And} {Mandatory, Or} {Optional, And} {Optional, Or}

 Aggregation: Represents a “has-a” or “is-part- of” relationship between two entities.  Entirely conceptual, only distinguishing the “whole” from the “part”  Does not change the diagrammatic meaning or traversal of the relationship  Does not link the lifetimes of the “whole” and “part”

 Use an Open diamond on the “whole” side

 Composition: A specific form of aggregation that represents an association between entities, where there is a strong ownership and coincidental lifetime between the “whole” and “part”.  In a Composite relationship the “whole” is responsible for the disposition of the relationship.  The “whole” is responsible for the creation and destruction of its parts.  An object may be part of only one composite at a time.

 Use a filled diamond on the “whole” side

By: Bryan Hunwardsen