Database Answers A Common Data Model

Home Ask a Question Best Practice Careers Contact Us Data Models Search Site Map
Semantic Data Models   

Back to the Data Model.
The Area being Modelled is :-
Semantic Data Models

A discussion on the topic of a Building Block Approach to Semantic Data Models was started by Elisia Getts on the Teradata Forums Web Site.

Here is the posting in full :-
"What is a building block approach to building semantic data models?
 The idea is that modeling constructs could be pre-defined and developed to promote rapid time to value, design flexibility, data consistency, and user-friendliness. 
 These building blocks could be collected into libraries, customized, and reused. 
 The building blocks could consist of star schema, analytical data set, data lab, and other types of building blocks along with guidelines for use and mappings to 
 pre-defined data models, such as the Teradata industry logical data models. 
 Different variations and recommended BI tools could also be defined for various building blocks.
 
 What are your thoughts on using a building block approach to build semantic data models ?"

A Semantic Data Model shows how a business user is likely to think about the data and the 'Things of Interest'. For example, a Data Modeller will typically think about a Party whereas a User will think about a Customer. In a similar way, an Address might be a user-friendly way of thinking about a Geographic Area and a Payment might correspond to a Financial Transaction.
A Semantic Data Model shows how a business user is likely to think about the data and the 'Things of Interest'.

For example, a Data Modeller will typically think about a Party whereas a User will think about a Customer.
In a similar way, an Address might be a user-friendly way of thinking about a Geographic Area and a Payment might correspond to a Financial Transaction.

The concept of Building Blocks also applies to Plug-and-Play Generic Components, such as a Data Warehouse, and the Data Model on the right shows a classic example. The idea of Generic Components starts us thinking about Generic Data Models that can provide us with Design Patterns.

This Semantic Data Model includes Customers, Addresses and Payments :-

Semantic Data Model for Customer, Addresses and Payments
This is a 'traditional' Data Warehouse for Customer Purchases :-

Customers and Purchases Data Warehouse
A good starting-point would be an Events-driven Canonical Data Model, such as this one, with specific Data Models for Subject Areas, such as Customers :-
This is a Canonical Data Model :-

Common Data Model


© DataBase Answers Ltd. 2012
About Us Contact Us