adriennetannenbaum - congres bi

8/3/2019 AdrienneTannenbaum - Congres BI

1/51

12002Database Design Solutions, Inc.

40 Morristown Road, Suite 2BBernardsville, NJ 07924www.dbdsolutions.com

Metadata and Business

IntelligenceFeira Internacional deBusiness Intelligence

So Paulo, Brasil

19 de abril de 2002


2/51



Lining Up the Data

Connecting thenumbers withthe brains


3/51



Important Topics

o Metadata What it is

Its Impact on Business Intelligence (BI) o The Well-Instituted Metadata Environmento Metadata before BI

How to do it


4/51



The Ultimate Objective

KnowledgeInformation

Data

Metadata

Intelligence!


5/51



So Where is theKnowledge?

Databases

Documents

Employees

Applications


6/51



The 5 Questions

o What data do I have?o What does it mean?

o Where is it?o How did it get there?o How do I get it? (Go get it for me)


7/51



More 5 Questions

1. What meta data do I have?2. What does it mean?

3. Where is it?4. How did it get there?5. How do I get it? (Go get it for me)


8/51


9/51



Business Intelligence

o What do we have?o How much?o What have we done?

When? How often?

What resulted? Was it

worthwhile?


10/51



Can WE DeriveDecisions From BI?

Data

Metadata

Information


11/51



Not Without Metadata!o The Way Ino The Way Aroundo The Way Out


12/51



Business Intelligence?

o Without information,which stems fromdata and process,

businesses would befar from intelligent


13/512002 Database Design Solutions, Inc.


What is Metadata?


14/51


15/51



Metadatas Role J 5 0 4 3

Part Inventory Guide

Characters withoutContext

Context

InformationJ 5 0 4 3Part Number forWindshield Wiper

Instance Data

Metadata

Information


16/51



Putting MetadataInto Perspective

o We wouldn t be able to survive without it Unless we already experienced or interpreted

this data


17/51



The Map Analogy

o Instance Data: TheMap

o Metadata: The Legend


18/51



The SupermarketAnalogy

o Aisle markers Incorrect aisle markers Missing aisle markers


19/51



The ProductAssembly Analogy

o Ever try to putsomething togetherwithout instructions?

Or with incorrect instructions?

Or with instructions that make no sense?

How about with pieces that do not have part numbers?


20/51



Metadata Confirmedo It identifies what we want

What data do we have?

o It clarifies what we want What does it mean?

o It locates what we want Where is it?

o It validates what we want Where did it come from?

o It gets what we want How do I get it? Go get it for me!


21/51


22/51



Data/Metadata/Information

o What data do I have?o What does it mean?

o Where is it?o How did it get there?o How do I get it?

o Product_priceo The gross charge for

the firm s offerings,before any discountso Sales Database

Product Table

o Update_Product Program

o Product_price Query

Data: $46.30


23/51



Metadatas Impact on BI

o Consider finding all ofthe data that you needto make a decision

o Consider interpretingfound data

o Consider basing newdecisions on past

trends


24/51



Where Should theMetadata Come From?

o Is it already around?o Is it worth anything?o Should you create it

all over again?o How do you make the

right decision?


25/51

2002 Database Design Solutions, Inc.


The Well InstitutedMetadata Environment

What it is andhow to getthere


26/51


27/51



DevelopmentTool

DBMSCatalog

The IntegratedMetamodel

Reporting

Tool

Unique Development Metamodel ConstructsUnique Reporting Tool Metamodel Constructs

Common Metamodel Constructs

MetadataDatabase

MetadataDatabase

MetadataDatabase

How We Should HandleOur Metadata (Today?)


28/51



Well Instituted Means

o The metadata helps instead of hinderso Disparate metadata is logically organizedo Multiple metadata stores are possible, related,

and accessible. These metadata stores can be part of different vendor

products Architectural access points are common

o Individuals do not need to access an entirearchitecture to reach metadata that is specificto their world.


29/51



Worthwhile Metadata?

o Must have 5 stars Accuracy Consistency Modularity Represented Perspectives Ease of Identification


30/51



BecomingWell Instituted

o Scope your BusinessIntelligence World

Information Sources Involved

Tools/Products Metadata Requirements


31/51



The Need For Requirements

o Requirements = Planning.o Needed for Metadata Solutions as well as

for Data (Application) Solutions.o Don t build it before you know what it isbeing built for!

o Don t compromise requirements to matcha particular vendor solution


32/51



Requirements Approach

Data Requirementso Requirements come

from users (people )

o Some data could benew

Metadata Requirementso Requirements come

from users (people ,

tools, other metadatasolutions)

o Metadata already exists

Therefore, identifying MetadataRequirements requires a different

approach


33/51



The Metadata RequirementsAnalysis Process

o Needed for both smallstandalone Metadatasolutions and large

Enterprise widesolutions.


34/51



RequirementsProcess Steps

1. Identify Metadata Beneficiaries (i.e.,users , e.g, developers ).

2. List metadata requirements (e.g., dataelement definition ) by beneficiary. 3. Determine the source of each metadata

requirement (e.g, data dictionary). For multiple sources, identify the metadata

of record .


35/51



RequirementsProcess Steps contd

4. Plan preliminary architecture andmetadata solution scope.

5. Re-categorize metadata. Determine theusage category (i.e., specific , unique ,or common ) of each metadatarequirement.

6. Build metamodels; models of themetadata.


36/51



RequirementsProcess Steps contd

7. Consider access (i.e., CRUD = Create,Read, Update, Delete) and displayrequirements for metadata.

8. Anticipate metadata processingrequirements (usually specific tosoftware)

9. Consider non-metadata requirements(technical support, security, organization,etc.)


37/51



A Multi-ToolArchitecture

MetadataDatabase

BI Tool

DevelopmentToolDBMSCatalogMetadata

Database

MetadataDatabase

MetadataDatabase


38/51

382002Database Design Solutions, Inc.40 Morristown Road, Suite 2B

Bernardsville, NJ 07924www.dbdsolutions.com

A MetadataSolution Architecture

Database

Table

Column

DBMSCatalog

MetadataDatabase

DevelopmentTool

MetadataDatabase

MetadataDatabase

BITool

MetadataDatabase

Profile-

ControlledFormat

Search and Retrieve Internet Search Engines

Transfor-mation

SourceProgram

SourceData

Element

Report

Column

Source

DataElement

DBMS API s

XML Tagged

Exchange

Initial BatchLoad

DBMS API


39/51

392002Database Design Solutions, Inc. 40 Morristown Road, Suite 2BBernardsville, NJ 07924www.dbdsolutions.com

Sharing Metadata?o For Business

Intelligence to benefitfrom a well-institutedmetadata solution:

Each tool component has the ability to access metadata from outside of its own database

Non-tool users can access metadata within a

particular tool sdatabase

f d


40/51


If Its Good,Everyone Wants It

o Just make sureeveryone can get it!


41/51

2002 Database Design Solutions, Inc.


Metadata Before BI?

What comes first?


42/51


If BI Comes First o We put something

together beforereading the directions

o We go food shoppingwithout a list

o We buy clotheswithout trying them on

o We cook an egg andthen try to separate it


43/51


If Metadata Comes Firsto We travel with directionso We cook with recipeso We shop with listso We try before we buy

Everything is performed: More efficiently With few errors In substantially less time!

S i BI


44/51


Supporting BIWith Metadata

Getting Started

S li Y


45/51


Sealing Your Requirements

1. Determine the data to be used for BI Current Data Stores Original Sources Transitions Along the Way

2. Evaluate its associated metadata (if you have it!) Does it answer the 5 Questions

What data do I have (available for BI)? What does it mean? Where is it (within my BI world)? How did it get there (sourcing)? How do I get it (BI tool query, etc.)

S li Y


46/51


Sealing Your Requirements - contd

3) Organize Metadata By Defined Data andby Beneficiary Interest

o Metadata which answers 5 questions about CRM data o Subsets of above metadata based upon who

will need it and for what purpose

4) Develop Metamodel as needed5) Populate Metamodel

S li Y


47/51


Sealing Your Requirements - contd

4) Assure Metadata Accessibility within BIarchitecture


48/51


Resulting Metadata

o Will address the data within the initial BIscope

oWill have an associated metamodel that isflexible enough to cover additional databoth within and outside of the BIenvironment

o Will be as accessible as the BI data itself


49/51

2002 Database Design Solutions, Inc.40 Morristown Road, Suite 2BBernardsville, NJ 07924

www.dbdsolutions.com

Conclusion

Metadata andBI should live

together


50/51


BI Without Metadata. o Should be against your religiono Will make your life miserable (eventually)o Does not justify the time and expense involved in

setting up a BI environment


51/51

Questions?o Recent Book:

Metadata Solutions: Using Metamodels, Repositories, XML,and Enterprise Portals to Achieve Information on Demand (2001, Addison Wesley)

o Visit our web site: www.dbdsolutions.com Publications Discussion Group

o Send me email [email protected]