Deriving a Relational DB Model from the AIXM CM

Slides:



Advertisements
Similar presentations
Three-Step Database Design
Advertisements

MSc IT UFCE8K-15-M Data Management Prakash Chatterjee Room 2Q18
Copyright © 2011 Pearson Education, Inc. Publishing as Pearson Addison-Wesley Chapter 3 The Basic (Flat) Relational Model.
Informatiesystemen in de Bouw 7M711 Joran Jessurun en Jos van Leeuwen Week 3.
Data Management Design
The Relational Model Codd (1970): based on set theory Relational model: represents the database as a collection of relations (a table of values --> file)
July 14, 2015ICS 424: recap1 Relational Database Design: Recap of ICS 324.
Neo.NET Entity Objects Design Goals Copyright © Erik Dörnenburg – Last updated: May 2004.
DATA MODELING AND DATABASE DESIGN
Part 06 – A More Complex Data Model Entity Framework and MVC NTPCUG Tom Perkins.
1 CSE 480: Database Systems Lecture 5: Relational Data Model.
Lecture 7 Integrity & Veracity UFCE8K-15-M: Data Management.
Presented to: AIXM Developer’s Seminar By: Navin Vembar Date: January 14, 2010 Federal Aviation Administration Changes in AIXM 5.1 from AIXM 5.0.
M Taimoor Khan Course Objectives 1) Basic Concepts 2) Tools 3) Database architecture and design 4) Flow of data (DFDs)
IST 220 Introduction to Databases Course Wrap-up.
Database Systems Design, Implementation, and Management Coronel | Morris 11e ©2015 Cengage Learning. All Rights Reserved. May not be scanned, copied or.
Chapter 9 Constraints. Chapter Objectives  Explain the purpose of constraints in a table  Distinguish among PRIMARY KEY, FOREIGN KEY, UNIQUE, CHECK,
CSE314 Database Systems Lecture 3 The Relational Data Model and Relational Database Constraints Doç. Dr. Mehmet Göktürk src: Elmasri & Navanthe 6E Pearson.
The European Organisation for the Safety of Air Navigation AIXM UML to XSD AIXM XML Developers' Seminar.
AIXM 5 UML Modelling Conventions. AIXM is GML AIXM is an XML exchange standard based on a subset of GML. Essentially: –AIXM Features are GML features.
Experience with XML Schema Ashok Malhotra Schema Usage  Mapping XML Schema and XML documents controlled by the Schema to object classes and instances.
Jennifer Widom Relational Databases The Relational Model.
DATA MODELING AND DATABASE DESIGN DATA MODELING AND DATABASE DESIGN Part 2.
The relational model1 The relational model Mathematical basis for relational databases.
More SQL: Complex Queries, Triggers, Views, and Schema Modification
Microsoft Office Access 2010 Lab 1
AIXM 5 UML to XSD.
AIXM 5.1 XML Developers' Seminar #2 – Dec 2009
Modeling Constraints Extracting constraints is what modeling is all about. But how do we express them? Examples: Keys: social security number uniquely.
Relational Database Design by ER- and EER-to- Relational Mapping
EF Relations Object Composition
Chapter 6 - Database Implementation and Use
Prepared by : Moshira M. Ali CS490 Coordinator Arab Open University
Chapter 2: Relational Model
A brief summary of database normalization
Ikan Software NV CWD4ALL
Multiplication table. x
Chapter 2: Intro to 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.
Entity-Relationship Model
Lecture # 13 (After 1st Exam)
Chapter 3: Intro to Relational Model
UML to XSD.
Chapter 2: Intro to Relational Model
Chapter 2: Intro to Relational Model
Generalization.
Referential Integrity
Normalization Referential Integrity
Relational Databases The Relational Model.
Relational Databases The Relational Model.
.NET Database Technologies:
Database Management System
SQL OVERVIEW DEFINING A SCHEMA
Referential Integrity
Session 2 Welcome: The seventh learning sequence
Primary key Introduction Introduction: A primary key, also called a primary keyword, is a key in a relational database that is unique for each record.
CHAPTER 4: LOGICAL DATABASE DESIGN AND THE RELATIONAL MODEL
SQL DATA CONSTRAINTS.
Section 4.5A Calculus AP/Dual, Revised ©2019
Design tools and techniques for a relational database system
AIXM 5 UML Modelling Conventions
Chapter 2: Intro to Relational Model
Domains 4/17/2019 See scm-intranet.
Properties of Definite Integrals
Chapter 15: Object-Oriented Database Development
5. 3 Coding with Denotations
John Barnden Professor of Artificial Intelligence
Integrity 5/5/2019 See scm-intranet.
AIXM Seminar 2009, December 15th
New Applications Modeled
Presentation transcript:

Deriving a Relational DB Model from the AIXM CM

Automatic Generation with Rose Data Modeler Automatic generation of table definitions straightforward Problems: Disregards stereotypes, not controllable Associations: disregards type and navigability

Relational Schema Derivation – Features and Objects <<feature>> and <<object>> implemented as tables artificial primary key (UID) attribute to column

Relational Schema Derivation – Associations (1) Association with multiplicity upper bound 1  primary/foreign key dependency

Relational Schema Derivation – Associations (2) Association with multiplicity upper bound > 1  over additional mapping table

Relational Schema Derivation – Associations (3) Generalization  Equal primary keys of tables of general and special class

Relational Schema Derivation – Choice <<choice>> stereotype of features/objects  over mapping table (XOR: enforce one column null)

General Considerations – generic or specialized? Generic or highly specialized approach? One generic SegmentLeg table with type column or one table for every SegmentLeg specialization? Consistency could still be enforced with constraints

General Considerations – codelists, enums, datatypes Implementation of <<enumeration>> and <<codelist>> As enum column type (if available) or as code table? enum type strictly enforces limited value set code table better scalable/extendable Or: simply as string and enforce allowed values outside DB? Implement data types as column types in DB?  Philosophical question: Implement all constraints in DB?!?

Discussion!?!