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.

Slides:



Advertisements
Similar presentations
1 Database Design I: The Entity- Relationship Model Chapter 5.
Advertisements

Advanced Data Modeling
Entity Relationship (ER) Modeling
4 1 Chapter 4 Entity Relationship (ER) Modeling Database Systems: Design, Implementation, and Management, Sixth Edition, Rob and Coronel.
The Relational Database Model
IT420: Database Management and Organization
Entity-Relationship Model
Chapter 6 Advanced Data Modelling
Database Systems: Design, Implementation, and Management Eighth Edition Chapter 6 Advanced Data Modeling.
Chapter 3 The Relational Model Transparencies © Pearson Education Limited 1995, 2005.
System Analysis - Data Modeling
Chapter 3. 2 Chapter 3 - Objectives Terminology of relational model. Terminology of relational model. How tables are used to represent data. How tables.
DAVID M. KROENKE’S DATABASE PROCESSING, 10th Edition © 2006 Pearson Prentice Hall 5-1 David M. Kroenke Database Processing Tenth Edition Chapter 5 Data.
Relational Model Stores data as tables –Each column contains values about the same attribute –Each column has a distinct name –Each row contains values.
Modeling Data The Entity Relationship Model (ER) For Database Design.
1–1 The E-R Model Prof. Sin-Min Lee Department of Computer Science.
Entity Relationship Diagrams
Data Modeling Entity - Relationship Models. Models Used to represent unstructured problems A model is a representation of reality Logical models  show.
SLIDE 1IS Fall 2002 Database Management: Discussion Session University of California, Berkeley School of Information Management and.
Sunday, June 28, Entity-Relationship and Enhanced Entity-Relationship Conceptual Data Models (Chapters 6 & Section 7.1)
Slides adapted from A. Silberschatz et al. Database System Concepts, 5th Ed. Entity-Relationship Model Database Management Systems I Alex Coman, Winter.
Chapter 8 Structuring System Data Requirements
Entity-Relationship Model
Entity-Relationship (E-R) Model
Modeling & Designing the Database
Database Design & ER Diagrams
Michael F. Price College of Business Chapter 6: Logical database design and the relational model.
Copyright 2002 Prentice-Hall, Inc. Modern Systems Analysis and Design Third Edition Jeffrey A. Hoffer Joey F. George Joseph S. Valacich Chapter 10 Structuring.
Trisha Cummings.  Most people involved in application development follow some kind of methodology.  A methodology is a prescribed set of processes through.
Data Modeling Using the Entity-Relationship Model
Class Agenda – 04/04/2006 Discuss database modeling issues
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 4 The Relational Model.
MIS 385/MBA 664 Systems Implementation with DBMS/ Database Management Dave Salisbury ( )
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.
© 2006 ITT Educational Services Inc. SE350 System Analysis for Software Engineers: Unit 8 Slide 1 Chapter 9 Structuring System Data Requirements.
CSCI 3140 Module 2 – Conceptual Database Design Theodore Chiasson Dalhousie University.
1 ER Modeling BUAD/American University Entity Relationship (ER) Modeling.
Entity Relationship 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.
Concepts and Terminology Introduction to Database.
©Silberschatz, Korth and Sudarshan2.1Database System Concepts Chapter 2: Entity-Relationship Model Entity Sets Relationship Sets Design Issues Mapping.
Chapter 11 & 12 Entity-Relationship (E-R) Model Characteristics of E-R Model Components of E-R Model Example of E-R Model Enhanced E-R Model.
Chapter 9: Logical Database Design and the Relational Model (ERD Mapping)
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.
©Silberschatz, Korth and Sudarshan2.1Database System Concepts Chapter 2: Entity-Relationship Model Entity Sets Relationship Sets Design Issues Mapping.
Chapter 2 : Entity-Relationship Model Entity Sets Relationship Sets Design Issues Mapping Constraints Keys E-R Diagram Extended E-R Features Design of.
Concepts of Database Management, Fifth Edition Chapter 6: Database Design 2: Design Methodology.
 Entity-relationship models (ERM) Entity-relationship models (ERM)  Simple E-R Diagram Simple E-R Diagram  Weak Entity Weak Entity  Strong Entity.
In this session, you will learn to: Map an ER diagram to a table Objectives.
UNIT_2 1 DATABASE MANAGEMENT SYSTEM[DBMS] [Unit: 2] Prepared By Lavlesh Pandit SPCE MCA, Visnagar.
Databases Illuminated Chapter 3 The Entity Relationship Model.
The Entity-Relationship Model, P. I R. Nakatsu. Data Modeling A data model is the relatively simple representation, usually graphic, of the structure.
©Silberschatz, Korth and Sudarshan2.1Database System Concepts Chapter 2: Entity-Relationship Model Entity Sets Relationship Sets Mapping Constraints Keys.
David M. Kroenke and David J. Auer Database Processing Fundamentals, Design, and Implementation Chapter Five: Data Modeling with the Entity-Relationship.
Mapping ER to Relational Model Each strong entity set becomes a table. Each weak entity set also becomes a table by adding primary key of owner entity.
Copyright 2002 Prentice-Hall, Inc. Modern Systems Analysis and Design Third Edition Jeffrey A. Hoffer Joey F. George Joseph S. Valacich Chapter 10 Structuring.
Week 2 Lecture The Relational Database Model Samuel ConnSamuel Conn, Faculty Suggestions for using the Lecture Slides.
Lecture # 14 Chapter # 5 The Relational Data Model and Relational Database Constraints Database Systems.
Database Designsemester Slide 1 Database Design Lecture 7 Entity-relationship modeling Text , 7.1.
COP Introduction to Database Structures
Logical Database Design and the Rational Model
Database Design Goal: specification of database schema Methodology:
Conceptual Design & ERD Modelling
Entity-Relationship Model
Outline of the ER Model By S.Saha
Entity/Relationship Model
Session 2 Welcome: The seventh learning sequence
Entity Relationship (ER) Modeling
Presentation transcript:

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 the enhanced E/R model Describe how super types and sub-types are modeled Explain when you would use an enhanced E/R model

What is Data Modeling? Data modeling is the act of exploring data-oriented structures. Data models can be used for a variety of purposes, from high-level conceptual models to physical data models. With data modeling you identify entity types whereas with class modeling you identify classes. Data attributes are assigned to entity types just as you would assign attributes and operations to classes. Traditional data modeling is different from class modeling because it focuses solely on data – class models allow you to explore both the behavior and data aspects of your domain, with a data model you can only explore data issues.

Three Basic Styles of Data Model: Conceptual - sometimes called domain models, are typically used to explore domain concepts with project stakeholders. Logical (LDM)- logical data model, used to explore the domain concepts, and their relationships, of your problem domain. Physical (PDM)- physical data model, used to design the internal schema of a database, depicting the data tables, the data columns of those tables, and the relationships between the tables.

Data Model: An entity type represents a collection of similar objects. Each entity type will have one or more data attributes.

Entity-Relationship (ER) Model E-R Model captures meanings rather than an actual implementation The E-R Model is viewed as set of: Entities Relationships among entities Symbols used in E-R Diagram Entity – (rectangle) an object that is involved in the enterprise and that be distinguished from other objects Attribute – (oval) describes one aspect of an entity type. Relationship – (diamond) Link – (line)

Entity-Relationship (ER) Model Keys Superkey: an attribute or set of attributes that uniquely identifies an entity Composite key: a key requiring more than one attribute Candidate key: a superkey such that no proper subset of its attributes is also a superkey (minimal superkey – has no unnecessary attributes) Primary key: the candidate key chosen to be used for identifying entities and accessing records. Unless otherwise noted "key" means "primary key" Alternate key: a candidate key not used for primary key Secondary key: attribute or set of attributes commonly used for accessing records, but not necessarily unique Foreign key: term used in relational databases (but not in the E-R model) for an attribute that is the primary key of another table and is used to establish a relationship with that table where it appears as an attribute also.

Enhanced Entity-Relationship (EER) Model One entity type might be a subtype of another. A relationship exists between a entity and the corresponding entity is called IsA. Type Hierarchy: Covering constraint: Union of subtype entities is equal to set of supertype entities. An entity is an element of at least one subtype Disjointness constraint: Sets of subtype entities are disjoint from one another (i.e., the sets are mutually exclusive). An entity can be an element of at most one entity

IsA Typically used in databases to be implemented as Object Oriented Models. The upper entity type is the more abstract entity type (supertype) from which the lower entities inherit its attributes

Super Types and Sub-Types Inheritance - All attributes of the supertype apply to the subtype. The subtype inherits all attributes of its supertype. The key of the supertype is also the key of the subtype Transitivity - This property creates a hierarchy of IsA relationships Example: Student is subtype of Person, Freshman is subtype of Student, therefore Freshman is also a subtype of Person Advantage: Used to create a more concise and readable E-R diagram. It best maps to object oriented approaches either to databases or related applications. Attributes common to different entity sets need not be repeated They can be grouped in one place as attributes of the supertype Attributes of (sibling) subtypes are likely to be different (and should be for this to be very useful)

ER Notations u=er_notations Mandatory- Optional (1:1 Binary)Mandatory-Optional (Complete, disjoint)

ER Notations u=er_notations Crow’s Feet (1-N Binary Identifying) Crow’s Feet (1-N Unary)

Links: Link 1: Link 2: Link 3: Link 4: otations otations