Entity-Relationship Data Model Alex Ostrovsky. Presentation Overview ► Short historical overview ► Elements of E-R Model ► Basic organization & relationships.

Slides:



Advertisements
Similar presentations
Chapter 2.1 V3.1 Napier University Dr Gordon Russell
Advertisements

Database Systems: Design, Implementation, and Management Tenth Edition
1 Database Theoretic Basis Entity Relationship (E-R) Modeling Database Theoretic Basis Entity Relationship (E-R) Modeling.
Dale Roberts 1 Department of Computer and Information Science, School of Science, IUPUI Dale Roberts, Lecturer Computer Science, IUPUI
ENTITY RELATIONSHIP MODELLING
Entity-Relationship Model
Functional Dependencies - Example
Entity-Relationship Model. The process of designing a database begins with: –an analysis of what information the database must hold, and –the relationships.
Lecturer: Sebastian Coope Ashton Building, Room G.18 COMP 201 web-page: Lecture.
System Analysis - Data Modeling
Entity-Relationship Data Model CS 157A Professor Sin-Min Lee Student: Yen-Chu Pan.
Entity-Relationship Model Lecture 2. Database Modeling and Implementation Process Ideas ER DesignRelational Schema Relational DBMS Implementation.
System Concepts and Architecture Rose-Hulman Institute of Technology Curt Clifton.
Entity-Relationship Model
M.P. Johnson, DBMS, Stern/NYU, Spring C : Database Management Systems Lecture #2 Matthew P. Johnson Stern School of Business, NYU Spring, 2005.
1–1 The E-R Model Prof. Sin-Min Lee Department of Computer Science.
Slides adapted from A. Silberschatz et al. Database System Concepts, 5th Ed. Entity-Relationship Model Database Management Systems I Alex Coman, Winter.
Entity-Relationship Model
1 The Entity-Relationship Data Model Chapter 2 (Database Design)
CS411 Database Systems Kazuhiro Minami
Chapter 3 Data Modeling Using the Entity- Relationship (ER) Model Dr. Bernard Chen Ph.D. University of Central Arkansas.
Entity Relationship Modeling Objectives: To illustrate how relationships between entities are defined and refined. To know how relationships are incorporated.
DAVID M. KROENKE’S DATABASE PROCESSING, 10th Edition © 2006 Pearson Prentice Hall 5-1 David M. Kroenke’s Chapter Five: Data Modeling with the Entity-Relationship.
DeSiamorewww.desiamore.com/ifm1 Database Management Systems (DBMS)  B. Computer Science and BSc IT Year 1.
Entity Relationship Modelling. What is Entity Relationship Modelling? The Entity-Relationship model is – ” “ a data model for high-level descriptions.
ICOM 5016 – Introduction to Database Systems Lecture 4 Dr. Manuel Rodriguez Department of Electrical and Computer Engineering University of Puerto Rico,
Database Systems The Entity-Relationship Model
CS411 Database Systems Kazuhiro Minami 02: The Entity-Relationship Model.
1 ER Modeling BUAD/American University Entity Relationship (ER) Modeling.
Entity-Relationship Data Model N. Harika Lecturer(csc)
Chapter 2 Data Models Database Systems: Design, Implementation, and Management, Rob and Coronel Adapted for INFS-3200.
Databases : Entity-Relationship Model 2007, Fall Pusan National University Ki-Joune Li These slides are made from the materials that Prof. Jeffrey D. Ullman.
Chapter 3 Data Modeling Using the Entity- Relationship (ER) Model Dr. Bernard Chen Ph.D. University of Central Arkansas Fall 2008.
©Silberschatz, Korth and Sudarshan2.1Database System Concepts Chapter 2: Entity-Relationship Model Entity Sets Relationship Sets Design Issues Mapping.
Entity-Relationship Model Using High-Level Conceptual Data Models for Database Design Entity Types, Sets, Attributes and Keys Relationship Types, Sets,
Lecture 4 Conceptual Data Modeling. Objectives Define terms related to entity relationship modeling, including entity, entity instance, attribute, relationship,
3 & 4 1 Chapters 3 and 4 Drawing ERDs October 16, 2006 Week 3.
Conceptual Database Design. Building an Application with a DBMS Requirements modeling (conceptual, pictures) –Decide what entities should be part of the.
The Relational Model 01/28/2014 – Material from Chapter 4 (Chap2 and Chap3 make an appearance)
© D. Wong Ch. 2 Entity-Relationship Data Model (continue)  Data models  Entity-Relationship diagrams  Design Principles  Modeling of constraints.
Entity-Relationship Model
CPSC 603 Database Systems Lecturer: Laurie Webster II, M.S.S.E., M.S.E.E., M.S.BME, Ph.D., P.E. Lecture 2 Introduction to a First Course in Database Systems.
Home Work. Design Principles and Weak Entity Sets.
Computing & Information Sciences Kansas State University Friday, 26 Sep 2008CIS 560: Database System Concepts Lecture 13 of 42 Friday, 26 September 2008.
Copyright © Curt Hill Entities and Relationships The basics and what they have to do with database.
Dale Roberts 1 Department of Computer and Information Science, School of Science, IUPUI Dale Roberts, Lecturer Computer Science, IUPUI
CPSC 603 Database Systems Lecturer: Laurie Webster II, M.S.S.E., M.S.E.E., M.S.BME, Ph.D., P.E. Lecture 4 Introduction to a First Course in Database Systems.
The Entity-Relationship Model CIS 4301 Lecture Notes 1/12/2006.
Entity relationship diagram Name: Quian Crosby Form:6AQ Subject: Information Technology Teacher: Ms. D. Anderson.
2 1 Database Systems: Design, Implementation, & Management, 7 th Edition, Rob & Coronel Data Models Why data models are important About the basic data-modeling.
Rensselaer Polytechnic Institute CSCI-4380 – Database Systems David Goldschmidt, Ph.D.
David M. Kroenke and David J. Auer Database Processing Fundamentals, Design, and Implementation Chapter Five: Data Modeling with the Entity-Relationship.
ERD :: 19 / 1 / Entity-Relationship (ER) Modeling. ER Modeling is a top-down approach to database design. Entity Relationship (ER) Diagram –A.
High-level Database Models Prof. Yin-Fu Huang CSIE, NYUST Chapter 4.
A short revision on entity- relationship modelling.
Modeling: Entity-Relationship Diagrams
Entity-Relationship Data Model
Entity Relationship (E-R) Model
COP Introduction to Database Structures
Session 2 Welcome: To the fourth learning sequence
ER model Ashima Wadhwa.
Entity Relationship Model
Chapter 7: Entity-Relationship Model
Outline of the ER Model By S.Saha
The Entity-Relationship Model
CPSC-310 Database Systems
Chapter 7: Entity-Relationship Model
Entity-Relationship Data Model
Database Dr. Roueida Mohammed.
Chapter 3: Multivalued Dependencies
Presentation transcript:

Entity-Relationship Data Model Alex Ostrovsky

Presentation Overview ► Short historical overview ► Elements of E-R Model ► Basic organization & relationships in E-R Model ► Design principles

History of E-R Model ► E-R Model was proposed by Dr. Peter Chen (currently professor at Louisiana State University) ► Chen’s original paper on E-R Model is the 35 th most sited paper in computer science ► Chen has written papers interconnecting E-R model and linguistics

Introduction ► Database Structure is often called Database Schema ► E-R model is graphical in nature, thus making it easy to analyze and observe relationship between data elements ► Most DBMS are based upon E-R model ► E-R model is not a good match for the sophisticated data structures required in today’s DBMS

Elements of E-R Model ► Data represented graphically via entity- relationship diagram which contains 3 main element types:  Entity sets  Attributes  Relationships

Entity sets, Attributes, Relationships ► Entity set  Is an abstract object, collection of such objects forms an entity set.  Similar notion as in OO design ► Attribute:  Some concrete data (or object type) by which entity set is defined ► Relationship  Specific connection between 2 or more entity sets

E-R Diagram ► Represents E-R elements by nodes of specific shape to indicate kind  Entity sets are represented by rectangles  Attributes are shown as ovals  Relationships correspond to diamonds ► Simple example from the book:

Simple illustration

Instances of E-R diagram ► DB described by E-R will contain specific data (i.e. database instance) ► Each entity set will contain a particular finite set of entities ► Each entity contains a particular value for each attribute ► E-R data is not stored directly in DB

E-R Relationships ► ► Suppose R is a relationship connecting entity sets E and F. Then:   If each member of E can be connected by R to at most one member of F, then we say that R is many- one from E to F. Note that in a many-one relationship from E to F, each entity in F can be connected to many members of E.   If R is both many-one from E to F and many-one from F to E, then we say that R is one-one. In a one-one relationship an entity of either entity set can be connected to at most one entity of the other set.   If R is neither many-one from E to F or from F to E, then we say R is many-many

Multi-way relationships ► ► There is a relationship Sequel-of between the entity set Movies and itself. ► ► To differentiate the two movies in a relationship, one line is labeled by the role Original and one by the role Sequel, indicating the original movie and its sequel, respectively.

Relationships Continued ► Some data models limit relationships to be binary ► It is possible to convert multi-way relationship into a collection of binary many- one relationships ► Need to introduce a connecting entity set, which will act as a bridge between smaller sets which come from splitting a larger multi-way relationship set. ► Connecting entity set might have its own attributes

Design Principles ► Faithfulness:  Design has to comply strictly with specifications  Logical attributes and relationships ► Avoid redundancy ► "Everything should be made as simple as possible, but not simpler.” Albert Einstein ► Choose right relationships ► Select right elements  Many choices exist between using attributes and using entity set/relationship combinations  An attribute is simpler to implement than either entity set or a relationship

Design Principals Cont. ► To replace an entity set by an attribute or attributes of several entity sets 3 conditions must be enforced:   All relationships in which entity set is involved must have arrows entering it. That is, it must be the “one” in many-one relationships, or its generalization for the case of multi-way relationships.   The attributes for E must collectively identify an entity. if there are several attributes, then no attribute must depend on the other attributes   No relationship involves E more than once

Thank You.

References ► Dr. Chen’s homepage: ► Database Systems: A First Course, J.D. Ullman & J. Widom ► relationship_diagram relationship_diagram relationship_diagram ► ► hip_diagram hip_diagram hip_diagram