4 1 Chapter 4 Entity Relationship (ER) Modeling Database Systems: Design, Implementation, and Management, Sixth Edition, Rob and Coronel.

Slides:



Advertisements
Similar presentations
Entity Relationship (ER) Modeling
Advertisements

Chapter # 4 BIS Database Systems
Entity Relationship (E-R) Modeling
Entity Relationship (E-R) Modeling Hachim Haddouti
Advanced Data Modeling
Entity Relationship (ER) Modeling
Chapter 4 Entity Relationship (E-R) Modeling
Entity Relationship (ER) Modeling
Chapter 4 Entity Relationship (ER) Modeling
4 1 Chapter 4 Entity Relationship (ER) Modeling Database Systems: Design, Implementation, and Management, Sixth Edition, Rob and Coronel.
Database Systems: Design, Implementation, and Management Eighth Edition Chapter 4 Entity Relationship (ER) Modeling.
Chapter 4 Entity Relationship (E-R) Modeling
Entity Relationship (ER) Modeling
Entity Relationship (ER) Modeling
Chapter 6 Advanced Data Modelling
Entity Relationship (E-R) Modeling
Chapter Five Data Modeling with the Entity-Relationship Model.
Database Systems: Design, Implementation, & Management, 5 th Edition, Rob & Coronel 1 Data Models: Degrees of Data Abstraction l Modified ANSI/SPARC Framework.
Chapter 4 Entity Relationship (ER) Modeling
Database Systems: Design, Implementation, and Management Tenth Edition
Entity-Relationship Model
Chapter 4 Entity Relationship (E-R) Modeling
Chapter Five Data Modeling with the Entity-Relationship Model.
BTM 382 Database Management Chapter 4: Entity Relationship (ER) Modeling Chitu Okoli Associate Professor in Business Technology Management John Molson.
ER Diagram Notation. E-R Diagram: Chen Model Entity – represented by a rectangle with its name in capital letters. Relationships – represented by an active.
Chapter 4 Entity Relationship (E-R) Modeling
3 Chapter 3 Entity Relationship (E-R) Modeling Database Systems: Design, Implementation, and Management, Fifth Edition, Rob and Coronel.
DeSiamorewww.desiamore.com/ifm1 Database Management Systems (DBMS)  B. Computer Science and BSc IT Year 1.
Chapter 7 Data Modeling with Entity Relationship Diagrams Database Principles: Fundamentals of Design, Implementation, and Management Tenth Edition.
ITEC 3220M Using and Designing Database Systems Instructor: Prof. Z.Yang Course Website: 3220m.htm
4 1 Chapter 4 Entity Relationship (ER) Modeling Database Systems: Design, Implementation, and Management, Seventh Edition, Rob and Coronel.
Chapter 5 Entity Relationship (ER) Modelling
1 ER Modeling BUAD/American University Entity Relationship (ER) Modeling.
Database Systems: Design, Implementation, and Management Tenth Edition Chapter 4 Entity Relationship (ER) Modeling.
Database Systems: Design, Implementation, and Management Eighth Edition Chapter 4 Entity Relationship (ER) Modeling.
Chapter 4 Entity Relationship (ER) Modeling.  ER model forms the basis of an ER diagram  ERD represents conceptual database as viewed by end user 
4 1 Database Systems: Design, Implementation, & Management, 7 th Edition, Rob & Coronel Relationship Degree Indicates number of entities or participants.
Database Design – Lecture 5 Conceptual Data Modeling – adding attributes.
DeSiamorePowered by DeSiaMore1 Database Management Systems (DBMS)  B. Computer Science and BSc IT Year 1.
3 & 4 1 Chapters 3 and 4 Drawing ERDs October 16, 2006 Week 3.
Chapter 9: Logical Database Design and the Relational Model (ERD Mapping)
Chapter 7 Data Modeling with Entity Relationship Diagrams
Msigwaemhttp//:msigwaem.ueuo.com/1 Database Management Systems (DBMS)  B. Computer Science and BSc IT Year 1.
1 A Demo of Logical Database Design. 2 Aim of the demo To develop an understanding of the logical view of data and the importance of the relational model.
3 & 4 1 Database Systems: Design, Implementation, & Management, 7 th Edition, Rob & Coronel Keys Consists of one or more attributes that determine other.
Database Systems: Design, Implementation, and Management Ninth Edition Chapter 4 Entity Relationship (ER) Modeling.
AL-MAAREFA COLLEGE FOR SCIENCE AND TECHNOLOGY INFO 232: DATABASE SYSTEMS CHAPTER 4 ENTITY RELATIONSHIP (ER) MODELING Instructor Ms. Arwa Binsaleh 1.
Entity Relationship Modeling
Database Design – Lecture 4 Conceptual Data Modeling.
Entity Relationship Model: E-R Modeling 1 Database Design.
The Entity-Relationship Model, P. I R. Nakatsu. Data Modeling A data model is the relatively simple representation, usually graphic, of the structure.
Chapter 4 Entity Relationship (E-R) Modeling
David M. Kroenke and David J. Auer Database Processing Fundamentals, Design, and Implementation Chapter Five: Data Modeling with the Entity-Relationship.
Department of Mathematics Computer and Information Science1 CS 351: Database Management Systems Christopher I. G. Lanclos Chapter 4.
Entity Relationship Modeling
Entity Relationship (E-R) Model
TMC2034 Database Concept and Design
Chen’s Type Guidance.
Entity Relationship (E-R) Modeling
Entity Relationship (E-R) Modeling
Tables and Their Characteristics
Database Design – Lecture 4
Chapter 4 Entity Relationship (ER) Modeling
Database Systems: Design, Implementation, and Management Tenth Edition
Review of Week 1 Database DBMS File systems vs. database systems
Chapter 4 Entity Relationship (ER) Modeling
Entity-Relationship Diagram (ERD)
ER MODELING Instructor: SAMIA ARSHAD
Entity Relationship (ER) Modeling
Chapter # 4 Entity Relationship (ER) Modeling.
Presentation transcript:

4 1 Chapter 4 Entity Relationship (ER) Modeling Database Systems: Design, Implementation, and Management, Sixth Edition, Rob and Coronel

4 2 Database Systems: Design, Implementation, & Management, 6 th Edition, Rob & Coronel The Entity Relationship (ER) Model ER model forms the basis of an ER diagram ERD represents the conceptual database as viewed by end user ERDs depict the ER model’s three main components: –Entities –Attributes –Relationships

4 3 Database Systems: Design, Implementation, & Management, 6 th Edition, Rob & Coronel Entities Refers to the entity set and not to a single entity occurrence Corresponds to a table and not to a row in the relational environment In both the Chen and Crow’s Foot models, an entity is represented by a rectangle containing the entity’s name Entity name, a noun, is usually written in capital letters

4 4 Database Systems: Design, Implementation, & Management, 6 th Edition, Rob & Coronel Attributes Characteristics of entities In Chen model, attributes are represented by ovals and are connected to the entity rectangle with a line Each oval contains the name of the attribute it represents In the Crow’s Foot model, the attributes are simply written in the attribute box below the entity rectangle

4 5 Database Systems: Design, Implementation, & Management, 6 th Edition, Rob & Coronel The Attributes of the STUDENT Entity

4 6 Database Systems: Design, Implementation, & Management, 6 th Edition, Rob & Coronel Domains Attributes have a domain: –The attribute’s set of possible values Attributes may share a domain

4 7 Database Systems: Design, Implementation, & Management, 6 th Edition, Rob & Coronel Primary Keys Underlined in the ER diagram Key attributes are also underlined in frequently used table structure shorthand Ideally composed of only a single attribute Possible to use a composite key: –Primary key composed of more than one attribute

4 8 Database Systems: Design, Implementation, & Management, 6 th Edition, Rob & Coronel The CLASS Table (Entity) Components and Contents

4 9 Database Systems: Design, Implementation, & Management, 6 th Edition, Rob & Coronel Attributes Composite attribute Simple attribute Single-value attribute Multivalued attributes

4 10 Database Systems: Design, Implementation, & Management, 6 th Edition, Rob & Coronel A Multivalued Attribute in an Entity

4 11 Database Systems: Design, Implementation, & Management, 6 th Edition, Rob & Coronel Splitting the Multivalued Attribute into New Attributes

4 12 Database Systems: Design, Implementation, & Management, 6 th Edition, Rob & Coronel Components of the Multivalued Attribute

4 13 Database Systems: Design, Implementation, & Management, 6 th Edition, Rob & Coronel A New Entity Set Composed of a Multivalued Attribute’s Components

4 14 Database Systems: Design, Implementation, & Management, 6 th Edition, Rob & Coronel Derived Attributes Attribute whose value may be calculated (derived) from other attributes Need not be physically stored within the database Can be derived by using an algorithm

4 15 Database Systems: Design, Implementation, & Management, 6 th Edition, Rob & Coronel Depiction of a Derived Attribute

4 16 Database Systems: Design, Implementation, & Management, 6 th Edition, Rob & Coronel End of Week 3 Project Assignment Phase 1

4 17 Database Systems: Design, Implementation, & Management, 6 th Edition, Rob & Coronel Relationships Association between entities Participants: –Entities that participate in a relationship Relationships between entities always operate in both directions Relationship can be classified as 1:M Relationship classification is difficult to establish if you only know one side

4 18 Database Systems: Design, Implementation, & Management, 6 th Edition, Rob & Coronel Connectivity and Cardinality Connectivity –Used to describe the relationship classification Cardinality –Expresses the specific number of entity occurrences associated with one occurrence of the related entity Established by very concise statements known as business rules

4 19 Database Systems: Design, Implementation, & Management, 6 th Edition, Rob & Coronel Connectivity and Cardinality in an ERD

4 20 Database Systems: Design, Implementation, & Management, 6 th Edition, Rob & Coronel RELATIONSHIP Strength Existence dependence –Entity’s existence depends on the existence of one or more other entities Existence independence –Entity can exist apart from one or more related entities Weak (non-identifying) relationships –One entity is not existence-independent on another entity Strong (Identifying) Relationships –Related entities are existence-dependent

4 21 Database Systems: Design, Implementation, & Management, 6 th Edition, Rob & Coronel A Weak (Non-Identifying) Relationship Between COURSE and CLASS

4 22 Database Systems: Design, Implementation, & Management, 6 th Edition, Rob & Coronel A Weak Relationship Between COURSE and CLASS

4 23 Database Systems: Design, Implementation, & Management, 6 th Edition, Rob & Coronel A Strong (Identifying) Relationship Between COURSE and CLASS

4 24 Database Systems: Design, Implementation, & Management, 6 th Edition, Rob & Coronel Relationship Participation Optional: –One entity occurrence does not require a corresponding entity occurrence in a particular relationship Mandatory: –One entity occurrence requires a corresponding entity occurrence in a particular relationship

4 25 Database Systems: Design, Implementation, & Management, 6 th Edition, Rob & Coronel An Optional CLASS Entity in the Relationship PROFESSOR teaches CLASS

4 26 Database Systems: Design, Implementation, & Management, 6 th Edition, Rob & Coronel COURSE and CLASS in a Mandatory Relationship

4 27 Database Systems: Design, Implementation, & Management, 6 th Edition, Rob & Coronel Relationship Strength and Weak Entities Weak entity meets two conditions –Existence-dependent: Cannot exist without entity with which it has a relationship –Has primary key that is partially or totally derived from the parent entity in the relationship Database designer usually determines whether an entity can be described as weak based on the business rules

4 28 Database Systems: Design, Implementation, & Management, 6 th Edition, Rob & Coronel A Weak Entity in an ERD

4 29 Database Systems: Design, Implementation, & Management, 6 th Edition, Rob & Coronel A Weak Entity in a Strong Relationship

4 30 Database Systems: Design, Implementation, & Management, 6 th Edition, Rob & Coronel Relationship Degree Indicates number of associated entities or participants Unary relationship –Association is maintained within a single entity Binary relationship –Two entities are associated Ternary relationship –Three entities are associated

4 31 Database Systems: Design, Implementation, & Management, 6 th Edition, Rob & Coronel Three Types of Relationships

4 32 Database Systems: Design, Implementation, & Management, 6 th Edition, Rob & Coronel The Implementation of a Ternary Relationship

4 33 Database Systems: Design, Implementation, & Management, 6 th Edition, Rob & Coronel Recursive Relationships Relationship can exist between occurrences of the same entity set Naturally found within a unary relationship

4 34 Database Systems: Design, Implementation, & Management, 6 th Edition, Rob & Coronel An ER Representation of Recursive Relationships

4 35 Database Systems: Design, Implementation, & Management, 6 th Edition, Rob & Coronel The 1:1 Recursive Relationship “EMPLOYEE is Married to EMPLOYEE”

4 36 Database Systems: Design, Implementation, & Management, 6 th Edition, Rob & Coronel Implementation of the M:N Recursive “PART Contains PART” Relationship

4 37 Database Systems: Design, Implementation, & Management, 6 th Edition, Rob & Coronel Implementation of the 1:M “EMPLOYEE Manages EMPLOYEE” Recursive Relationship

4 38 Database Systems: Design, Implementation, & Management, 6 th Edition, Rob & Coronel Entity Supertypes and Subtypes Generalization hierarchy –Depicts a relationship between a higher-level supertype entity and a lower-level subtype entity Supertype entity –Contains shared attributes Subtype entity –Contains unique attributes

4 39 Database Systems: Design, Implementation, & Management, 6 th Edition, Rob & Coronel Nulls Created by Unique Attributes

4 40 Database Systems: Design, Implementation, & Management, 6 th Edition, Rob & Coronel A Generalization Hierarchy

4 41 Database Systems: Design, Implementation, & Management, 6 th Edition, Rob & Coronel Disjoint Subtypes Also known as non-overlapping subtypes –Subtypes that contain a subset of the supertype entity set –Each entity instance (row) of the supertype can appear in only one of the disjoint subtypes Supertype and its subtype(s) maintain a 1:1 relationship

4 42 Database Systems: Design, Implementation, & Management, 6 th Edition, Rob & Coronel The EMPLOYEE/PILOT Supertype/Subtype Relationship

4 43 Database Systems: Design, Implementation, & Management, 6 th Edition, Rob & Coronel A Supertype/Subtype Relationship

4 44 Database Systems: Design, Implementation, & Management, 6 th Edition, Rob & Coronel A Supertype/Subtype Relationship in an ERD

4 45 Database Systems: Design, Implementation, & Management, 6 th Edition, Rob & Coronel A Comparison of ER Modeling Symbols

4 46 Database Systems: Design, Implementation, & Management, 6 th Edition, Rob & Coronel The Chen Representation of the Invoicing Problem

4 47 Database Systems: Design, Implementation, & Management, 6 th Edition, Rob & Coronel The Crow’s Foot Representation of the Invoicing Problem

4 48 Database Systems: Design, Implementation, & Management, 6 th Edition, Rob & Coronel The Rein85 Representation of the Invoicing Problem

4 49 Database Systems: Design, Implementation, & Management, 6 th Edition, Rob & Coronel The IDEF1X Representation of the Invoicing Problem

4 50 Database Systems: Design, Implementation, & Management, 6 th Edition, Rob & Coronel Developing an ER Diagram Database design is an iterative rather than a linear or sequential process Iterative process –Based on repetition of processes and procedures

4 51 Database Systems: Design, Implementation, & Management, 6 th Edition, Rob & Coronel Components of the ER Model

4 52 Database Systems: Design, Implementation, & Management, 6 th Edition, Rob & Coronel The Completed Tiny College ERD