Entity Relationship Diagrams Objectives s Learn the Elements of the E-R model (entities, attributes, and relationships) s Show how to apply the E-R model.

Slides:



Advertisements
Similar presentations
Chapter # 4 BIS Database Systems
Advertisements

Data Modeling and the Entity-Relationship Model
Data Modeling and the Entity-Relationship Model
Data Modeling and the Entity-Relationship Model Chapter Four DAVID M. KROENKE and DAVID J. AUER DATABASE CONCEPTS, 3 rd Edition.
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
IT420: Database Management and Organization
Entity-Relationship Model
Data Modeling and the Entity-Relationship Model
Data Modeling and the Entity-Relationship Model
DAVID M. KROENKE’S DATABASE PROCESSING, 10th Edition © 2006 Pearson Prentice Hall 5-1 COS 346 Day 6.
System Analysis - Data Modeling
DAVID M. KROENKE’S DATABASE PROCESSING, 10th Edition © 2006 Pearson Prentice Hall 5-1 David M. Kroenke Database Processing Tenth Edition Chapter 5 Data.
Chapter Five Data Modeling with the Entity-Relationship Model.
DAVID M. KROENKE’S DATABASE PROCESSING, 10th Edition © 2006 Pearson Prentice Hall 5-1 COS 346 Day 6.
Entity Relationship Diagrams
Fundamentals, Design, and Implementation, 9/e COS 346 Day 2.
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.
Data Modeling and the Entity-Relationship Model Chapter Four DAVID M. KROENKE and DAVID J. AUER DATABASE CONCEPTS, 5 th Edition.
Chapter 4 Entity Relationship (ER) Modeling
Database Systems: Design, Implementation, and Management Tenth Edition
Entity-Relationship Model
CS424 PK, FK, FD Normalization Primary and Foreign Keys Primary and foreign keys are the most basic components on which relational theory is based. Primary.
Chapter Five Data Modeling with the Entity-Relationship Model.
Modern Systems Analysis and Design Third Edition
Copyright 2002 Prentice-Hall, Inc. Modern Systems Analysis and Design Third Edition Jeffrey A. Hoffer Joey F. George Joseph S. Valacich Chapter 10 Structuring.
Oracle Academy -Week 1-.
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.
Chapter 7 Data Modeling with Entity Relationship Diagrams Database Principles: Fundamentals of Design, Implementation, and Management Tenth Edition.
4 1 Chapter 4 Entity Relationship (ER) Modeling Database Systems: Design, Implementation, and Management, Seventh Edition, Rob and Coronel.
Chapter 5 Entity–Relationship Modeling
1 ER Modeling BUAD/American University Entity Relationship (ER) Modeling.
Database Processing: Fundamentals, Design and Implementation, 9/e by David M. KroenkeChapter 2/1 Copyright © 2004 Please……. No Food Or Drink in the class.
4 1 Chapter 4 Entity Relationship (ER) Modeling Database Systems: Design, Implementation, and Management, Sixth Edition, Rob and Coronel.
Systems Analysis and Design in a Changing World, 6th Edition 1 Chapter 4 Domain Classes.
DAVID M. KROENKE’S DATABASE PROCESSING, 10th Edition © 2006 Pearson Prentice Hall, modified by Dr. Lyn Mathis 5-1 David M. Kroenke’s, 10 th ed. Chapter.
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 
Data Modeling IST210 Class Lecture.
Lecture 4 Conceptual Data Modeling. Objectives Define terms related to entity relationship modeling, including entity, entity instance, attribute, relationship,
Database Design – Lecture 5 Conceptual Data Modeling – adding attributes.
3 & 4 1 Chapters 3 and 4 Drawing ERDs October 16, 2006 Week 3.
The Entity-Relationship Model
Chapter 3 The Entity-Relationship Model David M. Kroenke Database Processing © 2000 Prentice Hall.
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.
The Entity-Relationship Model, P. I R. Nakatsu. Data Modeling A data model is the relatively simple representation, usually graphic, of the structure.
David M. Kroenke and David J. Auer Database Processing Fundamentals, Design, and Implementation Chapter Five: Data Modeling with the Entity-Relationship.
Copyright 2002 Prentice-Hall, Inc. Modern Systems Analysis and Design Third Edition Jeffrey A. Hoffer Joey F. George Joseph S. Valacich Chapter 10 Structuring.
IT 5433 LM2 ER & EER Model. Learning Objectives: Explain importance of data modeling Define and use the entity-relationship model Define E/R terms Describe.
Chapter 10 Structuring System Requirements: Conceptual Data Modeling
Business System Development
Data Modeling and the Entity-Relationship Model
Semantic Object Modeling (SOM)
TMC2034 Database Concept and Design
Requirements Become the E-R Data Model
Tables and Their Characteristics
Database Design – Lecture 4
Database Systems: Design, Implementation, and Management Tenth Edition
Chapter 10 Structuring System Requirements: Conceptual Data Modeling
Data Modeling and the Entity-Relationship Model
Database Processing: David M. Kroenke’s Chapter Five:
Entity-Relationship Diagram (ERD)
Chapter 10 Structuring System Requirements: Conceptual Data Modeling
Entity Relationship (ER) Modeling
Chapter # 4 Entity Relationship (ER) Modeling.
Data Modeling and the Entity-Relationship Model
Lecture 10 Structuring System Requirements: Conceptual Data Modeling
Presentation transcript:

Entity Relationship Diagrams Objectives s Learn the Elements of the E-R model (entities, attributes, and relationships) s Show how to apply the E-R model for modeling business situations s To develop data modeling skills s To interpret E-R diagrams

Entities s Entity is something that can be identified in the user’s work environment s Usually a noun s Entities are grouped into classes or sets s A particular entity is an instance of the entity class s Entities are usually depicted in an E-R diagram as a rectangle with the Entity name in capital letters

Attributes s Attributes (sometimes called properties) are characteristics that describe entities s Identifiers are attributes that describe an entity instance s Identifiers may be unique or non-unique s Composite identifiers consist of two or more attributes (ex: phone number: area code and number)

Relationships s Relationships are associations between entities s Relationships are sometimes referred to as “Has-a” or “Is-a” s Three types of binary relationships –One to one –One to Many –Many to Many

Cardinality s The maximum and minimum number of entities that can occur on one side of the relationship.

Entity Relationship Diagrams s There are many diagramming conventions--based on CASE tools (several will be illustrated in class) s Entity--Capital letters in a rectangle s Relationships--Diamonds s Maximum Cardinality--inside the diamond s Minimum Cardinality –Hash mark to indicated entity must exist –Oval to indicate entity may or may not be required

Attributes s Attributes can be shown as ellipses or in lists--see figure 3-6

Weak Entities s A weak entity is sometimes called a dependent entity s A weak entity cannot exist without another type of entity exists s A special type of weak entity is an ID- dependent entity s See figure 3-7 for examples

Subtype Entities s Some entities contain option sets of attributes or subtypes s Structures of subtypes and supertypes are called generalized hierarchies s The relationship is called a IS-A relationship s Subtypes inherit from supertypes s The subtypes may be mutually exclusive or not s See figure 3-8

Business Rules s Business Rules may or may not be included in an E-R diagram; depending on whether the application should enforce the business rules or the rules be enforced manually