Professional Documents
Culture Documents
THE DMBOK
DAMA BRASIL
SEPT 2014
DONNA BURBANK
VP, INFORMATION MANAGEMENT SERVICES
DONNA.BURBANK@ENTERPRISEARCHITECTS.COM
TWITTER: @DONNABURBANK
Twitter: @donnaburbank
3 | MODULE 01 COURSE INTRODUCTION | ENTERPRISE ARCHITEC TS 2014
And When Im Not Doing Data Management
Po de Acar, Rio de Janeiro
DATA DATA
DAMA
QUALITY DEVELOPMENT
MANAGEMENT
Framework DATABASE
Functions META DATA
MANAGEMENT
OPERATIONS
MANAGEMENT
DATA
GOVERNANCE
DATA WAREHOUSE
& BUSINESS REFERENCE &
INTELLIGENCE MASTER DATA
MANAGEMENT MANAGEMENT
DMBoK
Specification
Analysis
Measurement
DATA
ARCHITECTURE
Analysis
Data modelling
Database Design
Functions
Improvement MANAGEMENT Implementation
Architecture
Acquisition
Integration DATA Recovery
Control DATABASE
META DATA GOVERNANCE Tuning
Delivery OPERATIONS Retention
MANAGEMENT
Strategy MANAGEMENT Purging
Organisation & Roles
Policies & Standards
Issues
DOCUMENT & CONTENT Valuation DATA SECURITY
MANAGEMENT MANAGEMENT
Acquisition & Storage Standards
Backup & Recovery DATA Classifications
Content Management WAREHOUSE REFERENCE & Administration
Retrieval & BUSINESS MASTER DATA Authentication
Retention INTELLIGENCE MANAGEMENT Auditing
MANAGEMENT External Codes
Architecture Internal Codes
Implementation Customer Data
Training & Support Product Data
Monitoring & Tuning Dimension Management
Environmental
Critical Success Factors
Reporting Structures
Management Metrics
Values, Beliefs, Expectations
Elements
Attitudes, Styles, Preferences
Rituals, Symbols, Heritage
TECHNOLOGY ACTIVITIES
Phases, Tasks, Steps
Tool Categories Dependencies
Standards and Protocols Sequence and Flow
Section Criteria Use Case Scenarios
Learning Curves Trigger Events
GOALS &
PRINCIPLES
Vision and Mission
Business Benefits
Strategic Goals
Specific Objectives
Guiding Principles
PRACTICES
DELIVERABLES
& TECHNIQUES Inputs and Outputs
Information
Recognized Best Practices
Documents
Common Approaches
Databases
Alternative Techniques
Other Resources
ROLES &
RESPONSIBILITIES
Individual Roles
Organizational Roles
Business and IT Roles
Qualifications and Skills
INFORMATION MANAGEMENT
READINESS ASSESSMENT
Data Quality can only be considered within the Deriving Data Quality Requirements
context of the intended use of the data - i.e.
fitness for purpose Identify key data components associated with
business policies
The required level of Data Quality for a
particular data component is therefore Determine how identified data assertions affect
dependent on the collection of business the business
processes that interact with the component Evaluate how data errors are categorized within
These in turn are driven by the underlying a set of data quality dimensions
business policies, which are ultimately the Specify the business rules that measure the
source of many Data Quality requirements occurrence of data errors
Determining fitness for purpose requires Provide a means for implementing measurement
reporting on meaningful metrics associated processes that assess conformance to those
with well-defined data quality dimensions. business rules
Data quality can only be considered within the context of the intended use of the data
Data needs to be fit for purpose
Data quality needs to be assessed on that basis
Data quality can only be considered within the context of the intended use of the data
(data needs to be fit for purpose and data quality needs to be assessed on that basis)
Dimensions
itself or its counterpart in another data correctly describes the "real
data set or database. world" object or event being
described. The degree to which data
Timeliness The degree to which ACCURACY TIMELINESS
correctly describes the "real world"
data represent reality from the object or event being described.
required point in time. The time the
real world event being recorded Consistency The absence of
occurred. difference, when comparing two or
VALIDITY
more representations of a thing
against a definition. The absence of
difference, when comparing two or
more representations of a thing
against a definition
Source: DAMA UK
ARCHIVE
CREATE & MAINTAIN
PLAN SPECIFY ENABLE & PURGE
ACQUIRE & USE
RETRIEVE
(SOURCE DAMA)
BUSINESS RULES
Using a preliminary set of business rules
CONFORMANCE
Without common metrics, its difficult to define how good is data quality
ACCURACY INTEGRITY
CREDIBILITY DQI-B01
Example
TIMELINESS
Measurement
Framework
DATA QUALITY CURRENCY
PUNCTUALITY DQI-P01
COVERAGE
UNIQUENESS DQI-U01
The Data Quality Indicators and the business A typical Data Quality SLA should specify:
rules upon which they are built are used to The data elements covered by the agreement
measure and monitor data quality
The business impacts associated with data flaws
However, in order to ensure timely resolution
when thresholds are breached or non- The data quality dimensions associated with each data
element
conformant records are identified its important
to establish a Data Quality Service Level The expectations for quality for each data element for
Agreement (SLA) each of the identified dimensions in each application or
system in the value chain
This will set out business expectations for
response and remediation and provide a The methods for measuring against those expectations
starting point for more proactive data quality The acceptability threshold for each measurement
improvement
The individual(s) to be notified in case the acceptability
threshold is not met
STANDARDISATION
quiick
foxjumps
The quiick fox overthe
jumpsover the the
the lazy
lazydog
dog
STANDARDISATION SUBSTITUTION
brown
The quick fox jumps over the lazy dog
Few, if any, measurements Some basic measurements A comprehensive and A comprehensive and
There is a standard set of
of data quality are made on of validity and consistent set of business consistent set of business
business rules defined for
a routine basis and there is completeness are applied rules and data quality rules and data quality
key datasets and these are
no clear understanding to certain datasets, but indicators covering all indicators covering all
applied whenever data is
about the current level of these arent always applied datasets is stored in a local datasets is stored centrally
received.
data quality. consistently. repository. in a shared repository.
No feedback is supplied Feedback on data quality Data Stewards are supplied Data Stewards are supplied
with prompt feedback
regarding specific issues or tends to be handled on an with prompt feedback with prompt feedback
when exceptions occur, on
the general level of data ad-hoc basis with no when business rules arent when exceptions occur and
a regular schedule and on a
quality. routine reporting. satisfied. on a regular schedule.
self-service basis.
Seven DQ Mistakes
1 2 3 4
Treating data quality Fixing data in a data
Failing to consider the Confusing validity with management as a one-time warehouse rather than at
intended use of the data accuracy activity source
Data has to be fit for Validity is only the first step Quality data can only be Clean data for reporting
purpose, no more, no less towards accuracy ensured through a doesnt solve the operational
continuous cycle issues of poor DQ
5 6 7
Applying software quality Believing that good quality
Blaming systems for bad
principles to data quality data is the end goal
data
Data is infinitely more Deriving genuine value
People and processes lie at
volatile than SW and through information
the heart of most DQ
demands a different exploitation is the ultimate
problems
approach aim