Database Design With Semantic Object Models

Slides:



Advertisements
Similar presentations
Database Lecture Notes Mapping ER Diagrams to Tables 2 Dr. Meg Murray
Advertisements

Basic notation for supertype/subtype relationships
Database Processing: Fundamentals, Design, and Implementation, 9/e by David M. KroenkeChapter 5/1 Copyright © 2004 Please……. No Food Or Drink in the class.
--The Entity Relationship Model(3)--1 Outline  ER model  Overview  Entity types Attributes, keys  Relationship types  Weak entity types  Uses Crows.
Chapter 6 Advanced Data Modelling
Fundamentals, Design, and Implementation, 9/e COS 346 Day 8.
© 2005 by Prentice Hall 1 Chapter 5: Logical Database Design and the Relational Model Modern Database Management 7 th Edition Jeffrey A. Hoffer, Mary B.
Fundamentals, Design, and Implementation, 9/e Chapter 5 Database Design.
DAVID M. KROENKE’S DATABASE PROCESSING, 10th Edition © 2006 Pearson Prentice Hall 6-1 David M. Kroenke Database Processing Chapter 6 Transforming Data.
DAVID M. KROENKE’S DATABASE PROCESSING, 10th Edition © 2006 Pearson Prentice Hall 6-1 COS 346 Day 10.
Chapter Five Data Modeling with the Entity-Relationship Model.
1 © Prentice Hall, 2002 Chapter 5: Logical Database Design and the Relational Model Modern Database Management 6 th Edition Jeffrey A. Hoffer, Mary B.
DAVID M. KROENKE’S DATABASE PROCESSING, 10th Edition © 2006 Pearson Prentice Hall 6-1 David M. Kroenke’s Chapter Six: Transforming Data Models into Database.
DAVID M. KROENKE’S DATABASE PROCESSING, 10th Edition © 2006 Pearson Prentice Hall 5-1 COS 346 Day 8.
© 2002 by Prentice Hall 1 David M. Kroenke Database Processing Eighth Edition Chapter 6 Database Design Using Entity- Relationship Models.
Fundamentals, Design, and Implementation, 9/e COS 346 Day 2.
DAVID M. KROENKE’S DATABASE PROCESSING, 10th Edition © 2006 Pearson Prentice Hall 6-1 David M. Kroenke’s Chapter Six: Transforming ER Models into Database.
DAVID M. KROENKE’S DATABASE PROCESSING, 10th Edition © 2006 Pearson Prentice Hall 6-1 David M. Kroenke’s Chapter Six: Transforming ER Models into Database.
Michael F. Price College of Business Chapter 6: Logical database design and the relational model.
Chapter 3: The Enhanced E-R Model
Database Design.  Define a table for each entity  Give the table the same name as the entity  Make the primary key the same as the identifier of the.
© 2007 by Prentice Hall (Hoffer, Prescott & McFadden) 1 The Relational Model (Advanced)
 Keys are special fields that serve two main purposes: ◦ Primary keys are unique identifiers of the relation in question. Examples include employee numbers,
Chapter 91 ER & EER to Relational Mapping. Chapter 92 ER to Relational Mapping Step 1: For each regular entity type E in the ER schema, create a relation.
6.8 Case Study: E-R for Supplier-and-Parts Database
Converting ER model Into Relational Table
MIS 385/MBA 664 Systems Implementation with DBMS/ Database Management Dave Salisbury ( )
Chapter Six Professor Adams’ Slides. Note that entities are shadowed, tables are not. Note that entities have no physical existence (blueprint) Note.
Database Processing: Fundamentals, Design and Implementation, 9/e by David M. KroenkeChapter 2/1 Copyright © 2004 Please……. No Food Or Drink in the class.
Database Application Design n Characteristics of Database Applications n Form Design n Report Design n Application Program Design.
Normalization A technique that organizes data attributes (or fields) such that they are grouped to form stable, flexible and adaptive entities.
Database Design Using Entity-Relationship Models Transformation of Entity-Relationship Models into Relational Database Design Trees, Networks, and Bills.
Database Design IST210 Class Lecture
©Silberschatz, Korth and Sudarshan2.1Database System Concepts Chapter 2: Entity-Relationship Model Entity Sets Relationship Sets Design Issues Mapping.
IS 475/675 - Introduction to Database Design
DAVID M. KROENKE’S DATABASE PROCESSING, 10th Edition © 2006 Pearson Prentice Hall 6-1 David M. Kroenke’s Chapter Six: Transforming Data Models into Database.
The Semantic Object Model Semantic Objects Creating Data Models with Semantic Objects Types of Objects Object-Oriented Programming and Semantic Objects.
DESIGN AND IMPLEMENTATION DATA MODELING TOOLS Indah Puspa Sari ( ) Advisor : Adi Wibowo, M.T. Andreas Handojo, M.MT.
DataBase Management System What is DBMS Purpose of DBMS Data Abstraction Data Definition Language Data Manipulation Language Data Models Data Keys Relationships.
The Entity-Relationship 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.
In this session, you will learn to: Map an ER diagram to a table Objectives.
Mapping from conceptual model (EER-M)
1 Chapter 17 Methodology - Local Logical Database Design.
Chapter 4 The Semantic Object Model David M. Kroenke Database Processing © 2000 Prentice Hall.
Logical Database Design and the Relational Model.
Fundamentals, Design, and Implementation, 9/e Appendix B The Semantic Object Model.
Logical Database Design and the Relational Model.
Transforming ER models to relational schemas
Chapter 14 Semantic Modeling. Copyright © 2004 Pearson Addison-Wesley. All rights reserved.14-2 Topics in this Chapter The Overall Approach The E/R Model.
David M. Kroenke and David J. Auer Database Processing Fundamentals, Design, and Implementation Chapter Five: Data Modeling with the Entity-Relationship.
Lecture 4: Logical Database Design and the Relational Model 1.
David M. Kroenke and David J. Auer Database Processing Fundamentals, Design, and Implementation Appendix H: The Semantic Object Model.
Database Design with Semantic Object Models zMapping 7 types of semantic objects into relations.
Lecture # 14 Chapter # 5 The Relational Data Model and Relational Database Constraints Database Systems.
Chapter 5 Database Design
Semantic Object Modeling (SOM)
Chapter 4: Logical Database Design and the Relational Model
Chapter 4: Part B Logical Database Design and the Relational Model
SEEM3430: Information Systems Analysis and Design
Requirements Become the E-R Data Model
Chapter 5: Logical Database Design and the Relational Model
Quiz Questions Q.1 An entity set that does not have sufficient attributes to form a primary key is a (A) strong entity set. (B) weak entity set. (C) simple.
Advanced Database System
Database Design with Semantic Object Models
Software : TableDesigner
Semantic Objects.
CHAPTER 4: LOGICAL DATABASE DESIGN AND THE RELATIONAL MODEL
Database Processing: David M. Kroenke’s Chapter Six:
Presentation transcript:

Database Design With Semantic Object Models Transformation of Semantic Objects into Relational Database Designs Sample Objects

Seven Types of Semantic Objects Simple Objects Single relation. Fig. 7-2,1 Composite Objects One relation for the object and another relation for each multivalued attribute. The key of these relations is the composite of the identifier of the object plus the identifier of the group. Fig. 7-3,4 Compound Objects The relationships (1:1, 1:N, N:M) between objects need to be considered.

Semantic Objects Into Relations (Cont.) 1:1 Compound Objects One relation is needed for each object. Relations are associated by placing the key of either relation as a foreign key in the other relation. Fig. 7-6,7 1:N and N:1 Compound Objects Each object is represented with a relation and the key of the parent is place in the child. Fig. 7-8,9 N:M Compound Objects One relation is needed for each object and a third one to be the intersection relation. Fig. 7-10,11

Semantic Objects Into Relations (Cont.) Hybrid Objects Transformed into relations using a combination of the techniques for composite and compound objects. Fig.7-12,13,14 Association Objects Use a relation for each of the three associated objects, and then represent the relationships among the objects using the strategies used with compound objects. Fig. 7-15,16

Semantic Objects Into Relations (Cont.) Supertype (Parent) /Subtype Objects Define a relation for the parent object and one for each of the subtype objects. The key of all these relations in the key of the parent. Fig. 7-17,18 Archetype/Version Objects These are compound objects that model various instances of the basic object e.g. releases of software products. Fig. 7-19,20

Sample Objects Subscription Form -> Fig. 7-21 Product Description -> Fig. 7-22 Traffic-Warning Citation -> Fig. 7-23