Chapter 3  Define terms  Understand use of supertype/subtype relationships  Understand use of specialization and generalization techniques  Specify.

Slides:



Advertisements
Similar presentations
THE EXTENDED ENTITY RELATIONSHIP MODEL (EERM)
Advertisements

Conceptual Design Modeling the rules of organization Building ER model.
1 © Prentice Hall, 2002 Chapter 4: The Enhanced E-R Model and Business Rules Modern Database Management 6 th Edition Jeffrey A. Hoffer, Mary B. Prescott,
Chapter 4: The Enhanced ER Model and Business Rules
Enhanced E-R Models and Business Rules
1 Chapter 4 The Enhanced ER Model and Business Rules.
Chapter 3: The Enhanced E-R Model
Basic notation for supertype/subtype relationships
Enhanced Entity-Relationship Modeling. Strong and Weak Entity Types Strong entity: Each object is uniquely identifiable using primary key of that entity.
Chapter 3 The Enhanced E-R Model
© 2011 Pearson Education, Inc. Publishing as Prentice Hall 1 Chapter 3: The Enhanced E-R Model Modern Database Management 10 th Edition Jeffrey A. Hoffer,
1 © Prentice Hall, 2002 Chapter 4: The Enhanced E-R Model and Business Rules Modern Database Management 6 th Edition Jeffrey A. Hoffer, Mary B. Prescott,
Chapter 3 © 2013 Pearson Education, Inc. Publishing as Prentice Hall 1 CHAPTER 4: THE ENHANCED E-R MODEL Modern Database Management 11 th Edition Jeffrey.
Database Systems: Design, Implementation, and Management Eighth Edition Chapter 6 Advanced Data Modeling.
Database Design and the E-R Model Chapter 7 [2 of 2]
CHAPTER 3: THE ENHANCED E-R MODEL © 2013 Pearson Education, Inc. Publishing as Prentice Hall 1 Modern Database Management 11 th Edition Jeffrey A. Hoffer,
1 © Prentice Hall, 2002 Chapter 4: The Enhanced E-R Model and Business Rules Modern Database Management 6 th Edition Jeffrey A. Hoffer, Mary B. Prescott,
Chapter 4 © 2005 by Prentice Hall 1 Objectives Definition of terms Definition of terms Use of supertype/subtype relationships Use of supertype/subtype.
Copyright © 2007 Ramez Elmasri and Shamkant B. Navathe Chapter 4 Enhanced Entity-Relationship (EER) Modeling.
Chapter 4: The Enhanced ER Model and Business Rules
Enhanced Entity-Relationship Modeling
The Enhanced E-R (EER) Model
IS 4420 Database Fundamentals Chapter 4: The Enhanced ER Model and Business Rules Leon Chen.
Chapter 4: The Enhanced E-R Model and Business Rules
Chapter 4 1 Chapter 4: The Enhanced ER Model and Business Rules.
1 Chapter 4 Enhanced E-R Model. 2 Supertypes and Subtypes Subtype: A subgrouping of the entities in an entity type which has attributes that are distinct.
Chapter 3: The Enhanced E-R Model
1 Chapter 4: The Enhanced ER Model and Business Rules.
 Keys are special fields that serve two main purposes: ◦ Primary keys are unique identifiers of the relation in question. Examples include employee numbers,
Entities and Attributes
© 2011 Pearson Education, Inc. Publishing as Prentice Hall 1 Chapter 3: The Enhanced E-R Model Modern Database Management 10 th Edition Jeffrey A. Hoffer,
© 2007 by Prentice Hall (Hoffer, Prescott & McFadden) 1 The Enhanced Entity Relationship Diagrams (E-ERDs)
Chapter 4: The Enhanced ER Model and Business Rules
Chapter 4 1 Chapter 4: The Enhanced ER Model and Business Rules Modern Database Management Jeffrey A. Hoffer, Mary B. Prescott, Fred R. McFadden.
© 2009 Pearson Education, Inc. Publishing as Prentice Hall 1 Modeling Data in the Organization Chapters 3 + 4: Modern Database Management 9 th Edition.
Chapter 3: The Enhanced E-R Model
1 The Enhanced Entity Relationship Diagrams (E-ERDs)
Enhanced Entity-Relationship and Object Modeling Chapter 4
Chapter 3: The Enhanced E-R Model
CHAPTER 3: THE ENHANCED E-R MODEL © 2013 Pearson Education, Inc. Publishing as Prentice Hall 1 Modern Database Management 11 th Edition Jeffrey A. Hoffer,
Enhanced Entity-Relationship (EER) Modeling. Slide 4- 2 Chapter Outline EER stands for Enhanced ER or Extended ER EER Model Concepts Includes all modeling.
© 2011 Pearson Education 1 Chapter 3: Advanced Database Analysis Modern Database Management 10 th Edition, International Edition Jeffrey A. Hoffer, V.
CHAPTER 3: THE ENHANCED E-R MODEL © 2013 Pearson Education, Inc. Publishing as Prentice Hall 1 Modern Database Management 11 th Edition Jeffrey A. Hoffer,
Database Systems Supertypes and Subtypes Lecture # 10.
Database Management System Prepared by Dr. Ahmed El-Ragal Reviewed & Presented By Mr. Mahmoud Rafeek Alfarra College Of Science & Technology- Khan younis.
Entity Relationship Modeling
Enhanced Entity-Relationship Modeling
© Shamkant B. Navathe CC Enhanced Entity-Relationship Copyright © 2004 Ramez Elmasri and Shamkant Navathe.
© 2009 Pearson Education, Inc. Publishing as Prentice Hall 1 Chapter 4: The Enhanced E-R Model and Business Rules Modern Database Management 9 th Edition.
© 2009 Pearson Education, Inc. Publishing as Prentice Hall 1 Chapter 4: The Enhanced E-R Model Modern Database Management 9 th Edition Jeffrey A. Hoffer,
Advance Database Engineering 1 Chapter 4: The Enhanced ER Model and Business Rules Modern Database Management 7 th Edition Jeffrey A. Hoffer, Mary B. Prescott,
Copyright © 2016 Pearson Education, Inc. Modern Database Management 12 th Edition Jeff Hoffer, Ramesh Venkataraman, Heikki Topi CHAPTER 3: THE ENHANCED.
Data Modeling Advanced Concepts Updated 20/4/2015 TMC2034 Database Concept and Design1.
Lecture # 14 Chapter # 5 The Relational Data Model and Relational Database Constraints Database Systems.
© 2005 by Prentice Hall 1 Chapter 4: The Enhanced ER Model and Business Rules Modern Database Management 7 th Edition Jeffrey A. Hoffer, Mary B. Prescott,
Chapter 3: The Enhanced E-R Model
The Enhanced E-R Model and Business Rules
LECTURE 4: Chapter 4: The Enhanced E-R Model
Advanced Database Analysis
Chapter 4: The Enhanced E-R Model and Business Rules
Chapter 4: The Enhanced ER Model and Business Rules
Super Entity & Sub Entity
Database Management System 1 (ITED123A)
Chapter 3: The Enhanced E-R Model
Overview of Entity‐Relationship Model
CHAPTER 3: THE ENHANCED E-R MODEL
Chapter 5 Advanced Data Modeling
MBA 664 Database Management
MIS 385/MBA 664 Systems Implementation with DBMS/ Database Management
CGS 2545: Database Concepts Summer 2006
Presentation transcript:

Chapter 3  Define terms  Understand use of supertype/subtype relationships  Understand use of specialization and generalization techniques  Specify completeness and disjointness constraints  Develop supertype/subtype hierarchies for realistic business situations  Develop entity clusters  Explain universal (packaged) data model  Describe special features of data modeling project using packaged data model 1SPR 15

Chapter 3  Basic E-R introduced? 1970  Complex business relationships Enhanced ER model: extends original ER model with new modeling constructs  Most important modeling construct incorporated? ◦ Supertype/Subtype relationships  What enables us to model a general entity type? ◦ Supertype  What enables us to subdivide a general entity into several specialized entity? ◦ Subtype SPR 152

Chapter 3  Supertype: A generic entity type that has a relationship with one or more subtypes  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 3SPR 15

Chapter 3 4 a) EER notation 4 Chapter 3 SPR 15 Figure 3-1 Basic notation for supertype/subtype notation

Chapter 3 5 Different modeling tools may have different notation for the same modeling constructs. Figure 3-1 Basic notation for supertype/subtype notation (cont.) 5 Chapter 3 SPR 15 b) Microsoft Visio Notation

Chapter 3 6 Figure 3-2 Employee supertype with three subtypes All employee subtypes will have employee number, name, address, and date hired Each employee subtype will also have its own attributes 6 Chapter 3 SPR 15 The Company employs hourly, salaried and consultants as employees

Chapter 3  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 7SPR 15

Chapter 3 8 Figure 3-3 Supertype/subtype relationships in a hospital 8 Chapter 3 SPR 15 Hospitals need to keep records of Patients (regular therapy, outpatient, resident)

Chapter 3  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 9SPR 15

Chapter 3 10 a) Three entity types: CAR, TRUCK, and MOTORCYCLE All these types of vehicles have common attributes 10 Chapter 3 SPR 15 Figure 3-4 Example of generalization (a)

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

Chapter 3 12 a) Entity type PART Only applies to manufactured parts Applies only to purchased parts 12 Chapter 3 SPR 15 Figure 3-5 Example of specialization

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

Chapter 3  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) 14SPR 15

Chapter 3 Figure 3-6 Examples of completeness constraints a) Total specialization rule 15 Chapter 3 SPR 1515

Chapter 3 16 b) Partial specialization rule Figure 3-6 Examples of completeness constraints (cont.) 16 Chapter 3 SPR 15

Chapter 3  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 17 Chapter 3 SPR 15

Chapter 3 18 a) Disjoint rule Figure 3-7 Examples of disjointness constraints 18 Chapter 3 SPR 15

Chapter 3 19 b) Overlap rule Figure 3-7 Examples of disjointness constraints (cont.) 19 Chapter 3 SPR 15

Chapter 3  Subtype Discriminator : An attribute of the supertype whose values determine the target subtype(s)  Disjoint – a simple attribute with alternative values to indicate the possible subtypes  Overlapping – a composite attribute whose subparts pertain to different subtypes. Each subpart contains a Boolean value to indicate whether or not the instance belongs to the associated subtype 20 Chapter 3 SPR 15

Chapter 3 21 Figure 3-8 Introducing a subtype discriminator ( disjoint rule) 21 Chapter 3 SPR 15

Chapter 3 22 Figure 3-9 Subtype discriminator ( overlap rule) 22 Chapter 3 SPR 15

Chapter 3 23 Figure 3-10 Example of supertype/subtype hierarchy 23 Chapter 3 SPR 15

Chapter 3  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 24SPR 15

Chapter 3 25 Figure 3-13a Possible entity clusters for Pine Valley Furniture in Microsoft Visio Related groups of entities could become clusters SPR 15

Chapter 3 26 Figure 3-13b EER diagram of PVF entity clusters More readable, isn’t it? 26 Chapter 3 SPR 15

Chapter 3 27 Figure 3-14 Manufacturing entity cluster Detail for a single cluster 27 Chapter 3 SPR 15

Chapter 3  Predefined data models  Could be universal or industry- specific  Universal data model = a generic or template data model that can be reused as a starting point for a data modeling project (also called a “pattern”) 28SPR 15

Chapter 3  Use proven model components  Save time and cost  Less likelihood of data model errors  Easier to evolve and modify over time  Aid in requirements determination  Easier to read  Supertype/subtype hierarchies promote reuse  Many-to-many relationships enhance model flexibility  Vendor-supplied data model fosters integration with vendor’s applications  Universal models support inter-organizational systems 29SPR 15

Chapter 3 30 Packaged data models are generic models that can be customized for a particular organization’s business rules. Figure 3-15 PARTY, PARTY ROLE, and ROLE TYPE in a universal data model (a) Basic PARTY universal data model 30 Chapter 3 SPR 15

Chapter 3 31 Figure 3-15 PARTY, PARTY ROLE, and ROLE TYPE in a universal data model (b) PARTY supertype/subtype hierarchy 31 Chapter 3 SPR 15