Data-Ed Online: "Building a Solid Foundation: Data/Information Architecture"

Welcome!
TITLE

Building a Solid Foundation:
Data/Information Architecture

Date: February 14, 2012
Time: 2:00 PM ET
Presenter: Dr. Peter Aiken

PRODUCED BY CLASSIFICATION DATA SLIDE
DATA BLUEPRINT 10124-C W. BROAD ST, GLEN ALLEN, VA 23060 EDUCATION 2/14/2012 1
© Copyright this and previous years by Data Blueprint - all rights reserved!

TITLE
Meet Your Presenter: Dr. Peter Aiken
• Internationally recognized thought-leader in
the data management field with more than 30
years of experience
• Recipient of the 2010 International Stevens
Award
• Founding Director of Data Blueprint
(http://datablueprint.com)
• Associate Professor of Information Systems
at Virginia Commonwealth University
(http://vcu.edu)

• President of DAMA International (http://dama.org)
• DoD Computer Scientist, Reverse Engineering Program Manager/
Office of the Chief Information Officer
• Visiting Scientist, Software Engineering Institute/Carnegie Mellon
University
• 7 books and dozens of articles
• Experienced w/ 500+ data management practices in 20 countries

Building a Solid
Foundation:
Data/Information
Architecture

Dr. Peter Aiken: Building a Solid Foundation – Data/Information
DATA BLUEPRINT 10124-C W. BROAD ST, GLEN ALLEN, VA 23060 EDUCATION 2/14/2012

TITLE

Building a Solid Foundation:
Data/Information Architecture
All organizations have data architectures. The question is:
How effectively do they use them? This presentation
provides a clear and concise understanding of what is
meant by the term data architecture and the requirement
that data and information architectures must be
simultaneously managed. More importantly, organizations
must understand what it means to use data architecture to
support the implementation of organizational strategy.
Participants will understand the requirements for an
iterative, incremental approach to data architecture
reengineering, the complimentary role of the Zachman
Framework, and the ability to articulate the business value
of data architecture projects and components.

TITLE
Outline
1. Data Management Overview
2. What is Data/Information Architecture?
3. Why is Data/Information Architecture
Important?
4. Data/Information Architecture
Frameworks
5. Data/Information Architecture Building
Blocks
6. Guiding Principles & Best Practices
7. Considerations for Improving Data
Architecture Utility within your
Organization
8. Take Aways, References & Q&A


TITLE
The DAMA Guide to the Data Management Body of Knowledge
Published by DAMA
International
• The professional
association for Data
Managers (40
chapters worldwide)
DMBoK organized
around
• Primary data
management
functions focused
around data delivery
to the organization
• Organized around
several
environmental
elements

Data Management Functions

TITLE
The DAMA Guide to the Data Management Body of Knowledge

Amazon:
http://
www.amazon.com/
DAMA-Guide-
Management-
Knowledge-DAMA-
DMBOK/dp/
0977140083
Or enter the terms
"dama dm bok" at the
Amazon search
engine

Environmental Elements

TITLE
What is the CDMP?
• Certified Data Management
Professional
• DAMA International and ICCP
• Membership in a distinct group made
up of your fellow professionals
• Recognition for your specialized
knowledge in a choice of 17 specialty
areas
• Series of 3 exams
• For more information, please visit:
– http://www.dama.org/i4a/pages/
index.cfm?pageid=3399
– http://iccp.org/certification/
designations/cdmp


TITLE
Data Management


TITLE
Data Management
Manage data coherently.

Data Program
Coordination
Share data across boundaries.
Organizational
Data Integration

Data Stewardship Data Development

Assign responsibilities for data.
Engineer data delivery systems.

Data Support
Operations

Maintain data availability.


TITLE
Outline
Important?
Frameworks
Blocks
Organization


TITLE
Data Architecture Management

from The DAMA Guide to the Data Management Body of Knowledge © 2009 by DAMA International


Niccolò Machiavelli (1469-1527)
TITLE

He who doesn’t lay
his foundations before
hand, may by great
abilities do so afterward, although with
great trouble to the architect and
danger to the building.

TITLE
Polling Question #1
Most organizations do not formally manage any type of
architectures. I have surveyed 500 different organizations
around the world and found that not all of them have
architectures in place. What do you think is the
percentage of organizations worldwide with data
architectures?
a) 80%
b) 60%
c) 40%
d) Less than 10%


TITLE
Typically Managed Architectures
• Process Architecture
– Arrangement of inputs -> transformations = value -> outputs
– Typical elements: Functions, activities, workflow, events, cycles, products,
procedures
• Systems Architecture
– Applications, software components, interfaces, projects
• Business Architecture
– Goals, strategies, roles, organizational structure, location(s)
• Security Architecture
– Arrangement of security controls relation to IT Architecture
• Technical Architecture/Tarchitecture
– Relation of software capabilities/technology stack
– Structure of the technology infrastructure of an enterprise, solution or system
– Typical elements: Networks, hardware, software platforms, standards/protocols
• Data/Information Architecture
– Arrangement of data assets supporting organizational strategy
– Typical elements: specifications expressed as entities, relationships, attributes,
definitions, values, vocabularies


Architecture
TITLE

Architecture is both the process and product
of planning, designing and constructing
space that reflects functional, social, and
aesthetic considerations.
A wider definition may comprise all design
activity from the macro-level (urban design,
landscape architecture) to the micro-level
(construction details and furniture).
In fact, architecture today may refer to the
activity of designing any kind of system and
is often used in the IT world.

TITLE
Information Architectures
• … are plans, guiding the transformation of strategic
organizational information needs into specific information
systems development projects
– Source: Internet

• "Information architecture is a foundation discipline
describing the theory, principles, guidelines, standards,
conventions, and factors for managing information as a
resource. It produces drawings, charts, plans, documents,
designs, blueprints, and templates, helping everyone make
efficient, effective, productive and innovative use of all types
of information."
– Source: Information First by Roger & Elaine Evernden, 2003 ISBN 0 7506 5858 4 p.1.

• Defining the data needs of the enterprise and designing the
master blueprints to meet those needs
• Source: DM BoK

Data Architecture – Better Definition
TITLE

• Common vocabulary expressing
integrated requirements ensuring
that data assets are stored,
arranged, managed, and used in
systems in support of
organizational strategy*
• All organizations have *Source: Aiken 2010

information architectures
• Some are better understood and
documented (and therefore
more useful) than others

TITLE
Vocabulary is Important-Tank, Tanks, Tankers, Tanked


TITLE
Outline
Important?
Frameworks
Blocks
Organization


TITLE
Architecture Examples: Good


TITLE
Architecture Examples: Bad


TITLE
Why is Data Architecture Important?
• Poorly understood
– Data architecture asset value is
not well understood
• Inarticulately explained
– Little opportunity to obtain learning and
experience
• Indirectly experienced
– Cost organizations millions each year in
productivity/redundant and siloed efforts
– Example: Poorly thought out software
purchases

TITLE
What Questions Can Architectures Address?
• How and why do the Human resources
components interact? Policies,
directives,
• Where do they go? and rules
• When are they needed?
• Why and how will the
changes be Communication facilities
implemented?
• What should be Computers
managed organization-
wide and what should be Management
managed locally? responsibilities

• What standards should
be adopted?
Software Data
• What vendors should be
chosen?
• What rules should
govern the decisions?
• What policies should
guide the process?

TITLE
Polling Question #2
The average organization contains information about
customers in more than one place. What do you think is
the average number of places internally in which
organizations keep customer information?

a) 2
b) 9
c) 17
d) 20


TITLE
Who is Joan Smith?


TITLE
Data/Information Architectures Must be Managed Together
,&+-./0102".3%$-'$045$00
.6$"07+$-0+8"."8/.7+%8)

!"#$%%&'$"($)

!"#$%&'($") *+$)

!"#"$% *+,-+./)
!"#"$%
!"#"$%

&"'#$% ()"*+*,$%

1. Each FACT combines with one or more MEANINGS.
– Each specific FACT and MEANING combination is referred to as a DATUM.
2. An INFORMATION is one or more DATA that are returned in response to a
specific REQUEST
3. INTELLIGENCE is INFORMATION associated with its USES.
– INFORMATION REUSE is enabled when one FACT is combined with more than one MEANING.
© Copyright this and previous years by Data Blueprint - all rights reserved! [Built
on
deﬁni1on
by
Dan
Appleton
1983]

TITLE
Outline
Important?
Frameworks
Blocks
Organization


TITLE
Data Architecture Frameworks
• TOGAF
– The open group architectural framework
• ANSI/IEEE 1471-2000 Standard
– Defines specific design artifacts
• FEA
– Federal Enterprise Architecture/OMB
• MODAF
– UK Ministry of Defence
• AGATE • A system of ideas for
– France DGA Architecture Framework guiding analyses
• Industry Models • A means of organizing
– IBM/Teradata/Financial Transactions project data
Inc. • Data integration
• DODAF priorities decision
– US DoD Architecture Framework making framework
• Zachman Framework • A means of assessing
progress

™

Names Names
Where Why
Names
C o m p o s i t e I n t e g r a t i o n s A l i g n m e n t C o m p o s i t e I n t e g r a t i o n s

A A
Executive l
i Products Forecast Sales Material Supply Ntwk General Mgmt Product Cycle New Markets
l
i Scope
g g
Contexts
Product Types Plan Production Product Dist. Ntwk Product Mgmt Market Cycle Revenue Growth

Perspective
Sell Products Voice Comm. Ntwk Engineering Design Planning Cycle Expns Reduction

n Parts Bins
Customers
Take Orders
Train Employees
Data Comm. Ntwk
Manu. Process Ntwk
Manu. Engineering
Accounting
Order Cycle
Employee Cycle
Cust Convenience
Customer Satis. n
m
Territories Assign Territories Finance Maint. Cycle Regulatory Comp.
m Orders
Employees
Develop Markets
Maintain Facilities
Parts Dist. Ntwk
Personnel Dist. Ntwk
Transportation
Distribution
Production Cycle
Sales Cycle
New Capital
Social Contribution
e e.g.
Vehicles
Accounts e.g.
Repair Products
Record Transctns e.g.
etc., etc.
e.g.
Marketing
Sales e.g.
Economic Cycle
Accounting Cycle e.g.
Increased Yield
Increased Quality e
n n
t t
T
List: Inventory Types List: Process Types List: Distribution Types List: Responsibility Types List: Timing Types List: Motivation Types T
r r
a a
n n
s s
Business Mgmt f
o
e.g.: primitive
model:
e.g.: composite model: f
o Business
e.g. e.g. e.g. e.g. e.g. e.g.
Perspective r
m
r
m Concepts
a a
t t
i Business Entity Business Transform Business Location Business Role Business Interval Business End i
o o
n Business Relationship Business Input/Output Business Connection Business Work Product Business Moment Business Means n
s s

Architect e.g. e.g. e.g. e.g. e.g. e.g.
System
Perspective Logic
System Entity System Transform System Location System Role System Interval System End
System Relationship System Input /Output System Connection System Work Product System Moment System Means

Engineer e.g. e.g. e.g. e.g. e.g. e.g. Technology
Perspective Physics
Technology Entity Technology Transform Technology Location Technology Role Technology Interval Technology End
Technology Relationship Technology Input /Output Technology Connection Technology Work Product Technology Moment Technology Means

A A
l l
Technician i
g
e.g. e.g. e.g. e.g. e.g. e.g. i
g Tool
Perspective n
m
n
m
e
Components
e
n n
t t
Tool Entity Tool Transform Tool Location Tool Role Tool Interval Tool End
T Tool Relationship Tool Input /Output Tool Connection Tool Work Product Tool Moment Tool Means T
r
r
a a
n n
Enterprise s
f Inventory Process Distribution Responsibility Timing Motivation s
f Operations
Perspective o
r
Instantiations Instantiations Instantiations Instantiations Instantiations Instantiations o
r Instances
m m
a a
t t
The i
o
i
o The
Enterprise n
s
n
s Enterprise
PRODUCED BY m p o s i t e
C o I n t e g r a t i o n s A l i g n m e n t CLASSIFICATIONs i t e DATEe g r a t i o n s SLIDE
C o m p o I n t
*Horizontal integration lines

DATA BLUEPRINT 10124-C W. BROAD ST, GLEN ALLEN, VA 23060 EDUCATION
are shown for example purposes
02/06/12 30
only and are not a complete set.
Composite, integrative rela-
tionships connecting every cell
Names horizontally potentially exist.

Data Architectures are Developed in Response to Organizational Needs

satisfy specific organizational needs
Organizational Needs

become instantiated
and integrated into an Data/Information
Architecture

authorizes and
! articulates
!
" !
" !
"
!"#$%&'($")*+,-.&)
"
/.012%.&."-,3

PRODUCED BY CLASSIFICATION DATE SLIDE

TITLE
Outline
Important?
Frameworks
Blocks
Organization


TITLE
Data Architecture Management Building Blocks

√ √ √ √ √ √ √



TITLE
Data Architecture Management Overview



TITLE
Data Architecture Mgmt Goals and Principles
1) To plan with vision and
foresight to provide high
quality data

2) To identify and define
common data requirements

3) To design and implement
structures and plans to meet
the current and long-term
data requirements of the
enterprise


TITLE
Polling Question #3

What percentage of your data handles most of
your information needs?

a) 80%
b) 50%
c) 20%
d) 5%


TITLE
Data Architecture Mgmt Activities
1) Understand enterprise information needs

2) Develop and maintain the enterprise data model
3) Analyze and align with other business models
4) Define and maintain
– Data technology architecture

– Data integration architecture

– Data Warehouse/BI architecture

– Enterprise taxonomies and
namespaces

– Metadata architecture


TITLE
Data Architecture Mgmt Primary Deliverables
• Enterprise Data Model
• Information Value Chain
Analysis
• Data Technology Architecture
• Data Integration/MDM Architecture
• DW/BI Architecture
• Metadata Architecture
• Enterprise Taxonomies and Namespace
• Document Management Architecture
• Metadata


TITLE
Polling Question #4

Who is responsible for the data?

a) Everyone
b) CIO
c) Data Producers
d) Data Stewards


TITLE
Data Architecture Mgmt Roles and Responsibilities
Managers and Executives Participants
• Data Stewards
Consumers
• SMEs
• Data Stewards
• Data Architects • Data Architects
• Data Analysts • Data Analysts & Modelers
• Database Administrators • Other Enterprise Architects
• Software Developers • DM Executives & Managers
• Project Managers • CIO & other Executives
• Data Producers
• Database Administrators
• Knowledge Workers
• Data Model Administrators
Suppliers
• Executives
• Data Stewards
• Data Producers
• Information Consumers


TITLE
Data Architecture Mgmt Technology
• Data Modeling/CASE Tools

• Model Management Tool

• Metadata Repository

• XML Processors/Servers

• Data Discovery/Profiling Tools

• Office Productivity/Collaboration Tools


TITLE
Top 3 Things a Data Architecture Tool Needs to have in 2012
1. True business glossary
– Capturing the language of the business
independent of data structure, independent of
physical form, is the ideal way to properly identify,
classify, and manage disparate information sources
2. Business process and other business models
– These models define the context for information that we
manage. By aligning all information concepts with all
uses of that same concept across all business units and
all business use cases, we can ensure a consistent
definition of that information regardless of which subset of
the attributes we implement in a given application or
technology
3. Web-based collaboration
– This one is really about sharing the metadata with folks
that are not using a modeling tool but have a say in this
knowledge set.
Source: “Top 3 Things a Data Architecture Tool Needs to Have in 2012” by David Dichmann;
http://blogs.sybase.com/dichmann/2012/01/top-3-things-a-data-architecture-tool-needs-to-have-in-2012/

TITLE
Outline
Important?
Frameworks
Blocks
Organization


TITLE
Guiding Principles & Best Practices
1. Data architecture is an integrated set of
specification artifacts (master blueprints) used
to define data requirements, guide data
integration, control data assets, and align data
investments with business strategy
2. Enterprise data architecture is part of the
overall enterprise architecture, along with
process architecture, business architecture,
systems architecture, and technology
architecture
3. Enterprise data architecture includes three
major categories of specifications:
(1) The enterprise data model
(2) Information value chain analysis
(3) Data delivery architecture


TITLE
Guiding Principles & Best Practices, cont’d
4. Enterprise data architecture is
about more than just data. It helps
establish the semantics of an
enterprise, using a common
business vocabulary
5. An enterprise data model is an integrated subject-oriented
data model defining the essential data used across an entire
organization. Build an enterprise data model in layers:
– Subject area overview
– Conceptual views of entities and relationships for each subject area
– More detailed, partially attributed views of these same subject areas
6. Information value chain analysis defines the critical
relationships between data, processes, roles and
organizations, and other enterprise elements


TITLE
Guiding Principles & Best Practices, cont’d

7. Data delivery architecture defines the master blueprint for how data
flows across databases and applications. This ensures data quality
and integrity to support both transactional business processes and
business intelligence reporting and analysis
8. Architectural frameworks like TOGAF and The Zachman
Framework help organize collective thinking about architecture.
This allows different people with different objectives and
perspectives to work together to meet common interests.


TITLE
Outline
Important?
Frameworks
Blocks
Organization


TITLE
Data Architecture is non-trivial
!"#$%&'()*+,-$.+)'")/(,+)-")0'

()*+,-$.+)'-$)$#"-")0'7,+#,$-'
12&'3"*$4!056 • The successful
1(*'"8(90")056 development of a
"80",)$!' organizational data
3(,"%./"9:'7+!(%&:',"9+4,%"96
+,#$)(=$.+)$!'
()0"#,$.+)'
architecture requires a
$%./(."96 degree of information
%++,3()$.+)';(0<6 system development:
!"#$%&%'($)*'+$, – More often spoken about
-$./'%$0$"#(1 ()0",)$!' than sought after, and
+,#$)(=$.+)$!'
!"#"$
()0"#,$.+)' – More often sought after
%&'()#*'#+&*$
,*-+)&*.*/#01
$%./(."96 than achieved.
2($%, • Strategic planning
-$./'%$0$"#(1
%++,3()$.+)';(0<6 without the benefit of a
49",96 +0<",6
data architecture is just
*""32$%>'6 249()"99'' a ritual rain dance.
3+-$()96


TITLE
Largely Ineffective DM Investments
• Approximately, 10%
percent of
organizations
achieve parity and
(potential positive
returns) on their DM
investments.
• Only 30% of DM
investments achieve
tangible returns at
all.
• Seventy percent of
organizations have
very small or no
tangible return on
their DM
investments.

TITLE
Outline
Important?
Frameworks
Blocks
Organization


TITLE
Data Architecture Take Aways
• What is an information architecture?
– A structure of data-based information assets supporting implementation of
organizational strategy (or strategies)
– Most organizations have data assets that are not supportive of strategies
- i.e., information architectures that are not helpful
– The really important question is: how can organizations more effectively
use their information architectures to support strategy implementation?
• What is meant by use of an information architecture?
– Application of data assets towards organizational strategic objectives
– Assessed by the maturity of organizational data management practices
– Results in increased capabilities, dexterity, and self awareness
– Accomplished through use of data-centric development practices
(including taxonomies, stewardship, and repository use)
• How does an organization achieve better use of its information
architecture?
– Continuous re-development; the starting point isn't the beginning
– Information architecture components must typically be reengineered
– Using an iterative, incremental approach, typically focusing on one
component at a time and applying formal transformations

TITLE
References
Websites


TITLE
References, cont’d


TITLE
Questions?

+ =

It’s your turn!
Use the chat feature to submit
your questions to Peter now.


TITLE
Upcoming Events
March Webinar:
Practical Data Modeling
March 13, 2012 @ 2:00 PM ET/11:00 AM PT

April Webinar:
Data Operations Management:
Turning your Challenges Into Success
April 10, 2012 @ 2:00 PM ET/11:00 AM PT

Sign up here:
• www.datablueprint.com/webinar-schedule
• www.Dataversity.net
Brought to you by:


TITLE
Comparative Assessment Results

Data Program Coordination Challenge

Organizational Data Integration Challenge

Data Stewardship

Data Development

Data Support Operations Challenge

0 1 2 3 4 5
Nokia Industry Competition All Respondents

TITLE
Data-Centric Development Flow
• In support of strategy, the
organization develops specific goals/
objectives Strategy
• The goals/objectives drive the
development of specific data/
information assets with an eye to Goals/
organization-wide usage Objectives
• Network/infrastructure components
are developed to support
organization-wide use of data Data/Information
• Development of systems/applications
is derived from the
data/network architecture
Network/Infrastructure
• Advantages of this approach:
– Data/information assets are developed
from an organization-wide perspective
– Systems support organizational data/
information needs and compliment Systems/Applications
organizational process flows
– Data/information reuse is maximized
Original articulation from Doug Bagley @ Walmart

Data-Ed Online: "Building a Solid Foundation: Data/Information Architecture"

More Related Content

What's hot (20)

Similar to Data-Ed Online: "Building a Solid Foundation: Data/Information Architecture" (20)

More from DATAVERSITY (20)

Recently uploaded (20)

Data-Ed Online: "Building a Solid Foundation: Data/Information Architecture"