Data Model Scorecard : Semantic Data

Model Validation
1. How well do the characteristics of the model support the type
of model?

2. How well does the model capture the requirements?

3. How complete is the model?
4. How structurally sound is the model?
5. How well does the model leverage generic structures?
6. How well does the model follow naming standards?
7. How well has the model been arranged for readability?
8. How good are the definitions?
9. How consistent is the model with the enterprise?
10. How well does the metadata match the data?
1

3/7/16

Teradata Confidential

1. How Well Do the

Characteristics of the Model
Support the Type of Model?
Model type category
> Ensures that the definition for the model type is

met

Relational
Conceptual

Dimensional

Logical
Physical

Semantic data model red flags

> Normalized structure for analytics
> There are subtypes on the model
> Fuzzy grain
2

3/7/16

Teradata Confidential

2. How Well Does the Model

Capture the Requirements?
Correctness category
> Ensures the model accurately represents the

business and supports the application requirements

Semantic data model red flags

> Data Lab not leveraged
> Useless aggregates
> Data elements with a data modeling tool default

format

3/7/16

Teradata Confidential

3. How Complete is the Model?

Completeness category
> Ensures content and metadata are not leading

towards scope creep or Phase II

Semantic data model red flags

> Missing precise and complete set of business

questions
> Missing definitions
> Missing nullability

3/7/16

Teradata Confidential

4. How Structurally Sound is the

Model?

Structure category
> Ensures that the model follows good design

principles

Semantic data model red flags

> Circular relationships
> Partial key relationship
> Data element appears more than once in

same model, but with different format or

length.

3/7/16

Teradata Confidential

5. How Well Does the Model

Leverage Generic Structures?
Abstraction category
> Ensures the correct level of generic concepts

are applied on the model

Semantic data model red flag

> Too abstract!

THING

3/7/16

Teradata Confidential

6. How Well Does the Model

Follow Naming Standards?
Confirms that structure, term, and
syntax have been correctly applied to
the model
Structure
One subject
area, zero or
more
modifiers, one
class word

CUST_LAST_NAM

Syntax
Plural or singular, whether hyphens,
spaces, or Camelback, and case
7

3/7/16

Teradata Confidential

Term
Proper
language and
abbreviations

7. How Well Has the Model Been

Arranged for Readability?

Readability category
> Ensures the model is easy to read!

Semantic data model red flags

> Dimensions do not surround the fact table
> A font that is too small
> Too many entities on one display

3/7/16

Teradata Confidential

8. How Good are the

Definitions?
Confirms all definitions are clear,
complete, and correct.
The Customer Identifier
is the identifier for the
customer
54

Formal

3/7/16

An employee is
someone who
breathes oxygen

Teradata Confidential

9. How Consistent is the Model

With the Enterprise?
Consistency category
> Ensures the model complements the Big

Picture

Semantic data model red flags

> SMBB not leveraged
> Dimension not conformed
> Impossible to source from integrated data layer

10

3/7/16

Teradata Confidential

10. How Well Does the Metadata

Match the Data?
Data category
> Ensures structure matches reality

Semantic data model red flags

> Data does not match definition, name, format, or

length of metadata.
> Data sparse in required data element
> Data duplicates in a unique data element
PRODUCT

Product Identifier

Extract files
Database tables
Data entry screens

Product
Product
Product
Product
Product
Product

CALENDAR
Month Code
Year Code
Month Name
Month Sequence Number (AK1.1)
Year Name
Year Sequence Number

11

3/7/16

Teradata Confidential

Name (AK1.1)
Frozen Indicator (AK1.2,IE1.1)
UPC Code (AK2.1)
EAN Number (AK3.1)
Line Name
Category Description Text

SALES
Product Identifier (FK)
Month Code (FK)
Year Code (FK)
Region Identifier (FK)
Gross Sales Amount

GEOGRAPHY
Region Identifier
Region Name (AK1.1)
Country Identifier
Country Name
Country ISO Code

Data Model Scorecard : Semantic Data

Model Validation

1. How well do the characteristics of the model support the type

of model?

2. How well does the model capture the requirements?

3. How complete is the model?
4. How structurally sound is the model?
5. How well does the model leverage generic structures?
6. How well does the model follow naming standards?
7. How well has the model been arranged for readability?
8. How good are the definitions?
9. How consistent is the model with the enterprise?
3/7/16
Teradata Confidential
10.12 How
well does the metadata
match the data?