LELCTURE 4: ENHANCED ENTITY-RELATIONSHIP MODELING (EER)

Similar documents
Database Systems. A Practical Approach to Design, Implementation, and Management. Database Systems. Thomas Connolly Carolyn Begg

COMP102: Introduction to Databases, 13

Chapter 8: Enhanced ER Model

Chapter 4. Enhanced Entity- Relationship Modeling. Enhanced-ER (EER) Model Concepts. Subclasses and Superclasses (1)

COIS Databases

Copyright 2007 Ramez Elmasri and Shamkant B. Navathe Slide 4-1

THE ENHANCED ER (EER) MODEL CHAPTER 8 (6/E) CHAPTER 4 (5/E)

Chapter 8 The Enhanced Entity- Relationship (EER) Model

Chapter 9: Relational DB Design byer/eer to Relational Mapping Relational Database Design Using ER-to- Relational Mapping Mapping EER Model

Lecture 10. Spring 2018 Borough of Manhattan Community College

Chapter (4) Enhanced Entity-Relationship and Object Modeling

Ch 9: Mapping EER to Relational. Follow a seven-step algorithm to convert the basic ER model constructs into relations steps 1-7

Chapter 17. Methodology Logical Database Design for the Relational Model

CS 338 The Enhanced Entity-Relationship (EER) Model

Copyright 2016 Ramez Elmasri and Shamkant B. Navathe

Chapter 6: Entity-Relationship Model. E-R Diagrams

Enhanced Entity- Relationship Models (EER)


Chapter 2: Entity-Relationship Model

Chapter 6: Entity-Relationship Model

Enhanced Entity-Relationship (EER) Modeling

DATABASE DESIGN I - 1DL300

ER to Relational Mapping

ER-to-Relational Mapping

Outline. Note 1. CSIE30600 Database Systems ER/EER to Relational Mapping 2

DATABASE DESIGN I - 1DL300

Database Design Process

6.1 RELATIONSHIP CONCEPTS

Chapter 6: Entity-Relationship Model

Relational DB Design by ER- and EER-to-Relational Mapping Design & Analysis of Database Systems

DATABASDESIGN FÖR INGENJÖRER F

Lecture 10 - Chapter 7 Entity Relationship Model

Conceptual Database Design

Entity Relationship Data Model. Slides by: Shree Jaswal

CMP-3440 Database Systems

LECTURE 3: ENTITY-RELATIONSHIP MODELING

Data Analysis 2. Chapter 2.2 V3.0. Napier University Dr Gordon Russell

Weak Entity Sets. A weak entity is an entity that cannot exist in a database unless another type of entity also exists in that database.

Database Management

DATABASTEKNIK - 1DL116

Chapter 7: Entity-Relationship Model

Chapter 7: Entity-Relationship Model

Chapter 7 Relational Database Design by ER- and EERR-to-Relational Mapping

Database Principles: Fundamentals of Design, Implementation, and Management Tenth Edition. Chapter 8 Data Modeling Advanced Concepts

Chapter 7: Entity-Relationship Model

Entity-Relationship Modelling. Entities Attributes Relationships Mapping Cardinality Keys Reduction of an E-R Diagram to Tables

Topic 5: Mapping of EER Diagrams to Relations

Database Design Process. Requirements Collection & Analysis

Lecture3: Data Modeling Using the Entity-Relationship Model.

Entity-Relationship Model

Chapter 6: Entity-Relationship Model. The Next Step: Designing DB Schema. Identifying Entities and their Attributes. The E-R Model.

The Next Step: Designing DB Schema. Chapter 6: Entity-Relationship Model. The E-R Model. Identifying Entities and their Attributes.

Using High-Level Conceptual Data Models for Database Design A Sample Database Application Entity Types, Entity Sets, Attributes, and Keys

Roadmap of This Lecture. Weak Entity Sets Extended E-R Features Reduction to Relation Schemas Database Design UML*

Chapter 7: Entity-Relationship Model. Chapter 7: Entity-Relationship Model

Database Technology. Topic 4: Enhanced Entity- Relationship (EER) Modeling

Chapter 9 Outline. Relational Database Design by ER and EERto-Relational. Mapping Fundamentals of Database Systems

4. Entity Relationship Model

Entity-Relationship Model. Dr. Samaresh Mishra, School of Computer Engineering, KIIT University, Bhubaneswar

Chapter 2 ENTITY RELATIONSHIP MODEL

SVY2001: Databases for GIS

Chapter 6. Advanced Data Modeling. Database Systems: Design, Implementation, and Management, Seventh Edition, Rob and Coronel

Conceptual Data Modeling and the Entity- Relationship Model. Department of Computer Science Northern Illinois University September 2014

The Entity-Relationship Model. Steps in Database Design

Chapter 3 The Enhanced E-R Model

Conceptual Database Design (ER modeling) Chapter Three

KDI EER: The Extended ER Model

Module 2 : Entity-Relationship Model 15

COMP 244. ER-Diagram Notations. Entity-Relationship Diagrams DATABASE CONCEPTS & APPLICATIONS. Database Concepts & Applications 1.

Chapter 11 Object and Object- Relational Databases

King Fahd University of Petroleum and Minerals

Chapter 7: Entity-Relationship Model

Database Principles: Fundamentals of Design, Implementation, and Management Tenth Edition. Chapter 7 Data Modeling with Entity Relationship Diagrams

Data Analysis 3. SET08104 Database Systems. Napier University

MIS Database Systems Entity-Relationship Model.

Copyright 2016 Ramez Elmasri and Shamkant B. Navathe

COMP 244 DATABASE CONCEPTS & APPLICATIONS

COSC 304 Introduction to Database Systems Enhanced Entity-Relationship (EER) Modeling

Database Applications (15-415)

CONCEPTUAL DESIGN: ER TO RELATIONAL TO SQL

Advance Database Management System

Chapter 3 Data Modeling Using the Entity- Relationship (ER) Model

Database Management System (15ECSC208) UNIT I: Chapter 2: Relational Data Model and Relational Algebra

COMP Instructor: Dimitris Papadias WWW page:

Conceptual Data Models for Database Design

Object Modeling. Entity-Relationship (ER) diagrams (1976) Object Modelling Technique (OMT) diagrams (1991)

Unit1: Introduction. Database System Concepts, 6 th Ed. Silberschatz, Korth and Sudarshan See for conditions on re-use

Data Modeling Using the Entity-Relationship (ER) Model

Database Systems: Design, Implementation, and Management Tenth Edition. Chapter 4 Entity Relationship (ER) Modeling

SOLUTIONS TO REVIEW QUESTIONS AND EXERCISES FOR PART 3 - DATABASE ANALYSIS AND DESIGN (CHAPTERS 10 15)

Intro to DB CHAPTER 6

Data Analysis 3. Chapter 2.3 V3.0. Napier University Dr Gordon Russell

MTAT Introduction to Databases

Unified Modeling Language (UML)

Database Principles: Fundamentals of Design, Implementation, and Management Tenth Edition. Chapter 7 Data Modeling with Entity Relationship Diagrams

OVERVIEW OF DATABASE DEVELOPMENT

CSIT5300: Advanced Database Systems

LECTURE 6: GUIDELINES FOR GOOD RELATIONAL DESIGN MAPPING ERD TO RELATIONS

High-Level Database Models (ii)

The DBMS accepts requests for data from the application program and instructs the operating system to transfer the appropriate data.

Transcription:

LELCTURE 4: ENHANCED ENTITY-RELATIONSHIP MODELING (EER) Ref. Chapter12 from Database Systems: A Practical Approach to Design, Implementation and Management. Thomas Connolly, Carolyn Begg. IS220 : D at ab ase Fundamentals

Chapter Objectives 2 In this chapter you will learn: The limitations of the basic concepts of the Entity Relationship (ER) model and the requirements to represent more complex applications using additional data modeling concepts. The most useful additional data modeling concepts of the Enhanced Entity Relationship (EER) model called specialization/generalization and inheritance.

Main Terms 3 Enhanced ER model. Specialization Generalization Inheritance. Participation constraints. Disjoint constraints.

4 Enhanced Entity-Relationship (EER) Model Enhanced Entity-Relationship (EER) Model is an ER model supported with additional semantic concepts. Semantic concepts supported: Specialization Generalization

Specialization 5 Specialization: Top-down design process; we designate sub-groupings within an entity type that are distinctive from other entities in the set.

Generalization 6 Generalization: A bottom-up design process combine a number of entity types that share the same features into a higher-level (superclass) entity type. Specialization and generalization are simple inversions of each other; they are represented in an EER diagram in the same way.

Specialization/ Generalization 7 The sub-groupings (subclasses) become lower-level entity types that have attributes or participate in relationships that do not apply to the higher-level entity set (superclass).

Superclass/Subclass Relationship 8 Superclass IS_A relationship 1:1 Subclass MANAGER STAFF SECRETARY SALES PERSONNEL

Inheritance 9 A subclass entity type inherits all the attributes and relationship participation of the superclass entity type to which it is linked. An entity in a subclass represents the same real world object as in the superclass, and may possess subclass-specific attributes, and sometimes relationships, as well as those associated with the superclass.

Inheritance (cont.) 10 shared attributes name dob address Shared relationship Superclass STAFF contract COMPANY SALES Subclass require CAR PERSONNEL Unshared attributes car allowance sales area Unshared relationship

11 Constraints on Specialization/Generalization There are two constraints that may apply to a specialization/ generalization: Participation constraint Disjoint constraints.

Participation Constraints 12 Participation constraint determines whether every member in the superclass must participate as a member of a subclass. Two types of participation constraints: Mandatory (total) Optional (partial)

Participation Constraints (cont.) 13 Mandatory (total) participation where every member in the superclass must also be a member of a subclass. STAFF salary FULL-TIME STAFF PART-TIME STAFF Hourly-rate

Participation Constraints (cont.) 14 Optional (partial) participation where a member in the superclass need not belong to any of its subclasses. STAFF MANAGER SECRETARY SALES PERSONNEL

Disjoint Constraints 15 Disjoint constraint describes the relationship between members of the subclasses & indicates whether it is possible for a member of a subclass to be a member of one, or more than one, subclasses. Two types of disjoint constraints: Disjoint Non-Disjoint

Disjoint Constraints (cont.) 16 Disjoint constraint (d): when an entity can be a member of only one of the subclasses of the specialization. STAFF d salary FULL-TIME STAFF PART-TIME STAFF Hourly-rate

Disjoint Constraints (cont.) 17 Non-disjoint constraints (o): an entity is a member of more than one subclass of specialization. Entity types may overlap. STAFF o MANAGER SECRETARY SALES PERSONNEL

Summary of ER notations 18 ENTITY ATTRIBUTE WEAK ENTITY RELATIONSHIP IDENTIFYING RELATIONSHIP KEY ATTRIBUTE MULTI-VALUED COMPOSITE DERIVED

Summary of ER notations (cont.) 19 1 M CARDINALITY CONSTRAINTS (min,max) PARTICIPATION CONSTRAINTS

Summary of EER notations 20 d o Disjoint constraint Non-Disjoint constraint Total Participation Optional Participation