Entity-Relationship Model. From Chapter 5, Kroenke book

Similar documents
David M. Kroenke and David J. Auer Database Processing Fundamentals, Design, and Implementation

Chapter 2 Entity-Relationship Data Modeling: Tools and Techniques. Fundamentals, Design, and Implementation, 9/e

CS Database Design - Assignments #3 Due on 30 March 2015 (Monday)

Chapter 2 Entity-Relationship Data Modeling: Tools and Techniques. Fundamentals, Design, and Implementation, 9/e

Task: Design an ER diagram for that problem. Specify key attributes of each entity type.

CIS 330: Web-driven Web Applications. Lecture 2: Introduction to ER Modeling

DataBase Lab Lab # 7 ER Using ERWin

Database Systems: Design, Implementation, and Management Tenth Edition. Chapter 4 Entity Relationship (ER) Modeling

1/24/2012. Chapter 7 Outline. Chapter 7 Outline (cont d.) CS 440: Database Management Systems

Non-overlappingoverlapping. Final outcome of the worked example On pages R&C pages R&C page 157 Fig 3.52

Entity Relationship Diagram (ERD): Basics

Answer 2.3 The ER diagram is shown in Figure 2.1.

Represent entities and relations with diagrams

Objectives of logical design... Transforming the ERD diagram into relations. Relational database components. Mapping a composite attribute

Database Systems: Design, Implementation, and Management Tenth Edition. Chapter 4 Entity Relationship (ER) Modeling

Chapter 4 Entity Relationship Modeling In this chapter, you will learn:

Database Principles: Fundamentals of Design, Implementation, and Management Tenth Edition. Chapter 7 Data Modeling with Entity Relationship Diagrams

Chapter 2: Entity-Relationship Model. Entity Sets. Entity Sets customer and loan. Attributes. Relationship Sets. A database can be modeled as:

Topic 5: Mapping of EER Diagrams to Relations

THE ENTITY- RELATIONSHIP (ER) MODEL CHAPTER 7 (6/E) CHAPTER 3 (5/E)

Conceptual Data Modeling and the Entity- Relationship Model. Department of Computer Science Northern Illinois University September 2014

4 Data Modeling and the Entity-Relationship Model (cont.)

Using High-Level Conceptual Data Models for Database Design A Sample Database Application Entity Types, Entity Sets, Attributes, and Keys

More on the Chen Notation

Chapter 4. In this chapter, you will learn:

The Entity Relationship Model

MTAT Introduction to Databases

Multiple Choice Questions

Introduction to Data Management. Lecture #3 (Conceptual DB Design) Instructor: Chen Li

COMP 244. ER-Diagram Notations. Entity-Relationship Diagrams DATABASE CONCEPTS & APPLICATIONS. Database Concepts & Applications 1.

LAB 2 Notes. Conceptual Design ER. Logical DB Design (relational) Schema Refinement. Physical DD

Chapter 2 Conceptual Modeling. Objectives

Module 2 : Entity-Relationship Model 15

CSE 530A. ER Model. Washington University Fall 2013

ER modeling. Lecture 4

Carnegie Mellon Univ. Dept. of Computer Science /615 - DB Applications. Problem. Faloutsos - Pavlo CMU SCS /615

Fundamentals, Design, and Implementation, 9/e Copyright 2004 Database Processing: Fundamentals, Design, and Implementation, 9/e by David M.

Conceptual Database Design. COSC 304 Introduction to Database Systems. Entity-Relationship Modeling. Entity-Relationship Modeling

COMP 244 DATABASE CONCEPTS & APPLICATIONS

Database Management System 6 ER Modeling...

Chapter # 4 Entity Relationship (ER) Modeling

Introduction to modeling. ER modelling

Systems Analysis and Design Methods Chapter 7: Data Modeling and Analysis

Conceptual Modeling in ER and UML

Conceptual Data Modeling

Relational Model (cont d) & Entity Relational Model. Lecture 2

Advance Database Management System

A l Ain University Of Science and Technology

Introduction to Database Design

CS 338 The Enhanced Entity-Relationship (EER) Model

Conceptual Data Models for Database Design

Chapter 6: Entity-Relationship Model

ER Model Overview. The Entity-Relationship Model. Database Design Process. ER Model Basics

The DBMS accepts requests for data from the application program and instructs the operating system to transfer the appropriate data.

IS 263 Database Concepts

DATABASE SYSTEMS. Chapter 5 Entity Relationship (ER) Modelling DESIGN IMPLEMENTATION AND MANAGEMENT INTERNATIONAL EDITION ROB CORONEL CROCKETT

Problem. Carnegie Mellon Univ. Dept. of Computer Science /615 - DB Applications

Administrivia. Carnegie Mellon Univ. Dept. of Computer Science /615 - DB Applications. Course Topics. Problem

Introduction to Database Design

Entity Relationship Modeling. From Rob and Coronel (2004), Database Systems: Design, Implementation, and Management

Introduction to Data Management. Lecture #3 (Conceptual DB Design)

Handout 2. A very brief intro to relational databases (with more coming later). Conceptual Data Modeling Entity-Relationship Diagrams.

Overview of Database Design Process Example Database Application (COMPANY) ER Model Concepts

Database Design. ER Model. Overview. Introduction to Database Design. UVic C SC 370. Database design can be divided in six major steps:

CSE 880:Database Systems. ER Model and Relation Schemas

CSC 261/461 Database Systems Lecture 7

Chapter 17. Methodology Logical Database Design for the Relational Model

Introduction to Data Management. Lecture #3 (Conceptual DB Design)

Overview. Introduction to Database Design. ER Model. Database Design

ER DIAGRAM ER) diagram, a graphical representation of entities and their relationships to each other, typically used in computing in regard to the

Unit 2 - Data Modeling. Pratian Technologies (India) Pvt. Ltd.

Lecture3: Data Modeling Using the Entity-Relationship Model.

CSC 261/461 Database Systems Lecture 6. Spring 2017 MW 3:25 pm 4:40 pm January 18 May 3 Dewey 1101

Database Applications (15-415)

Agenda: Understanding Relationship Types Degree and Cardinality with Examples

A l Ain University Of Science and Technology

MIDTERM EXAMINATION Spring 2010 CS403- Database Management Systems (Session - 4) Ref No: Time: 60 min Marks: 38

Objectives Definition iti of terms Importance of data modeling Write good names and definitions for entities, relationships, and attributes Distinguis

Entity Relationship Modelling

CMP-3440 Database Systems

CSCC43H: Introduction to Databases

CLASS DISCUSSION AND NOTES. October AH-5b (2 hardcopies + softcopy); Project Submission Chap. 6 DB Design

System Analysis And Design Methods ENTITY RELATIONSHIP DIAGRAM (ERD) Prof. Ali Khaleghi Eng. Hadi Haedar

Data Modeling Using the Entity-Relationship (ER) Model

Ch 9: Mapping EER to Relational. Follow a seven-step algorithm to convert the basic ER model constructs into relations steps 1-7

CSIT5300: Advanced Database Systems

COSC 304 Introduction to Database Systems. Entity-Relationship Modeling

Database Management System (15ECSC208) UNIT I: Chapter 1: Introduction to DBMS and ER-Model

Chapter Outline. Note 1. Overview of Database Design Process Example Database Application (COMPANY) ER Model Concepts

Major components of ER diagram Practices

Data Modeling Using the Entity- Relationship Model Design & Analysis of Database Systems

KDI EER: The Extended ER Model

System Analysis & design

Chapter 2 ENTITY RELATIONSHIP MODEL

Data Modeling with the Entity Relationship Model. CS157A Chris Pollett Sept. 7, 2005.

Entity-Relationship Model. Dr. Samaresh Mishra, School of Computer Engineering, KIIT University, Bhubaneswar

Database Systems ER Model. A.R. Hurson 323 CS Building

Conceptual Database Design (ER modeling) Chapter Three

Data Modeling During System Analysis. Logical Data Model Stages. What is Conceptual Database Design? Gathering Information for Conceptual

The Entity-Relationship Model. The Entity-Relationship model. The ER model. The Entity-Relationship model. E-R Model Constructs. E-R Model Constructs

Transcription:

Entity-Relationship Model From Chapter 5, Kroenke book

Database Design Process Requirements analysis Conceptual design data model Logical design Schema refinement: Normalization Physical tuning

Problem: University Database Divisions (Colleges) Departments Faculty Students

The College Report

The Department Report

The Department Major Report

The Student Acceptance Letter

Conceptual Design Overview Entity-Relationship (ER) Model What are the entities and relationships for given problem? What information about these entities and relationships should we store? What are the integrity constraints or business rules that hold?

Entities Something that can be identified and the users want to track Entity class Entity instance There are usually many instances of an entity in an entity class.

Attributes Attributes: describe the characteristics of an entity Entity instances: Same attributes Different values

Identifiers Identifiers = attributes that identify entity instances Composite identifiers: Identifiers that consist of two or more attributes

Relationships Relationships: associations between entities No attributes Relationship degree

Cardinality Cardinality means count - a number Maximum cardinality Minimum cardinality

Maximum Cardinality Maximum cardinality: maximum number of entity instances that can participate in a relationship One-to-One [1:1] One-to-Many [1:N] Many-to-Many [N:M]

Minimum Cardinality Minimum cardinality: minimum number of entity instances that must participate in a relationship. zero [0] optional one [1] mandatory

HAS-A Relationships Previous relationships: HAS-A relationships: Each entity instance has a relationship with another entity instance: An EMPLOYEE has one BADGE A BADGE has an assigned EMPLOYEE.

Data Modeling Notation: ERwin

Class Exercise Give examples of the following relationships: Maximum cardinality: One-to-One One-to-Many Many-to-Many Minimum cardinality Optional-Optional Mandatory-Optional Mandatory-Mandatory

ID-Dependent Entities ID-dependent entity: entity (child) whose identifier includes the identifier of another entity (parent) Example: BUILDING : APARTMENT Minimum cardinality from the IDdependent entity to the parent is always one

ID-Dependent Entities A solid line indicates an identifying relationship

Weak Entities A weak entity is an entity whose existence depends upon another entity. All ID-Dependent entities are considered weak. But there are also non-id-dependent weak entities. The identifier of the parent does not appear in the identifier of the weak child entity.

Weak Entities (Continued) A dashed line indicates a nonidentifying relationship Weak entities must be indicated by an accompanying text box in Erwin There is no specific notation for a nonidentifying but weak entity relationship

ID-Dependent and Weak Entities ID-Dependent entity: Identifier depends (includes) another identifier Identifying relationship Ex: BUILDING:APARTMENT Weak entity: existence depends on another entity Ex: MODEL:CAR ID-Dependent Weak Weak does NOT imply ID-Dependent

Subtype Entities Subtype entity: special case of a supertype entity: STUDENT : UNDERGRADUATE or GRADUATE Supertype: all common attributes [discriminator attribute] Subtypes: specific attributes

Subtypes: Exclusive or Inclusive If subtypes are exclusive, one supertype relates to at most one subtype. If subtypes are inclusive, one supertype can relate to one or more subtypes.

Subtypes: Exclusive or Inclusive

Subtypes: IS-A relationships IS-A relationships: a subtype IS A supertype. Supertype and subtypes identifiers are identical Use subtypes if Have attributes that make sense only for subtypes Want to specify a relationship only for subtype or supertype

ER Summary Entities, attributes, identifiers HAS-A Relationships Degree: binary, ternary Maximum cardinality Minimum cardinality Weak entities ID-dependent entities; identifying relationships IS-A Relationships Inclusive, Exclusive

Class Exercise Draw ER diagram for a database used to manage IT360 class (at least 3 entities) Specify entities, attributes, identifiers Specify relationships Specify cardinalities for relationships

Class Exercise Drugwarehouse.com has offered you a free lifetime supply of prescription drugs (no questions asked) if you design its database schema. Given the rising cost of health care, you agree. Here is the information that you gathered: Patients are identified by their SSN, and we also store their names and age Doctors are identified by their SSN, and we also store their names and specialty Each patient has one primary care physician Each doctor has at least one patient