Soapbox: Producing Database Schema for DDI4 Dr. Brigitte Mathiak.

Slides:



Advertisements
Similar presentations
Three-Step Database Design
Advertisements

Nested state diagrams:Problems with flat state diagram
Michael Pizzo Software Architect Data Programmability Microsoft Corporation.
Database Systems: Design, Implementation, and Management Ninth Edition
© Krumbein / Kudrass ADBIS | 2003 September 3-6, 2003, Dresden, Germany {kudrass | Thomas Kudrass, Tobias Krumbein Rule-Based.
Chapter 2 Data Models Database Systems: Design, Implementation, and Management, Seventh Edition, Rob and Coronel.
Database Design (Data Modeling) DCO11310 Database Systems and Design By Rose Chang.
Object Relational Mapping. What does ORM do? Maps Object Model to Relational Model. Resolve impedance mismatch. Resolve mapping of scalar and non-scalar.
Geographic Information Systems
Database Systems: Design, Implementation, and Management Eighth Edition Chapter 2 Data Models Database Systems, 8th Edition 1.
Chapter 4 Entity Relationship (E-R) Modeling
Course Instructor: Aisha Azeem
Framework for Model Creation and Generation of Representations DDI Lifecycle Moving Forward.
Modernizing the Data Documentation Initiative (DDI-4) Dan Gillman, Bureau of Labor Statistics Arofan Gregory, Open Data Foundation WICS, 5-7 May 2015.
NIEM-UML Profile Justin Stekervetz, NIEM PMO
CSE446 S OFTWARE Q UALITY M ANAGEMENT Spring 2014 Yazılım ve Uyguluma Geliştirme Yöneticisi Orhan Başar Evren.
2 1 Chapter 2 Data Model Database Systems: Design, Implementation, and Management, Sixth Edition, Rob and Coronel.
1 CIM User Group Conference Call december 8th 2005 Using UN/CEFACT Core Component methodology for EIC/TC 57 works and CIM Jean-Luc SANSON Electrical Network.
Controlled Vocabularies for DDI 4 How to represent CVs?
IS-907 Java EE JPA: Simple Object-Relational Mapping.
2 1 Chapter 2 Data Models Database Systems: Design, Implementation, and Management, Seventh Edition, Rob and Coronel.
Database Design - Lecture 2
Database Systems: Design, Implementation, and Management Ninth Edition
Relational DB Components
A Z Approach in Validating ORA-SS Data Models Scott Uk-Jin Lee Jing Sun Gillian Dobbie Yuan Fang Li.
IE 423 – Design of Decision Support Systems Data modeling and database development.
1 Java Inheritance. 2 Inheritance On the surface, inheritance is a code re-use issue. –we can extend code that is already written in a manageable manner.
Chapter # 2 Data Models BIS Database Systems A.Thanop Somprasong
Chapter 9 Moving to Design
Object Oriented Analysis and Design 1 Chapter 7 Database Design  UML Specification for Data Modeling  The Relational Data Model and Object Model  Persistence.
The european ITM Task Force data structure F. Imbeaux.
Chapter 38 Persistence Framework with Patterns 1CS6359 Fall 2011 John Cole.
©Silberschatz, Korth and Sudarshan2.1Database System Concepts Chapter 2: Entity-Relationship Model Entity Sets Relationship Sets Design Issues Mapping.
Chapter 2 : Entity-Relationship Model Entity Sets Relationship Sets Design Issues Mapping Constraints Keys E-R Diagram Extended E-R Features Design of.
Component 4/Unit 6b Topic II Relational Databases Keys and relationships Data modeling Database acquisition Database Management System (DBMS) Database.
Jozef Kuper.  Describe a Database  Entities  Atributes  Relationships.
Object-Oriented Modeling: Static Models. Object-Oriented Modeling Model the system as interacting objects Model the system as interacting objects Match.
Seminar 10: OODB Design (Self-Study)
SimDB Implementation & Browser IVOA InterOp 2008 Meeting, Theory Session 1. Baltimore, 26/10/2008 Laurent Bourgès This work makes use of EURO-VO software,
11 Chapter 11 Object-Oriented Databases Database Systems: Design, Implementation, and Management 4th Edition Peter Rob & Carlos Coronel.
Copyright © 2013 by The McGraw-Hill Companies, Inc. All rights reserved. McGraw-Hill/Irwin APPENDIX C DESIGNING DATABASES APPENDIX C DESIGNING DATABASES.
ModTransf A Simple Model to Model Transformation Engine Cédric Dumoulin.
1 ER Modeling BUAD/American University Mapping ER modeling to Relationships.
Winter 2011SEG Chapter 11 Chapter 1 (Part 1) Review from previous courses Subject 1: The Software Development Process.
Chapter 16 UML Class Diagrams 1CS6359 Fall 2012 John Cole.
Declarative Languages and Model Based Development of Web Applications Besnik Selimi South East European University DAAD: 15 th Workshop “Software Engineering.
Chapter 16 UML Class Diagrams.
Towards Unifying Vector and Raster Data Models for Hybrid Spatial Regions Philip Dougherty.
Mapping Objects ↔Relational DB. The Problem with Databases Databases store data in rows in tables, which are not like objects. We can simulate object.
©Silberschatz, Korth and Sudarshan2.1Database System Concepts Chapter 2: Entity-Relationship Model Entity Sets Relationship Sets Mapping Constraints Keys.
Database System Concepts, 6 th Ed. ©Silberschatz, Korth and Sudarshan See for conditions on re-usewww.db-book.com Chapter 7: Entity-Relationship.
DOMAIN DRIVEN DESIGN Dave 12 May WHAT IS DDD? Set of principles to aid in building complex systems Enables us to focus on core problem domain NOT.
ORM Basics Repository Pattern, Models, Entity Manager Ivan Yonkov Technical Trainer Software University
Data Models. 2 The Importance of Data Models Data models –Relatively simple representations, usually graphical, of complex real-world data structures.
Geographic Information Systems GIS Data Databases.
OGP Seabed Survey Data Model (SSDM)
New Technology: Why, What ,How
Data Modeling II XML Schema & JAXB Marc Dumontier May 4, 2004
Geographic Information Systems
UML to XSD.
UML UML Data Modeling.
Advanced Database Models
System models October 5, 2005.
.NET Database Technologies:
ITEC 3220A Using and Designing Database Systems
ER Example Expressed as IMM Core Instance Specifications
Database 2.
Geographic Information Systems
Software Architecture & Design
Presentation transcript:

Soapbox: Producing Database Schema for DDI4 Dr. Brigitte Mathiak

Libraries for automation English + UML XML Schema Java.NET relDB Conceptual layer Implementation layer Data exchange layer Data storage layer JPA JAXB TODO

UML meta model Classes (DDIObject, Study) the entities/objects Attributes (label, year) properties of said objects Inheritance (between DDIObject and Study) means one class has all the attributes of the other Aggregation (between Study and Dataset) Dataset belongs to the study DDIObject label Study year Dataset

public class Study extends private String year; } JAXP generates Minor manual adjustments needed for core and some relationships

Aggregation @ManyToMany private List variable = new ArrayList (); Aggregation is a bit more complicated, as it has to be treated differently between XML (one-to-many) and relDB (ManyToMany) We automatically produce a flat-hierarchy XML with IDs for everything DB is more complicated – manyToMany is undesirable for many reasons – Better is to restrict navigation as often as possible to produce artificial one-to-many relationships – More on

TODO Synchronize with the work already done by Oliver Hopt concerning XSD Schema Update the prototype with the new input from this Sprint Make decisions concerning grouping and its DB representation

Dedicated grouping objects Disadvantages – Bloats the model, because many objects double – Transforms to a lot of manyToMany tables in DB – Instances have an additional required level – Many level hierarchies have to be modeled explicitly Advantages – Can model every level of type safety Grouping modelling options (1) CodeScheme Code *

Grouping modelling options (2) Composite pattern: – Reduces complexity on the instance level – Really simple DB representation OR Component informationparent Component informationparenthIndex

… even simpler This is the natural collapse of the Composite Pattern – (only if both leaf and the composite do not carry additional attributes) This is not type safe Stuff *

Target structure property value … XXX …