data modeling zone 2017

48
Data Modeling by Example © BCP Software / Marco Wobben

Upload: marco-wobben

Post on 22-Jan-2018

169 views

Category:

Technology


0 download

TRANSCRIPT

Page 1: Data Modeling Zone 2017

Data Modeling by Example

© BCP Software / Marco Wobben

Page 2: Data Modeling Zone 2017

• Capture business language

• Support agile modeling

• Validation by users

• Integrate documentation

• Include language domains

• Model once, bootstrap everything

What if?

Page 3: Data Modeling Zone 2017

Fact Oriented Modeling

Page 4: Data Modeling Zone 2017

Methods

• Development originated in the 70’s “one family, three relatives”

Method By Tool EmphasisNIAM Nijssen DocTool relational ORM Halpin NORMA constraints FCO-IM Bakema & co. CaseTalk communication

Page 5: Data Modeling Zone 2017

High level modeling

Page 6: Data Modeling Zone 2017

Specialists at work

Page 7: Data Modeling Zone 2017

Facts

Page 8: Data Modeling Zone 2017

Expression

Page 9: Data Modeling Zone 2017

Visualise

Page 10: Data Modeling Zone 2017

Generate

Page 11: Data Modeling Zone 2017

Communicate Data Capture Knowledge

Page 12: Data Modeling Zone 2017

FCO-IM

• Communication Oriented, • Information Modeling, • Fully.

Page 13: Data Modeling Zone 2017

Make it work

Page 14: Data Modeling Zone 2017

a Fact

Name of Customer: “Customer 4081 is Sandia Labs.”

Customer

Customer NoName

Name of Customer

Page 15: Data Modeling Zone 2017

Add Unicity

Customer

Customer NoName

Name of Customer

Name of Customer: “Customer 4081 is Sandia Labs.”

Page 16: Data Modeling Zone 2017

Agile: Add a Fact

Customer Location City

City Name

Customer

Customer NoName

Name of Customer: “Customer 4081 is Sandia Labs.” Customer Location: “Customer 4081 is located in Albuquerque.”

Name of Customer

Page 17: Data Modeling Zone 2017

Transformation(s)

Customer Location City

City Name

Customer

Customer NoName

Name of Customer: “Customer 4081 is Sandia Labs.” Customer Location: “Customer 4081 is located in Albuquerque.”

Name of Customer

Page 18: Data Modeling Zone 2017

Group (before)

Name of Customer: “Customer 4081 is Sandia Labs.” Customer Location: “Customer 4081 is located in Albuquerque.”

Customer Location City

City Name

Customer

Customer NoName

Name of Customer

consolidate identical populations

Page 19: Data Modeling Zone 2017

Group (after)

City

City Name

Customer

Customer NoName

Name: “Customer 4081 is Sandia Labs.” City: “Customer 4081 is located in Albuquerque.”

consolidate identical populations

Page 20: Data Modeling Zone 2017

Lexicalise

City

City Name

Customer

Customer NoName

Name: “Customer 4081 is Sandia Labs.” City Name: “Customer 4081 is located in Albuquerque.”

every place holder has a data type

Page 21: Data Modeling Zone 2017

City

City Name

Customer

Customer NoName

Reduce

Name: “Customer 4081 is Sandia Labs.” City Name: “Customer 4081 is located in Albuquerque.”

remove redundancy and unused concepts

Page 22: Data Modeling Zone 2017

City Name

Customer

Customer NoName

Generate Artifacts

Name: “Customer 4081 is Sandia Labs.” City Name: “Customer 4081 is located in Albuquerque.”

Page 23: Data Modeling Zone 2017

SQL DDL

CREATE TABLE Customer ( Customer_No integer NOT NULL, Name varchar(64), City_Name varchar(256), PRIMARY KEY (Customer_No) );

City Name

Customer

Customer NoName

Page 24: Data Modeling Zone 2017

Table Document

Page 25: Data Modeling Zone 2017

SQL DDL & DML

Page 26: Data Modeling Zone 2017

CDM

Page 27: Data Modeling Zone 2017

PDM

Page 28: Data Modeling Zone 2017

UML

Page 29: Data Modeling Zone 2017

XML Schema

Page 30: Data Modeling Zone 2017

Ontology

Page 31: Data Modeling Zone 2017

Validation

Page 32: Data Modeling Zone 2017

Rule Validation

Page 33: Data Modeling Zone 2017

Rule Validation

Page 34: Data Modeling Zone 2017

Rule Validation

Page 35: Data Modeling Zone 2017

Model Validation

Page 36: Data Modeling Zone 2017

User Validation

Page 37: Data Modeling Zone 2017

Why a Data Model?

• Capturing business requirements

• Promotes reuse, consistency, quality

• Bridge between business and technology personnel

• Avoid late discovery of missed requirements

• Critical in managing integration between systems

• Pre-cursor to DBMS design / generate DDL

Source: DAMA-I Survey

Page 38: Data Modeling Zone 2017

Practice

Page 39: Data Modeling Zone 2017

Work sheet

Page 40: Data Modeling Zone 2017

Work sheet

Page 41: Data Modeling Zone 2017

Work sheet

Employee Name: “Employee 618 has name Boven WJ van.”

Page 42: Data Modeling Zone 2017

Work sheet

Page 43: Data Modeling Zone 2017

Work sheet

Working Hours:“In week 200138 employee 618 worked on project 6323.16

for 2 hours on task 15.”

Page 44: Data Modeling Zone 2017

Work sheet

Working Hours:“In week 200138 employee 618 worked on project 6323.16

for 2 hours on task 15.”

Project Employee:’employee 618 worked on project 6323.16’

Page 45: Data Modeling Zone 2017

ArtifactsDatabases Oracle SQL Server MySQL SQLite SQL92 MongoDB Interbase MsAccess Denodo …

Other PowerDesigner OWL/RDF XML Schema DWH Models Relational Diagrams UML Class Diagrams HTML + Images Spreadsheets …

Page 46: Data Modeling Zone 2017

Some Customers

• Banking

• Travel

• Medical

• Education

• Government

Page 47: Data Modeling Zone 2017

Some MetricsKLM / m~ëëÉåÖÉê=C=`~êÖç ~ NRMM=Ñ~Åí=íóéÉë

ProRail / jÉí~=a~í~=j~å~ÖÉãÉåí ~ OMMM=Ñ~Åí=íóéÉë=

HAN University / léÉê~íáçå~ä ~ SMMM=Ñ~Åí=íóéÉë

Erasmus MC / a~í~=t~êÉÜçìëÉ ~ PRMM=Ñ~Åí=íóéÉë

Page 48: Data Modeling Zone 2017

Contact

j~êÅç=tçÄÄÉå=

ã~êÅçï]ÄÅéJëçÑíï~êÉKåä=

ïïïKÄÅéJëçÑíï~êÉKåä===L===ïïïKÅ~ëÉí~äâKÅçã