This document discusses the conceptual data vault modeling approach. It presents a sample data vault model and describes schema transformation rules to move from a 3NF model to a raw vault/staging area to dimensional structures. It also discusses leveraging existing modeling tools to implement the conceptual data vault by feeding the tools configuration through XML transformation or other means. The work on formalizing and fully implementing the conceptual data vault approach is described as still in progress.

1. Presented by:
© 2018-2019 Genesee Academy, LLC
www.GeneseeAcademy.com
Conecptional Data Vault
Torsten Glunde
tglunde
DVEM Rising, Colorado USA, October 2018

2. Conceptional Data Vault Model
 Paper Jovanovic and Bojicic from
2012 http://sais.aisnet.org/2012/JovanovicBojicic.pdf
 Meta model with versioning and
formalized transformation rules
 Source 3NF -> Raw Vault /
Staging -> Dimensional
 Alternativ
• ELM -> “Vault Logical“
• Transform to Vault physical

3. Sample Model

4. Schema Transformation Rules

5. Alternative Generalization

6. Leveraging existing modeling tools and Know-How
• Feeding the Tools with Configuration
o XML Transformation
o Xtext based
• Existing Tools
o SAP PowerDesigner
o MID Innovator
o IBM Data Architect
• Mapping for Source and Business Rules
o Editor für Attributzuordnung (Stage - RAW
Vault)
o Mapping Keyword Hub/Link/Satellit
o Driving Key am Satellit Keyword
• Formalization and C-DV implementation
unfinished work in progress

7. Model Driven Development
Cube
(PSA)
Stage
Other
Relational
“Physical Vault”
Data Flow
“Logical Vault”
Conceptional
Map
Core – Data VaultLanding
Mart
Generator ETLETL
Map Soft RulesMap 1:1 + Hard Rules
Attribut
mapping
1 2 3 4
Hard Rules
Star
ETL
Mapping Specification
BPMN, DMN
Transform

8. Barebone Model
Reg
Countr
yJob Emp
Dep Loc
 3NF Version of ELM
• Adding Business Key
• Adding Cardinality
• Adding NBR Role Names
 Sticking to business language
 No technical Detail
• No Keyed Instance, Satellite nor Hub
• Implementation agnostic