Chapter 11 (I) CIS458 Sungchul Hong. Chapter 11 - Objectives How to use Entity–Relationship (ER) modelling in database design. Basic concepts associated.

Slides:



Advertisements
Similar presentations
Conceptual Data Modeling: ER
Advertisements

Data Modeling (CB 12) CPSC 356 Database Ellen Walker Hiram College (Includes figures from Database Systems by Connolly & Begg, © Addison Wesley 2002)
Ch5: ER Diagrams - Part 1 Much of the material presented in these slides was developed by Dr. Ramon Lawrence at the University of Iowa.
Entity Relationship (ER) Modeling
Entity Relationship (ER) Modeling
Entity Relationship (ER) Modeling
CSC271 Database Systems Lecture # 22. Summary: Previous Lecture  Applying Database SDLC on DreamHome  Database planning  System definition  Requirements.
Pertemuan Entity Relationship Diagram
Copyright © 2011 Pearson Education, Inc. Publishing as Pearson Addison-Wesley Chapter 7 Data Modeling Using the Entity- Relationship (ER) Model.
Lecture Eleven Entity-Relationship Modelling
Data Modeling ISYS 464. Database Design Process Conceptual database design: –The process of creating a data model independent of implementation details.
Chapter 4 ENTITY-RELATIONSHIP MODELLING.
Database Systems: Design, Implementation, & Management, 5 th Edition, Rob & Coronel 1 Data Models: Degrees of Data Abstraction l Modified ANSI/SPARC Framework.
Entity-Relationship (E-R) Model
Chapter 4 Entity-Relationship modeling Transparencies © Pearson Education Limited 1995, 2005.
Database Management COP4540, SCS, FIU Database Modeling Using the Entity-Relationship Model (Chapter 3)
Entity-Relationship modeling Transparencies
Chapter 12 Entity-Relationship Modeling Pearson Education © 2009.
DeSiamorewww.desiamore.com/ifm1 Database Management Systems (DBMS)  B. Computer Science and BSc IT Year 1.
CSE314 Database Systems Data Modeling Using the Entity- Relationship (ER) Model Doç. Dr. Mehmet Göktürk src: Elmasri & Navanthe 6E Pearson Ed Slide Set.
the Entity-Relationship Model
Entity-relationship Modeling Transparencies 1. ©Pearson Education 2009 Objectives How to use ER modeling in database design. The basic concepts of an.
Entity-Relationship Model
Outline What is ER Model? And Why? Example COMPANY Database
Data Modeling Using the Entity-Relationship (ER) Model
Chapter 5 Entity Relationship (ER) Modelling
Chapter 5 Entity–Relationship Modeling
Copyright © 2011 Pearson Education, Inc. Publishing as Pearson Addison-Wesley Chapter 7 Data Modeling Using the Entity- Relationship (ER) Model.
Entity Relationship Modeling
C HAPTER 11 Entity-Relationship modelling Transparencies © Pearson Education Limited 1995,
1 Pertemuan > > Matakuliah: >/ > Tahun: > Versi: >
Lecture On Database Analysis and Design By- Jesmin Akhter Lecturer, IIT, Jahangirnagar University.
9/10/2012ISC 329 Isabelle Bichindaritz1 Entity Relationship (E-R) Modeling.
© Pearson Education Limited, Chapter 7 Entity-Relationship modeling Transparencies.
Entity-Relationship Modeling Based on Chapter 12.
1 Chapter 11 Entity-Relationship Modeling Transparencies Last Updated: 25 April 2011 By M. Arief
Chapter 12 Entity-Relationship Modeling Pearson Education © 2009.
CS 3630 Database Design and Implementation. Assignment 1 2 What is 3630?
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.
4 1 Database Systems: Design, Implementation, & Management, 7 th Edition, Rob & Coronel Relationship Degree Indicates number of entities or participants.
DeSiamorePowered by DeSiaMore1 Database Management Systems (DBMS)  B. Computer Science and BSc IT Year 1.
Msigwaemhttp//:msigwaem.ueuo.com/1 Database Management Systems (DBMS)  B. Computer Science and BSc IT Year 1.
1 Session 2 Welcome: The fifth learning sequence “ Entity-Relationship Model -2“ E-R Model Recap : In the previous learning sequence, we discussed the.
Chapter 3 Data Modeling Using the Entity-Relationship (ER) Model Copyright © 2004 Pearson Education, Inc.
Data modeling using the entity-relationship model Chapter 3 Objectives How entities, tuples, attributes and relationships among entities are represented.
1 Entity-Relationship Model © Pearson Education Limited 1995, 2005.
Databases Illuminated Chapter 3 The Entity Relationship Model.
Entity Relationship Modeling
Data Modelling Using Entity-Relationship (ER) Model
Part3 Database Analysis and Design Techniques Chapter 05- Entity-Relationship Modeling Lu Wei College of Software and Microelectronics Northwestern Polytechnical.
Database Systems – ER Diagrams EXAMPLE COMPANY DATABASE Requirements of the Company (oversimplified to illustrate) The company is organized into DEPARTMENTs.
Chapter 2 Data Modeling Using the Entity-Relationship (ER) Model Copyright © 2004 Pearson Education, Inc.
1 Database Systems Entity Relationship (E-R) Modeling.
Chapter 3 Data Modeling Using the Entity-Relationship (ER) Model Copyright © 2004 Pearson Education, Inc.
Entity-Relationship Modeling. 2 Entity Type u Entity type –Group of objects with same properties, identified by enterprise as having an independent existence.
Data Modeling and the Entity-Relationship Model CS 475 Lecture Notes.
Chapter 8 Entity-Relationship Modeling Pearson Education © 2009.
CSCI 6315 Applied Database Systems Review for Midterm Exam I Xiang Lian The University of Texas Rio Grande Valley Edinburg, TX 78539
ENTITY-RELATIONSHIP MODELLING. Objectives: How to use Entity–Relationship (ER) modelling in database design. Basic concepts associated with ER model.
Entity Relationship (E-R) Model
Chapter # 3 Data Modeling Using the Entity-Relationship (ER) Model
COP Introduction to Database Structures
Conceptual Design & ERD Modelling
TMC2034 Database Concept and Design
CS 3630 Database Design and Implementation
Entity-Relationship Modeling
Entity-Relationship Modeling
Chapter Entity-Relationship Modeling & Enhanced Entity- Relationship Modeling.
Chapter 7: Entity-Relationship Model
Chapter Entity-Relationship Modeling & Enhanced Entity- Relationship Modeling.
Presentation transcript:

Chapter 11 (I) CIS458 Sungchul Hong

Chapter 11 - Objectives How to use Entity–Relationship (ER) modelling in database design. Basic concepts associated with ER model. Diagrammatic technique for displaying ER model using Unified Modelling Language (UML). How to identify and resolve problems with ER models called connection traps. How to build an ER model from a requirements specification.

Entity-Relationship Model ER modeling is a top-down approach to database design. Unified Modeling Language

ER Diagram of Branch View of DreamHome

Concepts of the ER Model Entity types Relationship types Attributes

Entity Type Entity type –Group of objects with same properties, identified by enterprise as having an independent existence. Entity occurrence –Uniquely identifiable object of an entity type.

Entity Type & Entity Occurrence EmployeeCompany

Examples of Entity Types

ER Diagram of Staff and Branch Entity Types

Entities (EX) A college is divided into several schools. Each school is administered by a dean. A dean is a professor Each school is composed of several departments. Each department offers several courses. A course can have many sections Each professor may teach up to four classes, each one a section of a course. A professor may also be on a research contract and teach no classes at all.

Relationship Types Relationship type –Set of meaningful associations among entity types. Relationship occurrence –Uniquely identifiable association, which includes one occurrence from each participating entity type.

Semantic Net of Has Relationship Type Branch has staff

ER Diagram of Branch Has Staff Relationship

Relationship Types Degree of a Relationship –Number of participating entities in relationship. Relationship of degree: –two is binary; –three is ternary; –four is quaternary.

Binary Relationship called POwns

Ternary Relationship called Registers

Question Can three binary relationships substitute a ternary relationship? (In general)

Quaternary Relationship called Arranges

Relationship Types Recursive Relationship –Relationship type where same entity type participates more than once in different roles. Relationships may be given role names to indicate purpose that each participating entity type plays in a relationship.

Recursive Relationship called Supervises with Role Names

Entities associated through two distinct Relationships with Role Names

Attributes Attribute –Property of an entity or a relationship type. Attribute Domain –Set of allowable values for one or more attributes.

Attributes Simple Attribute –Attribute composed of a single component with an independent existence. Composite Attribute –Attribute composed of multiple components, each with an independent existence.

Attributes Single-valued Attribute –Attribute that holds a single value for each occurrence of an entity type. Multi-valued Attribute –Attribute that holds multiple values for each occurrence of an entity type.

Attributes Derived Attribute –Attribute that represents a value that is derivable from value of a related attribute, or set of attributes, not necessarily in the same entity type.

car 1 ((ABC 123, TEXAS), TK629, Ford Mustang, convertible, 1999, (red, black)) car 2 ((ABC 123, NEW YORK), WP9872, Nissan 300ZX, 2-door, 2002, (blue)) car 3 ((VSY 720, TEXAS), TD729, Buick LeSabre, 4-door, 2003, (white, blue)). CAR Registration(RegistrationNumber, State), VehicleID, Make, Model, Year, (Color)

Keys Candidate Key –Minimal set of attributes that uniquely identifies each occurrence of an entity type. Primary Key –Candidate key selected to uniquely identify each occurrence of an entity type. Composite Key –A candidate key that consists of two or more attributes.

Primary Key (EX) staffNo, name, position salary, totalStaff branchNo, address {street, city, zip code, telephone number[1..3]} Patient number, patient name, drug number, drug name, description, dosage, method of admin, units per day, start date, finish date.

ER Diagram of Staff and Branch Entities and their Attributes

Entity Type Strong Entity Type –Entity type that is not existence-dependent on some other entity type. Weak Entity Type –Entity type that is existence-dependent on some other entity type.

Strong Entity Type called Client and Weak Entity Type called Preference

Relationship called Advertises with Attributes NPDC N1P1110 N1P2110 N2P1120