Carnegie Mellon Univ. Dept. of Computer Science /615 - DB Applications. Problem. Faloutsos - Pavlo CMU SCS /615
|
|
- Isaac Watkins
- 5 years ago
- Views:
Transcription
1 Faloutsos - Pavlo /615 Carnegie ellon Univ. Dept. of Computer Science /615 - DB Applications C. Faloutsos - A. Pavlo Lecture#2: E-R diagrams Problem Develop an application for U.G. admin: Student info Who-takes-what class Class rosters Transcripts How do you proceed? (Which role(s) are you playing?) Faloutsos - Pavlo /615 2 Database Design Requirements Analysis Conceptual Design Logical Design Schema Refinement Physical Design Security Design Faloutsos - Pavlo /
2 Faloutsos - Pavlo /615 Database Design Requirements Analysis Conceptual Design Logical Design Schema Refinement Physical Design Security Design user s needs high level (ER) Tables ormalization Indices etc Access controls Faloutsos - Pavlo /615 4 aintain Problem Develop an application for U.G. admin: Student info Who-takes-what class Class rosters Transcripts If you are the *new* DBA, what would you rather inherit: Faloutsos - Pavlo /615 5 This or this? drop table if exists student; create table student (ssn fixed, name char(20)); drop table if exists takes; create table takes (ssn fixed, cid char(10), grade fixed); Student Takes Course Faloutsos - Pavlo /
3 Faloutsos - Pavlo /615 True story Health insurance company Wants to catch (some of the abundant) fraud Schema: patients, visit doctors, get medicine, Doctors perform operations, urses monitor patients, etc etc Q: How many tables do you think it spans? Faloutsos - Pavlo /615 7 True story Schema: patients, visit doctors, get medicine, Doctors perform operations, urses monitor patients, etc etc Q: How many tables do you think it spans? 10? 20? 30? Faloutsos - Pavlo /615 8 True story Schema: patients, visit doctors, get medicine, Doctors perform operations, urses monitor patients, etc etc Q: How many tables do you think it spans? 10? 20? 30? A: 120 PAGES of schema Faloutsos - Pavlo /
4 Faloutsos - Pavlo /615 otivation & upcoming conclusion: E-R diagrams are excellent documentation tools Student Takes Course Faloutsos - Pavlo / concepts Entities Overview Relationships Attributes Specialization/Generalization Aggregation ER modeling questions Faloutsos - Pavlo / Tools Entities ( entity sets ) Student Takes Course Relationships ( rel. sets ) P and mapping constraints attributes Faloutsos - Pavlo /
5 Faloutsos - Pavlo /615 Example Students, taking courses, offered by instructors; a course may have multiple sections; one instructor per section nouns -> entity sets verbs -> relationship sets Faloutsos - Pavlo / Example Students, taking courses, offered by instructors; a course may have multiple sections; one instructor per section nouns -> entity sets verbs -> relationship sets Faloutsos - Pavlo / Example Students, taking courses, offered by instructors; a course may have multiple sections; one instructor per section nouns -> entity sets verbs -> relationship sets Faloutsos - Pavlo /
6 Faloutsos - Pavlo /615 name... STUDET ssn ISTRUCTOR issn primary key = unique identifier -> underline Faloutsos - Pavlo / name ssn STUDET c-id c-name COURSE issn ISTRUCTOR but: sections of course (with different instructors)? Faloutsos - Pavlo / ssn STUDET c-id s-id SECTIO COURSE issn ISTRUCTOR but: s-id is not unique... (see later) Faloutsos - Pavlo /
7 Faloutsos - Pavlo /615 ssn STUDET c-id s-id SECTIO COURSE issn ISTRUCTOR Q: how to record that students take courses? Faloutsos - Pavlo / ssn s-id STUDET takes SECTIO c-id COURSE issn ISTRUCTOR Faloutsos - Pavlo / STUDET takes s-id SECTIO teaches 1 ISTRUCTOR c-id COURSE Faloutsos - Pavlo /
8 Faloutsos - Pavlo /615 STUDET takes s-id SECTIO teaches 1 ISTRUCTOR 1 has c-id COURSE Faloutsos - Pavlo / to 1 (example?) 1 to to Cardinalities Faloutsos - Pavlo / Cardinalities 1 1 COUTRY has CAPITAL PERSO 1 owns CAR STUDET takes SECTIO Faloutsos - Pavlo /
9 Faloutsos - Pavlo /615 Cardinalities COUTRY has CAPITAL Book s notation: PERSO owns CAR STUDET takes SECTIO Faloutsos - Pavlo / Book s notation vs 1 to notation Cardinalities 1 1 COUTRY has 1 PERSO owns CAPITAL CAR STUDET takes SECTIO Faloutsos - Pavlo / Cardinalities 1 1 COUTRY has CAPITAL PERSO 1 owns CAR STUDET takes SECTIO Faloutsos - Pavlo /
10 Faloutsos - Pavlo /615 Total/partial participation 1:1 1:1 total, total COUTRY has CAPITAL?? PERSO?:1?: owns CAR?? STUDET?: takes?: SECTIO Faloutsos - Pavlo / Total/partial participation 1:1 1:1 total, total COUTRY has CAPITAL partial, total PERSO 1:1 0: owns CAR?? STUDET?: takes?: SECTIO Faloutsos - Pavlo / Total/partial participation 1:1 1:1 total, total COUTRY has CAPITAL partial, total PERSO 1:1 0: owns CAR partial, total STUDET 1: 0: takes SECTIO Faloutsos - Pavlo /
11 Faloutsos - Pavlo /615 Total/partial participation Is it legal? partial, total PERSO 1:1 0: owns CAR Faloutsos - Pavlo / Total/partial participation Is it legal? O! why not? partial, total PERSO 1:1 0: owns CAR Faloutsos - Pavlo / Subtle concept: Weak entities section has no unique-id of its own!(?) c-id s-id SECTIO 1 has COURSE Faloutsos - Pavlo /
12 Faloutsos - Pavlo /615 Weak entities weak entities: if they need to borrow a unique id from a strong entity - thick box. c-id + s-id : unique id for SECTIO partial key (eg., s-id ) - dashed-underline identifying relationship (eg., has ) c-id s-id SECTIO 1 has COURSE Faloutsos - Pavlo / Weak entities Other example(s) of weak entities???id 1?????????? Faloutsos - Pavlo / Weak entities Other example(s) of weak entities? e-id name Dependent 1 has Employee Faloutsos - Pavlo /
13 Faloutsos - Pavlo /615 ore details self-relationships - example????????? Faloutsos - Pavlo / ore details self-relationships - example? 1 manages EPLOYEE Faloutsos - Pavlo / ore details self-relationships - example??? Has-friend FB user?? Faloutsos - Pavlo /
14 Faloutsos - Pavlo /615 ore details 3-way and k-way relationships? Faloutsos - Pavlo / ore details 3-way and k-way relationships? Rare, but possible: EPLOYEE uses TOOL PROJECT P Faloutsos - Pavlo / ore details 3-way and k-way relationships? Rare, but possible: user reviews keyword App-store/amazon reviews app P Faloutsos - Pavlo /
15 Faloutsos - Pavlo /615 concepts Entities Overview Relationships Attributes Specialization/Generalization Aggregation ER modeling questions Faloutsos - Pavlo / ore details - attributes key (or primary key): unique identifier underlined, in the ER diagram [not in textbook - FYI: multivalued or set-valued attributes (eg., dependents for EPLOYEE) derived attributes (eg., 15% tip) ] Faloutsos - Pavlo / Overview concepts Entities Relationships Attributes Specialization/Generalization Aggregation ER modeling questions Basic Advanced/ rare Faloutsos - Pavlo /
16 Faloutsos - Pavlo /615 Specialization eg., students: part time (#credithours) and full time (major) ssn name STUDET IS-A major FT-STUDET PT-STUDET #credits Faloutsos - Pavlo / Observations Generalization: exact reverse of specialization attribute inheritance could have many levels of an IS-A hierarchy Faloutsos - Pavlo / ore details Overlap constraints A Covering constraints B C Faloutsos - Pavlo /
17 Faloutsos - Pavlo /615 ore details Overlap constraints can an entity belong to both B and C? Covering constraints can an A entity belong to neither B nor C? B A C Faloutsos - Pavlo / ore details Overlap constraints - examples? A o overlap with overlap A A B C B C B C Faloutsos - Pavlo / ore details Covering constraints - examples? Total coverage A C B B A C Partial coverage A B C Faloutsos - Pavlo /
18 Faloutsos - Pavlo /615 concepts Entities Overview Relationships Attributes Specialization/Generalization Aggregation ER modeling questions Faloutsos - Pavlo / Aggregation computer model (w/ CPU and HD) and aker (eg., Dell, HP) CPU HD? AKER Faloutsos - Pavlo / Aggregation treat a relationship as an entity used to express a relationship among relationships CPU HD AKER Faloutsos - Pavlo /
19 Faloutsos - Pavlo /615 concepts Entities Overview Relationships Attributes Specialization/Generalization Aggregation ER modeling questions Faloutsos - Pavlo / Conceptual design Entity vs attribute Entity vs relationship Binary or ternary relationships? Aggregation? Faloutsos - Pavlo / Entity vs. attribute Entity EPLOYEE (w/ emp#, name, job_code,...) Q: How about spouse - entity or attribute? Q: How about dependents? Faloutsos - Pavlo /
20 Faloutsos - Pavlo /615 Entity vs. attribute Entity EPLOYEE (w/ emp#, name, job_code,...) Q: How about spouse - entity or attribute? A: probably, attribute is enough Q: How about dependents? A: Entity - we may have many dependents Faloutsos - Pavlo / Entity vs. Relationship STUDET takes SECTIO OR STUDET 1 TAKES 1 SECTIO Faloutsos - Pavlo / Binary vs Ternary Relationships usually, binary relationships are cleaner : Faloutsos - Pavlo /
21 Faloutsos - Pavlo /615 Binary vs. Ternary Relationships name ssn lot pname age If each policy is owned by just 1 employee: Employees Covers Policies policyid cost Dependents Faloutsos - Pavlo / Binary vs. Ternary Relationships name ssn lot pname age If each policy is owned by just 1 employee: Employees Covers Policies policyid cost Bad design Dependents Faloutsos - Pavlo / Binary vs. Ternary Relationships name ssn lot pname age If each policy is owned by just 1 employee: Key constraint on Policies would mean policy can only cover 1 dependent! Employees Covers Policies policyid cost Bad design Dependents Faloutsos - Pavlo /
22 Faloutsos - Pavlo /615 Binary vs. Ternary Relationships If each policy is owned by just 1 employee: Key constraint on Policies would mean policy can only cover 1 dependent! What are the additional constraints in the 2nd diagram? ssn ssn name Employees Bad design name Employees lot policyid Purchaser Better design Policies cost pname pname Beneficiary Policies Faloutsos - Pavlo / policyid cost lot Covers age Dependents age Dependents Binary vs Ternary Rel. But sometimes ternary rel. can not be replaced by a set of binary rel s: Faloutsos - Pavlo / Binary vs. Ternary Relationships (Contd.) qty Parts Contract Departments Suppliers Parts VS. Departments can-supply Suppliers deals-with why is it bad? Faloutsos - Pavlo /
23 Faloutsos - Pavlo /615 Binary vs. Ternary Relationships (Contd.) qty Parts Contract Departments Suppliers VS. Parts Departments can-supply Suppliers deals-with S can-supply P, D needs P, and D deals-with S does not imply that D has agreed to buy P from S. How do we record qty? Faloutsos - Pavlo / Binary vs. Ternary Relationships (Contd.) qty Parts Contract Departments ot in textbook: in practice, often: Suppliers qty Parts Contract Departments Suppliers Faloutsos - Pavlo / Binary vs. Ternary Relationships (Contd.) ot in textbook: in practice, often: qty c-id Parts Contract Departments Suppliers Faloutsos - Pavlo /
24 Faloutsos - Pavlo /615 Binary vs. Ternary Relationships (Contd.) ot in textbook: in practice, often: qty c-id Parts Contract 1 1 Suppliers Departments Faloutsos - Pavlo / Ternary vs. aggregation use aggregation, if we want to attach a relationship to a relationship (see book for example) (in practice, again we create a unique-id and resort to binary relationships) Faloutsos - Pavlo / Ternary vs. aggregation How would you handle this case? CPU HD AKER Faloutsos - Pavlo /
25 Faloutsos - Pavlo /615 Ternary vs. aggregation How would you handle this case? COP. ODEL CPU HD AKER Faloutsos - Pavlo / Ternary vs. aggregation How would you handle this case? COP. ODEL???? CPU HD AKER Faloutsos - Pavlo / Ternary vs. aggregation How would you handle this case? HAS_CPU CPU COP. ODEL HD AKER Faloutsos - Pavlo /
26 Faloutsos - Pavlo /615 Summary E-R Diagrams: a powerful, user-friendly tool for data modeling: Entities (strong, weak) Attributes (primary keys, discriminators, derived, multivalued) Relationships (1:1, 1:, :; multi-way) Generalization/Specialization; Aggregation Faloutsos - Pavlo / POPULAR Summary E-R Diagrams: a powerful, user-friendly tool for data modeling: Entities (strong, weak) Attributes (primary keys, discriminators, derived, multivalued) Relationships (1:1, 1:, :; multi-way) Generalization/Specialization; Aggregation Faloutsos - Pavlo / Summary - cont d (strong) entity set attribute weak entity set A primary key relationship set A partial key identifying rel. set for weak entity Faloutsos - Pavlo /
27 Faloutsos - Pavlo /615 Summary - cont d cardinalities cardinalities partial/total l:h l :h cardinalities with limits (not in textbook - FYI) Faloutsos - Pavlo / Summary - cont d IS-A aggregation Faloutsos - Pavlo /
Problem. Carnegie Mellon Univ. Dept. of Computer Science /615 - DB Applications
Carnegie ellon Univ. Dept. of Computer Science 15-415/615 - DB Applications C. Faloutsos - A. Pavlo Lecture#2: E-R diagrams Problem Develop an application for U.G. admin: Student info Who--what class Class
More informationAdministrivia. Carnegie Mellon Univ. Dept. of Computer Science /615 - DB Applications. Course Topics. Problem
Faloutsos - Pavlo 15-415/615 Carnegie ellon Univ. Dept. of Computer Science 15-415/615 - DB Applications C. Faloutsos - A. Pavlo Lecture#2: E-R diagrams Administrivia Course url: http://15415.courses.cs.cmu.edu/
More informationDatabase Applications (15-415)
Database Applications (15-415) The Entity Relationship Model Lecture 2, January 15, 2014 Mohammad Hammoud Today Last Session: Course overview and a brief introduction on databases and database systems
More informationMIS Database Systems Entity-Relationship Model.
MIS 335 - Database Systems Entity-Relationship Model http://www.mis.boun.edu.tr/durahim/ Ahmet Onur Durahim Learning Objectives Database Design Main concepts in the ER model? ER Diagrams Database Design
More informationThe Entity-Relationship (ER) Model 2
The Entity-Relationship (ER) Model 2 Week 2 Professor Jessica Lin Keys Differences between entities must be expressed in terms of attributes. A superkey is a set of one or more attributes which, taken
More informationThe Entity-Relationship Model. Overview of Database Design
The Entity-Relationship Model Chapter 2, Chapter 3 (3.5 only) Database Management Systems 3ed, R. Ramakrishnan and J. Gehrke 1 Overview of Database Design Conceptual design: (ER Model is used at this stage.)
More informationIntroduction to Data Management. Lecture #3 (Conceptual DB Design) Instructor: Chen Li
Introduction to Data Management Lecture #3 (Conceptual DB Design) Instructor: Chen Li 1 Announcements v HW #1 is now available v Today s plan Conceptual DB design, cont. Advanced ER concepts 2 Weak Entities
More informationCIS 330: Web-driven Web Applications. Lecture 2: Introduction to ER Modeling
CIS 330: Web-driven Web Applications Lecture 2: Introduction to ER Modeling 1 Goals of This Lecture Understand ER modeling 2 Last Lecture Why Store Data in a DBMS? Transactions (concurrent data access,
More informationDatabase Systems. Lecture2:E-R model. Juan Huo( 霍娟 )
Database Systems Lecture2:E-R model Juan Huo( 霍娟 ) Reference slides: http://www.cs.wisc.edu/ dbbook Berkeley, Professor Eben Haber,Professor Mary Roth Review: Benefits of a DBMS 1. Data independence applications
More informationModeling Your Data. Chapter 2. cs542 1
Modeling Your Data Chapter 2 cs542 1 Part II Discussion of the Model: Good Design/ Bad Design cs542 2 Design : The Obvious Use meaningful and descriptive s (it s for the human after all) Keep as simple
More informationDatabases Model the Real World. The Entity- Relationship Model. Conceptual Design. Steps in Database Design. ER Model Basics. ER Model Basics (Contd.
The Entity- Relationship Model R &G - Chapter 2 A relationship, I think, is like a shark, you know? It has to constantly move forward or it dies. And I think what we got on our hands is a dead shark. Woody
More informationDatabase Management Systems. Chapter 2 Part 2
Database Management Systems Chapter 2 Part 2 Introduction to Database Design Database Management Systems 3ed, R. Ramakrishnan and J. Gehrke 1 Class Hierarchies Classify entities sets into Super-class and
More informationIntroduction to Database Design. Dr. Kanda Runapongsa Dept of Computer Engineering Khon Kaen University
Introduction to Database Design Dr. Kanda Runapongsa (krunapon@kku.ac.th) Dept of Computer Engineering Khon Kaen University Overview What are the steps in designing a database? Why is the ER model used
More informationThe Entity-Relationship Model. Overview of Database Design. ER Model Basics. (Ramakrishnan&Gehrke, Chapter 2)
The Entity-Relationship Model (Ramakrishnan&Gehrke, Chapter 2) CS 432 Fall 2007 1 Overview of Database Design Conceptual design: (ER Model is used at this stage.) What are the entities and relationships
More informationCS 4604: Introduction to Database Management Systems. B. Aditya Prakash Lecture #5: Entity/Relational Models---Part 1
CS 4604: Introduction to Database Management Systems B. Aditya Prakash Lecture #5: Entity/Relational Models---Part 1 E/R: NOT IN BOOK! IMPORTANT: Follow only lecture slides for this topic! Differences
More informationIntroduction to Database Design
ICS 321 Fall 2009 Introduction to Database Design Asst. Prof. Lipyeow Lim Information & Computer Science Department University of Hawaii at Manoa 09/03/2009 Lipyeow Lim -- University of Hawaii at Manoa
More informationThe Entity-Relationship Model
The Entity-Relationship Model Chapter 2 Database Management Systems 3ed, R. Ramakrishnan and J. Gehrke 1 Overview of Database Design Conceptual design: (ER Model is used at this stage.) What are the entities
More informationThe Entity-Relationship Model
The Entity-Relationship Model Chapter 2 Database Management Systems, R. Ramakrishnan and J. Gehrke 1 Overview of Database Design Conceptual design: (ER Model is used at this stage.) What are the entities
More informationThe Entity-Relationship (ER) Model
The Entity-Relationship (ER) Model (Study Cow book Chapter 2) Comp 521 Files and Databases Fall 2012 1 Overview of Database Design Conceptual design: (ER Model is used at this stage.) What are the entities
More informationDatabases Model the Real World. The Entity- Relationship Model. Conceptual Design. Steps in Database Design. ER Model Basics. ER Model Basics (Contd.
The Entity- Relationship Model CS 186 Fall 2002: Lecture 2 R &G - Chapter 2 A relationship, I think, is like a shark, you know? It has to constantly move forward or it dies. And I think what we got on
More informationCONCEPTUAL DESIGN: ER TO RELATIONAL TO SQL
RELATIONAL MODEL TO Data Model CONCEPTUAL DESIGN: ER TO RELATIONAL TO How to represent Entity sets, Relationship sets, Attributes, Key and participation constraints, Subclasses, Weak entity sets...? 2
More informationCS/INFO 330 Entity-Relationship Modeling. Announcements. Goals of This Lecture. Mirek Riedewald
CS/INFO 330 Entity-Relationship Modeling Mirek Riedewald mirek@cs.cornell.edu Announcements Office hour update (see class homepage) First homework assignment will be available from CMS later today Some
More informationThe Relational Model (ii)
ICS 321 Fall 2009 The Relational Model (ii) Asst. Prof. Lipyeow Lim Information and Computer Science Department University of Hawaii at Manoa 1 Internet Book Store Example Isbn title author qty price year
More informationThe Relational Model. Roadmap. Relational Database: Definitions. Why Study the Relational Model? Relational database: a set of relations
The Relational Model CMU SCS 15-415/615 C. Faloutsos A. Pavlo Lecture #3 R & G, Chap. 3 Roadmap Introduction Integrity constraints (IC) Enforcing IC Querying Relational Data ER to tables Intro to Views
More informationContents. Database. Information Policy. C03. Entity Relationship Model WKU-IP-C03 Database / Entity Relationship Model
Information Policy Database C03. Entity Relationship Model Code: 164323-03 Course: Information Policy Period: Spring 2013 Professor: Sync Sangwon Lee, Ph. D 1 Contents 01. Overview of Database Design 02.
More informationIntroduction to Database Design
Introduction to Database Design UVic C SC 370 Daniel M German Introduction to Database Design (1.2.0) CSC 370 4/5/2005 14:52 p.1/33 Overview What are the steps in designing a database? What is the entity-relationship
More informationIntroduction to Database Design
Introduction to Database Design UVic C SC 370, Fall 2002 Daniel M. German Department of Computer Science University of Victoria 2 1 Introduction to Database Design CSC 370 dmgerman@uvic.ca Overview What
More informationDatabase Applications (15-415)
Database Applications (15-415) The Relational Model Lecture 3, January 18, 2015 Mohammad Hammoud Today Last Session: The entity relationship (ER) model Today s Session: ER model (Cont d): conceptual design
More informationRepresent entities and relations with diagrams
LEARNING OBJECTIVES Define data modeling terms Describe E-R Model Identify entities and relations Represent entities and relations with diagrams WHAT IS DATA MODELING? A data model is a collection of concepts
More informationIntroduction to Data Management. Lecture #3 (Conceptual DB Design)
Introduction to Data Management Lecture #3 (Conceptual DB Design) Instructor: Mike Carey mjcarey@ics.uci.edu Database Management Systems 3ed, R. Ramakrishnan and J. Gehrke 1 Announcements Today s plan:
More informationIntroduction to Data Management. Lecture #3 (Conceptual DB Design)
Introduction to Data Management Lecture #3 (Conceptual DB Design) Instructor: Mike Carey mjcarey@ics.uci.edu Database Management Systems 3ed, R. Ramakrishnan and J. Gehrke 1 Announcements Reminders: Sign
More informationThe Relational Model. Chapter 3
The Relational Model Chapter 3 Why Study the Relational Model? Most widely used model. Systems: IBM DB2, Informix, Microsoft (Access and SQL Server), Oracle, Sybase, MySQL, etc. Legacy systems in older
More informationOVERVIEW OF DATABASE DEVELOPMENT
DATABASE SYSTEMS I WEEK 2: THE ENTITY-RELATIONSHIP MODEL OVERVIEW OF DATABASE DEVELOPMENT Requirements Analysis / Ideas High-Level Database Design Conceptual Database Design / Relational Database Schema
More informationRelational Databases BORROWED WITH MINOR ADAPTATION FROM PROF. CHRISTOS FALOUTSOS, CMU /615
Relational Databases BORROWED WITH MINOR ADAPTATION FROM PROF. CHRISTOS FALOUTSOS, CMU 15-415/615 Roadmap 3 Introduction Integrity constraints (IC) Enforcing IC Querying Relational Data ER to tables Intro
More informationCIS 330: Applied Database Systems. ER to Relational Relational Algebra
CIS 330: Applied Database Systems ER to Relational Relational Algebra 1 Logical DB Design: ER to Relational Entity sets to tables: ssn name Employees lot CREATE TABLE Employees (ssn CHAR(11), name CHAR(20),
More informationThe Relational Model. Chapter 3. Database Management Systems, R. Ramakrishnan and J. Gehrke 1
The Relational Model Chapter 3 Database Management Systems, R. Ramakrishnan and J. Gehrke 1 Why Study the Relational Model? Most widely used model. Vendors: IBM, Informix, Microsoft, Oracle, Sybase, etc.
More informationThe Relational Model. Outline. Why Study the Relational Model? Faloutsos SCS object-relational model
The Relational Model CMU SCS 15-415 C. Faloutsos Lecture #3 R & G, Chap. 3 Outline Introduction Integrity constraints (IC) Enforcing IC Querying Relational Data ER to tables Intro to Views Destroying/altering
More informationEntity-Relationship Model. From Chapter 5, Kroenke book
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:
More information1/24/2012. Chapter 7 Outline. Chapter 7 Outline (cont d.) CS 440: Database Management Systems
CS 440: Database Management Systems Chapter 7 Outline Using High-Level Conceptual Data Models for Database Design A Sample Database Application Entity Types, Entity Sets, Attributes, and Keys Relationship
More informationIntroduction to Data Management. Lecture #5 (E-R Relational, Cont.)
Introduction to Data Management Lecture #5 (E-R Relational, Cont.) Instructor: Mike Carey mjcarey@ics.uci.edu Database Management Systems 3ed, R. Ramakrishnan and J. Gehrke 1 Announcements v HW#1 is due
More informationData Modeling. Yanlei Diao UMass Amherst. Slides Courtesy of R. Ramakrishnan and J. Gehrke
Data Modeling Yanlei Diao UMass Amherst Slides Courtesy of R. Ramakrishnan and J. Gehrke 1 Outline v Conceptual Design: ER Model v Relational Model v Logical Design: from ER to Relational 2 Conceptual
More informationDatabase Design. ER Model. Overview. Introduction to Database Design. UVic C SC 370. Database design can be divided in six major steps:
Database Design Database design can be divided in six major steps: Requirements analysis Conceptual Database design (mostly done using the ER model) Logical Database design Schema refinement Physical Database
More informationThe Relational Model 2. Week 3
The Relational Model 2 Week 3 1 We have seen how to create a database schema, how do we create an actual database on our computers? professor(pid : string, name : string) course(pid : string, number :
More informationHigh Level Database Models
ICS 321 Fall 2011 High Level Database Models Asst. Prof. Lipyeow Lim Information & Computer Science Department University of Hawaii at Manoa 9/21/2011 Lipyeow Lim -- University of Hawaii at Manoa 1 Database
More informationThe Relational Model. Chapter 3. Comp 521 Files and Databases Fall
The Relational Model Chapter 3 Comp 521 Files and Databases Fall 2012 1 Why Study the Relational Model? Most widely used model by industry. IBM, Informix, Microsoft, Oracle, Sybase, etc. It is simple,
More informationDatabase Management Systems. Chapter 3 Part 2
Database Management Systems Chapter 3 Part 2 The Relational Model Database Management Systems 3ed, R. Ramakrishnan and J. Gehrke 1 Logical DB Design: ER to Relational Entity sets to tables: CREATE TABLE
More informationSYLLABUS ADMIN DATABASE SYSTEMS I WEEK 2 THE ENTITY-RELATIONSHIP MODEL. Assignment #2 changed. A2Q1 moved to A3Q1
DATABASE SYSTEMS I WEEK 2 THE ENTITY-RELATIONSHIP MODEL Class Time and Location: Tue 14:30-16:20 AQ3005 Thu 14:30-15:20 AQ3003 Course Website: http://www.cs.sfu.ca/cc/354/rfrank/ Instructor: Richard Frank,
More informationUsing High-Level Conceptual Data Models for Database Design A Sample Database Application Entity Types, Entity Sets, Attributes, and Keys
Chapter 7: Data Modeling Using the Entity- Relationship (ER) Model Using High-Level Conceptual Data Models for Database Design A Sample Database Application Entity Types, Entity Sets, Attributes, and Keys
More informationOverview. Introduction to Database Design. ER Model. Database Design
Introduction to Database Design UVic C SC 370 Dr. Daniel M. German Department of Computer Science Overview What are the steps in designing a database? What is the entity-relationship (ER) model? How does
More informationDatabase Applications (15-415)
Database Applications (15-415) The Entity Relationship Model Lecture 2, January 12, 2016 Mohammad Hammoud Today Last Session: Course overview and a brief introduction on databases and database systems
More informationDatabase Design Process
Database Design Process Real World Functional Requirements Requirements Analysis Database Requirements Functional Analysis Access Specifications Application Pgm Design E-R Modeling Choice of a DBMS Data
More informationChapter 2: Entity-Relationship Model
Chapter 2: Entity-Relationship Model! Entity Sets! Relationship Sets! Design Issues! Mapping Constraints! Keys! E-R Diagram! Extended E-R Features! Design of an E-R Database Schema! Reduction of an E-R
More informationIntro to DB CHAPTER 6
Intro to DB CHAPTER 6 DATABASE DESIGN &THEER E-R MODEL Chapter 6. Entity Relationship Model Design Process Modeling Constraints E-R Diagram Design Issues Weak Entity Sets Extended E-R Features Design of
More informationCOMP Instructor: Dimitris Papadias WWW page:
COMP 5311 Instructor: Dimitris Papadias WWW page: http://www.cse.ust.hk/~dimitris/5311/5311.html Textbook Database System Concepts, A. Silberschatz, H. Korth, and S. Sudarshan. Reference Database Management
More informationVARDHAMAN COLLEGE OF ENGINEERING Shamshabad , Hyderabad B.Tech. CSE IV Semester (VCE - R11) T P C 3+1* -- 4 (A1511) DATABASE MANAGEMENT SYSTEMS
1 VARDHAMAN COLLEGE OF ENGINEERING Shamshabad 501 218, Hyderabad B.Tech. CSE IV Semester (VCE - R11) T P C 3+1* -- 4 (A1511) DATABASE MANAGEMENT SYSTEMS UNIT - I INTRODUCTION: History of database systems,
More informationTranslation of ER-diagram into Relational Schema. Dr. Sunnie S. Chung CIS430/530
Translation of ER-diagram into Relational Schema Dr. Sunnie S. Chung CIS430/530 Learning Objectives Define each of the following database terms Relation Primary key Foreign key Referential integrity Field
More informationEntity-Relationship Model
Entity-Relationship Model Data Models High-level or conceptual data models provide concepts that are close to the way many users perceive data, whereas low-level or physical data models provide concepts
More informationTHE ENTITY- RELATIONSHIP (ER) MODEL CHAPTER 7 (6/E) CHAPTER 3 (5/E)
THE ENTITY- RELATIONSHIP (ER) MODEL CHAPTER 7 (6/E) CHAPTER 3 (5/E) 2 CHAPTER 7 OUTLINE Using High-Level, Conceptual Data Models for Database Design Entity-Relationship (ER) model Popular high-level conceptual
More informationEntity Relationship Data Model. Slides by: Shree Jaswal
Entity Relationship Data Model Slides by: Shree Jaswal Topics: Conceptual Modeling of a database, The Entity-Relationship (ER) Model, Entity Types, Entity Sets, Attributes, and Keys, Relationship Types,
More informationHigh-Level Database Models (ii)
ICS 321 Spring 2011 High-Level Database Models (ii) Asst. Prof. Lipyeow Lim Information & Computer Science Department University of Hawaii at Manoa 1 Logical DB Design: ER to Relational Entity sets to
More informationThe Entity-Relationship Model. Steps in Database Design
The Entity-Relationship Model Steps in Database Design 1) Requirement Analysis Identify the data that needs to be stored data requirements Identify the operations that need to be executed on the data functional
More informationCS 146 Database Systems
DBMS CS 146 Database Systems Entity-Relationship (ER) Model CS 146 1 CS 146 2 A little history Progression of Database Systems In DBMS: single instance of data maintained and accessed by different users
More informationOverview of db design Requirement analysis Data to be stored Applications to be built Operations (most frequent) subject to performance requirement
ITCS 3160 Data Base Design and Implementation Jing Yang 2010 Fall Class 12: Data Modeling Using the Entity-Relationship (ER) Model Overview of db design Requirement analysis Data to be stored Applications
More informationEntity-Relationship Modelling. Entities Attributes Relationships Mapping Cardinality Keys Reduction of an E-R Diagram to Tables
Entity-Relationship Modelling Entities Attributes Relationships Mapping Cardinality Keys Reduction of an E-R Diagram to Tables 1 Entity Sets A enterprise can be modeled as a collection of: entities, and
More informationLecture3: Data Modeling Using the Entity-Relationship Model.
College of Computer and Information Sciences - Information Systems Dept. Lecture3: Data Modeling Using the Entity-Relationship Model. Ref. Chapter12 Prepared by L. Nouf Almujally & Aisha AlArfaj Rev. by
More informationCIS 330: Applied Database Systems
1 CIS 330: Applied Database Systems Lecture 3: Introduction to ER Modeling The Relational Model Johannes Gehrke johannes@cs.cornell.edu http://www.cs.cornell.edu/johannes Announcements How many laptops
More informationConceptual Design. The Entity-Relationship (ER) Model
Conceptual Design. The Entity-Relationship (ER) Model CS430/630 Lecture 12 Slides based on Database Management Systems 3 rd ed, Ramakrishnan and Gehrke Relationship Set Representation ssn name lot since
More informationThe Relational Model. Chapter 3. Comp 521 Files and Databases Fall
The Relational Model Chapter 3 Comp 521 Files and Databases Fall 2014 1 Why the Relational Model? Most widely used model by industry. IBM, Informix, Microsoft, Oracle, Sybase, MySQL, Postgres, Sqlite,
More informationChapter 7: Entity-Relationship Model
Chapter 7: Entity-Relationship Model, 7th Ed. See www.db-book.com for conditions on re-use Chapter 7: Entity-Relationship Model Design Process Modeling Constraints E-R Diagram Design Issues Weak Entity
More informationEntity-Relationship Diagrams
Entity-Relationship Diagrams Fall 2017, Lecture 3 There is nothing worse than a sharp image of a fuzzy concept. Ansel Adams 1 Recall: Relational Database Management Relational DataBase Management Systems
More informationER Model Overview. The Entity-Relationship Model. Database Design Process. ER Model Basics
ER Model Overview The Entity-Relationship Model Davood Rafiei Developed by Peter Chen in the mid 70 s Used for the design of conceptual schema. The world is described in terms of entities relationships
More informationIntroduction to Data Management. Lecture #4 E-R Model, Still Going
Introduction to Data Management Lecture #4 E-R Model, Still Going Instructor: Mike Carey mjcarey@ics.uci.edu Database Management Systems 3ed, R. Ramakrishnan and J. Gehrke Today s Reminders Continue to
More informationChapter 2: Entity-Relationship Model. Entity Sets. Entity Sets customer and loan. Attributes. Relationship Sets. A database can be modeled as:
Chapter 2: Entity-Relationship Model Entity Sets Entity Sets Relationship Sets Design Issues Mapping Constraints Keys E-R Diagram Extended E-R Features Design of an E-R Database Schema Reduction of an
More informationChapter 6: Entity-Relationship Model. E-R Diagrams
Chapter 6: Entity-Relationship Model A database can be modeled as: a collection of entities, relationship among entities. An entity is an object that exists and is distinguishable from other objects. Example:
More informationCOMP 244. ER-Diagram Notations. Entity-Relationship Diagrams DATABASE CONCEPTS & APPLICATIONS. Database Concepts & Applications 1.
COMP 244 DATABASE CONCEPTS & APPLICATIONS ER-Diagram Notations Attribute Key Attribute Multi-valued attributes Entity-Relationship Diagrams Derived Attribute Weak Entity Identifying Relationship 1 2 Database
More informationConceptual Database Design. COSC 304 Introduction to Database Systems. Entity-Relationship Modeling. Entity-Relationship Modeling
COSC 304 Introduction to Database Systems Entity-Relationship Modeling Dr. Ramon Lawrence University of British Columbia Okanagan ramon.lawrence@ubc.ca Conceptual Database Design Conceptual database design
More informationAdvance Database Management System
Advance Database Management System Conceptual Design Lecture- A simplified database design process Database Requirements UoD Requirements Collection and Analysis Functional Requirements A simplified database
More informationDatabase Design CENG 351
Database Design Database Design Process Requirements analysis What data, what applica;ons, what most frequent opera;ons, Conceptual database design High level descrip;on of the data and the constraint
More informationEntity Relationship Modelling
Entity Relationship Modelling Overview Database Analysis Life Cycle Components of an Entity Relationship Diagram What is a relationship? Entities, attributes, and relationships in a system The degree of
More informationDatabase Systems. Overview - important points. Lecture 5. Some introductory information ERD diagrams Normalization Other stuff 08/03/2015
Lecture 5 Database Systems Instructor: M.Imran Khalil Imrankhalil3@gmail.com Resource:Imrankhalil3.wordpress.com University of Sargodha Canal Campus Lahore Overview - important points Some introductory
More informationThe Entity-Relationship Model
The Entity-Relationship Model Chapter 2 Instructor: Vladimir Zadorozhny vladimir@sis.pitt.edu Information Science Program School of Information Sciences, University of Pittsburgh 1 Database: a Set of Relations
More informationConceptual Modeling in ER and UML
Courses B0B36DBS, A7B36DBS: Database Systems Practical Classes 01 and 02: Conceptual Modeling in ER and UML Martin Svoboda 21. and 28. 2. 2017 Faculty of Electrical Engineering, Czech Technical University
More informationChapter 6: Entity-Relationship Model
Chapter 6: Entity-Relationship Model Database System Concepts, 5th Ed. See www.db-book.com for conditions on re-use Chapter 6: Entity-Relationship Model Design Process Modeling Constraints E-R Diagram
More informationDatabase Design Process. Requirements Collection & Analysis
Database Design Process Real World Functional Requirements Requirements Analysis Database Requirements Functional Analysis Access Specifications Application Pgm Design E-R Modeling Choice of a DBMS Data
More informationCMSC 424 Database design Lecture 3: Entity-Relationship Model. Book: Chap. 1 and 6. Mihai Pop
CMSC 424 Database design Lecture 3: Entity-Relationship Model Book: Chap. 1 and 6 Mihai Pop Database Design Steps Entity-relationship Model Typically used for conceptual database design info Conceptual
More informationEnhanced Entity-Relationship (EER) Modeling
CHAPTER 4 Enhanced Entity-Relationship (EER) Modeling Copyright 2017 Ramez Elmasri and Shamkant B. Navathe Slide 1-2 Chapter Outline EER stands for Enhanced ER or Extended ER EER Model Concepts Includes
More informationChapter (4) Enhanced Entity-Relationship and Object Modeling
Chapter (4) Enhanced Entity-Relationship and Object Modeling Objectives Concepts of subclass and superclass and the related concepts of specialization and generalization. Concept of category, which is
More informationDATABASE SYSTEMS. Chapter 5 Entity Relationship (ER) Modelling DESIGN IMPLEMENTATION AND MANAGEMENT INTERNATIONAL EDITION ROB CORONEL CROCKETT
DATABASE SYSTEMS DESIGN IMPLEMENTATION AND MANAGEMENT INTERNATIONAL EDITION ROB CORONEL CROCKETT Chapter 5 Entity Relationship (ER) Modelling 1 Coronel & Crockett 978184480731) In this chapter, you will
More informationConceptual Design. The Entity-Relationship (ER) Model
Conceptual Design. The Entity-Relationship (ER) Model CS430/630 Lecture 12 Slides based on Database Management Systems 3 rd ed, Ramakrishnan and Gehrke Database Design Overview Conceptual design The Entity-Relationship
More informationcourse 3 Levels of Database Design CSCI 403 Database Management Mines Courses ERD Attributes Entities title 9/26/2018
3 Levels of Database Design CSCI 403 Database Management 13 Database Modeling with Entity-Relationship Diagrams Conceptual (this lecture) Understand data entities & relationships between them Communication
More informationCOMP 244 DATABASE CONCEPTS & APPLICATIONS
1 COMP 244 DATABASE CONCEPTS & APPLICATIONS Entity-Relationship Diagrams 2 ER-Diagram Notations Attribute Key Attribute Multi-valued attributes Derived Attribute Weak Entity Identifying Relationship 3
More informationTranslating an ER Diagram to a Relational Schema
Translating an ER Diagram to a Relational Schema CS386/586 Introduction to Database Systems, Lois Delcambre 1999-2009 Slide 1 Translate each entity set into a table, with keys. Entity set: represented
More informationCOSC 304 Introduction to Database Systems. Entity-Relationship Modeling
COSC 304 Introduction to Database Systems Entity-Relationship Modeling Dr. Ramon Lawrence University of British Columbia Okanagan ramon.lawrence@ubc.ca Conceptual Database Design Conceptual database design
More informationRoadmap of This Lecture. Weak Entity Sets Extended E-R Features Reduction to Relation Schemas Database Design UML*
E-R Model (II) 1 Roadmap of This Lecture Weak Entity Sets Extended E-R Features Reduction to Relation Schemas Database Design UML* 2 Weak Entity Sets An entity set that does not have a primary key is referred
More informationDatabase Systems: Design, Implementation, and Management Tenth Edition. Chapter 4 Entity Relationship (ER) Modeling
Database Systems: Design, Implementation, and Management Tenth Edition Chapter 4 Entity Relationship (ER) Modeling Objectives In this chapter, students will learn: The main characteristics of entity relationship
More informationTranslation to Relational Schema
Translation to Relational Schema Agenda this Week Translation of the Entity Relationship Diagram into a Relational Schema Understanding the Stable Translation method Understanding the concept of Foreign
More informationData Analysis 1. Chapter 2.1 V3.1. Napier University Dr Gordon Russell
Data Analysis 1 Chapter 2.1 V3.1 Copyright @ Napier University Dr Gordon Russell Entity Relationship Modelling Overview Database Analysis Life Cycle Components of an Entity Relationship Diagram What is
More informationCSIT5300: Advanced Database Systems
CSIT5300: Advanced Database Systems L01: Entity Relationship (ER) Model Dr. Kenneth LEUNG Department of Computer Science and Engineering The Hong Kong University of Science and Technology Hong Kong SAR,
More informationCSE 530A. ER Model. Washington University Fall 2013
CSE 530A ER Model Washington University Fall 2013 Database Design Requirements Analysis Conceptual Database Design Creates an abstract model Logical Database Design Converts abstract model to concrete
More informationChapter 2 Conceptual Modeling. Objectives
Chapter 2 Conceptual Modeling Basic Entity Relationship Diagrams 1 Objectives Definition of terms Importance of data modeling Write good names and definitions for entities, relationships, and attributes
More information