A short revision on entity- relationship modelling.

Slides:



Advertisements
Similar presentations
Chapter 6: Entity-Relationship Model (part I)
Advertisements

Dale Roberts 1 Department of Computer and Information Science, School of Science, IUPUI Dale Roberts, Lecturer Computer Science, IUPUI
Text-Book Chapters (7 and 8) Entity-Relationship Model
Chapter 4 Notes. Entity-Relationship Model E/R Diagrams Weak Entity Sets Converting E/R Diagrams to Relations.
Design Principles: Faithfulness
Weak Entity Sets. Occasionally, entities of an entity set need “help” to identify them uniquely. Example. Crews might have a number and some description,
Weak Entity Sets. Occasionally, entities of an entity set need “help” to identify them uniquely. Entity set E is weak if in order to identify entities.
Databases Revision.
System Concepts and Architecture Rose-Hulman Institute of Technology Curt Clifton.
--The Entity Relationship Model(1)--1 The Entity Relationship Model.
Entity-Relationship Model
The Entity-Relationship Data Model
SLIDE 1IS Fall 2002 Database Management: Discussion Session University of California, Berkeley School of Information Management and.
Slides adapted from A. Silberschatz et al. Database System Concepts, 5th Ed. Entity-Relationship Model Database Management Systems I Alex Coman, Winter.
Murali Mani The Entity- Relationship Model. Murali Mani Database Design Stages Application Requirements Conceptual Design Logical Design Physical Design.
Chapter 4 Entity-Relationship modeling Transparencies © Pearson Education Limited 1995, 2005.
What is a Database Management System? 1. Manages very large amounts of data. 2. Supports efficient access to very large amounts of data. 3. Supports concurrent.
the Entity-Relationship Model
ICOM 5016 – Introduction to Database Systems Lecture 4 Dr. Manuel Rodriguez Department of Electrical and Computer Engineering University of Puerto Rico,
Entity-Relationship Data Model N. Harika Lecturer(csc)
Databases : Entity-Relationship Model 2007, Fall Pusan National University Ki-Joune Li These slides are made from the materials that Prof. Jeffrey D. Ullman.
©Silberschatz, Korth and Sudarshan2.1Database System Concepts Chapter 2: Entity-Relationship Model Entity Sets Relationship Sets Design Issues Mapping.
Database Management Systems MIT Lesson 02 – Database Design (Entity Relationship Diagram) By S. Sabraz Nawaz.
Entity Relationship Diagram. Introduction Definition: Entity-relationship diagram is a data-modeling technique that visualises entities, the attributes.
 Entity-relationship models (ERM) Entity-relationship models (ERM)  Simple E-R Diagram Simple E-R Diagram  Weak Entity Weak Entity  Strong Entity.
© D. Wong Ch. 2 Entity-Relationship Data Model (continue)  Data models  Entity-Relationship diagrams  Design Principles  Modeling of constraints.
Entity-Relationship Model
 An entity-relationship diagram (ERD) is a specialized graphic that illustrates the interrelationships between entities in a database.
ITTelkom Entity Relationship Diagram (1) CS2343 Perancangan Basisdata Relasional.
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.
UNIT_2 1 DATABASE MANAGEMENT SYSTEM[DBMS] [Unit: 2] Prepared By Lavlesh Pandit SPCE MCA, Visnagar.
Databases Illuminated Chapter 3 The Entity Relationship Model.
Databases 1 Fifth lecture. Entity-Relationship Model Diagrams Class hierarchies Weak entity sets From E/R diagrams to Relations 2.
Lecture 03 Entity-Relationship Diagram. Chapter Outline.
Dale Roberts 1 Department of Computer and Information Science, School of Science, IUPUI Dale Roberts, Lecturer Computer Science, IUPUI
DatabaseIM ISU1 Fundamentals of Database Systems Chapter 3 Data Modeling Using Entity-Relationship Model.
Data Modeling Using the Entity-Relationship (ER) Data Model.
1 Announcements Reading for next week: Chapters 8 and 10  Last reading from the text for a little while (I promise) About those database accounts....
Data Modeling Using the Entity- Relationship (ER) Model.
CSE 412/598 DATABASE MANAGEMENT COURSE NOTES 3. ENTITY-RELATIONSHIP CONCEPTUAL MODELING Department of Computer Science & Engineering Arizona State University.
©Silberschatz, Korth and Sudarshan2.1Database System Concepts Chapter 2: Entity-Relationship Model Entity Sets Relationship Sets Mapping Constraints Keys.
Chapter 2: Entity-Relationship Model. 3.2 Chapter 2: Entity-Relationship Model Design Process Modeling Constraints E-R Diagram Design Issues Weak Entity.
©Silberschatz, Korth and Sudarshan7.1Database System Concepts - 6 th Edition Chapter 7: Entity-Relationship Model.
Lecture 3 A short revision of ER and EER modelling See R. Elmasri, S.B. Navathe. Fundamentals of Database Systems (third edition) Addison-wesley. Chapter.
Database -Entity-Relationship Model 2012/03/05.
CS422 Principles of Database Systems Entity-Relationship Model Chengyu Sun California State University, Los Angeles.
High-level Database Models Prof. Yin-Fu Huang CSIE, NYUST Chapter 4.
A short review on entity- relationship modelling.
Copyright © 2011 Pearson Education, Inc. Publishing as Pearson Addison-Wesley Chapter 7 Lecture # 16 July 26,2012 Data Modeling using the Entity Relationship.
Database Designsemester Slide 1 Database Design Lecture 7 Entity-relationship modeling Text , 7.1.
Entity-Relationship Data Model
Contents Design Process Modeling Constraints E-R Diagram Design Issues
Session 2 Welcome: To the fourth learning sequence
Entity-Relationship Model
Entity Relationship Diagram
Entity-Relationship Model
Entity-Relationship Model
Entity Relationship Model
Entity-Relationship Model
Chapter 2: Entity-Relationship Model
Chapter 7 Entity-Relationship Model
Outline of the ER Model By S.Saha
CPSC-310 Database Systems
CPSC-310 Database Systems
The Entity-Relationship Model
Database Modeling using Entity Relationship Model (E-R Model)
Chapter 7: Entity-Relationship Model
Entity Relation Model Tingting Zhang.
ER MODELING Instructor: SAMIA ARSHAD
Entity-Relationship Data Model
Presentation transcript:

A short revision on entity- relationship modelling

Entity/Relationship Models An Entity/Relationship model consists of diagrams to represent designs. Entity like object = ”thing.” Entity types like class = set of ”similar” entities/objects. Attribute = property of entities in an entity type. Relations connect different entity type.

Entity/Relationship Models In diagrams: entity types are rectangles; attributes are oval; relations are diamonds.

Multiway Relationships Usually relationships are binary. That is they connect two entity types. However, there are some cases where three or more entity types must be connected by one relationship. These relationships are called multiway relationships.

Roles A recursive relationship is a relation type where the same entity participates more than one in different roles. We label each edge with the role name.

An Example

Multiplicity of relationships Many to Many relation: Bars serve different beers Many to One relation: Drinkers have favorite beers One to One relation: Breweries have only one best seller

Total participation If all the elements of the entity type E are related to some element of an entity type F via a relationship R, then the participation of E in R is called total participation. Example: breweries must have one best seller beer.

Keys A key is a set of attributes such that no two entities agree on all these attributes. In E/R model every entity type must have a designated key. In E/R diagrams you should underline all attributes of the key.

Weak entity types Entity sets that do not have key attributes of their own are called weak entity types. The remaining attributes come from another (or more) entity type which is related to the weak entity set by an identifying relationship. IN E/R diagrams you should represent weak entity sets as double rectangles represent identifying relationships as double diamonds

Exercise Suppose you are hired to develop a geographical information system. Your task is to develop its databases, with the following information: A continent has a name and contains different countries (e.g., Europe). Each country resides only in one continent. Each country has a name, a population value, official language(s), and its capital city. Each official language may be shared by different countries (e.g.English). Each language has a unique ID (LangID) and a name. Each city carries a name and a population value. Each city resides only in one country. The name of each city is unique within its country. Each river has a unique ID (RiverID), a name, and its length. Rivers run through one or more countries. International treaties are identified by their names. They also contain their subjects as well as starting dates. Each treaty consists of at least two countries. 1.Design and draw an E/R diagram that captures the above information. Be careful to indicate any key and participation constraints (multiplicity constraints). 2.Convert the E/R diagram to a relational database schema.

Exercise A continent has a name and contains different countries (e.g., Europe). Each country resides only in one continent. Each country has a name, a population value, official language(s), and its capital city. Each official language may be shared by different countries (e.g.English). Each language has a unique ID (LangID) and a name. Each city carries a name and a population value. Each city resides only in one country. The name of each city is unique within its country. Each river has a unique ID (RiverID), a name, and its length. Rivers run through one or more countries. International treaties are identified by their names. They also contain their subjects as well as starting dates. Each treaty consists of at least two countries.

Solution

Solution (Cont.)