CS 3630 Database Design and Implementation

Slides:



Advertisements
Similar presentations
Conceptual / semantic modelling
Advertisements

Database Design: ER Modelling (Continued)
Chapter 2.2 V3.0 Napier University Dr Gordon Russell
ER Modeling Case Studies
Chapter 12 Enhanced Entity-Relationship Modeling Transparencies © Pearson Education Limited 1995, 2005.
Enhanced Entity-Relationship Modeling. Strong and Weak Entity Types Strong entity: Each object is uniquely identifiable using primary key of that entity.
Data Modeling (CB 12) CPSC 356 Database Ellen Walker Hiram College (Includes figures from Database Systems by Connolly & Begg, © Addison Wesley 2002)
Methodology Logical Database Design for the Relational Model
Enhanced Entity-Relationship Modeling
1 Database Systems: A Practical Approach to Design, Implementation and Management International Computer Science S. Carolyn Begg, Thomas Connolly Lecture.
1 Enhanced Entity Relationship Modelling EER Model Concepts Includes all basic ER modeling concepts Additional concepts: subclasses/superclasses specialization/generalization.
Enhanced ER modeling techniques Transparencies
Entity-Relationship (E-R) Model
December 4, 2002 Data Modeling – James Cohen Enhanced Entity Relationship (EER) Model Presented by James Cohen.
EXTENDED-ER (EER) MODEL CONCEPTS. Enhanced-ER (EER) Model Concepts  Basic ER diagram + more concepts =EER model  Additional concepts:  Subclasses/superclasses.
Enhanced Entity-Relationship Model (EER) 1. Enhanced-ER (EER) Model Concepts Includes all modeling concepts of basic ER Additional concepts: subclasses/superclasses,
Extending ER Diagrams (13) CPSC 356 Database Ellen Walker Hiram College (Includes figures from Database Systems: A Practical Approach to Design, Information.
Chapter 2 Entity-Relationship Model Chapter 11 & 12 in Textbook.
Team Dosen UMN ER Modelling Connolly Book Chapter
Entity Relationship Modeling
Switch off your Mobiles Phones or Change Profile to Silent Mode.
Dr Gordon Russell, Napier University Data Analysis 2 - V2.0 1 Data Analysis 2 Unit 2.2.
Chapter 12 Entity-Relationship Modeling Pearson Education © 2009.
CSC271 Database Systems Lecture # 25. Summary: Previous Lecture  Structural constraints  Multiplicity  Cardinality  Participation  Connection traps.
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.
Enhanced Entity-Relationship Modeling
Part3 Database Analysis and Design Techniques Chapter 05- Entity-Relationship Modeling Lu Wei College of Software and Microelectronics Northwestern Polytechnical.
Data Analysis 4 Chapter 2.4 V3.0 Napier University Dr Gordon Russell.
Chapter 11 (2) CIS458 Sungchul Hong. Structural Constraints Main type of constraint on relationships is called multiplicity. Multiplicity - number (or.
April 20022/CS/3X EER 1 Database Design Enhanced entity-relationship modelling John Wordsworth Department of Computer Science The University of Reading.
Advanced Database and Client Server Applications Susan Curtis, Paul Crowther, Alan Houldcroft, Peter Lake, John Whitfield.
Database Systems 主講人 : 陳建源 日期 :99/10/19 研究室 : 法 Chapter 4 Enhanced Entity-Relationship and Object Modeling.
ENTITY-RELATIONSHIP MODELLING. Objectives: How to use Entity–Relationship (ER) modelling in database design. Basic concepts associated with ER model.
Databases (CS507) CHAPTER 7.
CS 3630 Database Design and Implementation
Enhanced Entity-Relationship Modeling
Chapter # 3 Data Modeling Using the Entity-Relationship (ER) Model
Enhanced Entity-Relationship Modeling
Enhanced Entity-Relationship and Object Modeling Objectives
Conceptual Design & ERD Modelling
CS 3630 Database Design and Implementation
The Enhanced Entity- Relationship (EER) Model
Session 2 Welcome: The sixth learning sequence
The Relational Model May Aldoayan.
Logical Database Design for the Relational Model
CS 3630 Database Design and Implementation
Enhanced ER Modeling Transparencies
Database EER.
Figure Specialization Hierarchy
Chapter 13 Enhanced Entity-Relationship Modeling
CS 3630 Database Design and Implementation
Entity-Relationship Modeling
Data Modeling with Entity Relationship Diagrams (Cont.)
Enhanced Entity-Relationship Modeling
Chapter Entity-Relationship Modeling & Enhanced Entity- Relationship Modeling.
Data Analysis 4 Unit 2.4 Dr Gordon Russell, Napier University
CS4222 Principles of Database System
376a. Database Design Dept. of Computer Science Vassar College
Enhanced Entity-Relationship Modeling Transparencies
Enhanced Entity-Relationship Modeling Transparencies
Enhanced Entity-Relationship Modeling
Chapter Entity-Relationship Modeling & Enhanced Entity- Relationship Modeling.
Database EER.
ENHANCED ENTITY-RELATIONSHIP (EER) MODEL
Sampath Jayarathna Cal Poly Pomona
Enhanced Entity-Relationship Modeling
Data Analysis 2 Unit 2.2 Dr Gordon Russell, Napier University
Enhanced Entity-Relationship Modeling
Presentation transcript:

CS 3630 Database Design and Implementation

Problems with E-R Model Fan Traps College Faculty Department Has Operates The relationship between Faculty and Department is missing.

Problems with E-R Model Correcting Fan Traps The relationship between College and Faculty is maintained Department College Faculty Has Operates

Problems with E-R Model Chasm Traps Staff Branch PropertyForRent Has Oversees 1..1 1..* 0..1 0..* The relationship between PropertyForRent and Branch may be missing.

Problems with E-R Model Correcting Chasm Traps One extra relationship is needed Staff Branch PropertyForRent Has Oversees 1..1 1..* 0..1 0..* Offers 1..1 1..*

EER: Enhanced E-R Model Specialization / Generalization SubClass / SuperClass Not required for Assignment 3

Subclasses for Different Roles SuperClass: Staff SubClasses: Manager Instructor SalesPersonnel Secretary

Common and Different Attributes SuperClass: Staff: staffNo, name, address, phone, salary SubClasses: Manager: mgrStartDate, bonus SalesPersonnel: salesArea, carAllowance Secretary: typingSpeed

Different Entities for Subclasses? staffNo Name Position Bonus salesArea typingSpeed SL21 John White Manager 2000 SG37 Ann Beech Secretary 100 SA9 Mary Howe Sales Asst SA1A

Constraints for Sub-Classes Participation: Mandatory Optional Disjoint: Disjoint (or) Non-disjoint (and) Business Rules

Participation: Mandatory SuperClass: Staff SubClasses PartTime FullTime

Participation: Optional SuperClass: Staff SubClasses Supervisor Supervisee

Disjoint (Xor) SuperClass: Staff SubClasses PartTime FullTime

Nondisjoint (And) SuperClass: Staff SubClasses: Manager SalesPersonnel Secretary

EER Diagram Staff staffNo Manager bonus SalesPersonnel salesArea {Mandatory, And} Manager bonus SalesPersonnel salesArea Secretary typingSpeed

EER Diagram Staff staffNo FullTime salaryScale PartTime hoursRate {Mandatory, Xor} FullTime salaryScale PartTime hoursRate

Assignment3 EER not required.