Академический Документы
Профессиональный Документы
Культура Документы
GUIDE
DATA MANAGEMENT
CONTEXT DIAGRAM
BUSSINESS AND IT SHARING
Data management is a
shared responsibility
between data
Business data ownership
management
is the concerned with
professionals within IT
accountability for
and the business data
business responsibilities
owners representing the
in data management
interests of data
producers and
information consumers
Integration -
Insight - cannot
Discovery - cannot
extract value
cannot find the manipulate and
and knowledge
right information combine
from information
information
Management
Dissemination cannot manage
- cannot and control
consume information
information volumes and
growth
DATA MANAGEMENT PROBLEM
Application
Managing
Recoveries / Vendor Power
Storage
Backup Management Management
Equipment
Retention
Archiving and
Storage Managing Managing
Archive
Provisioning Complexity Costs
Management
Proper
Backup
Capacity Managing
Administration
Forecasting Storage
and
and Storage Growth
Management
Reporting
DATA MANAGEMENT CHALLENGE
Explosive Data Growth
Value and volume of data is overwhelming
More data is see as critical
Annual rate of 50+% percent
Compliance Requirements
Compliance with stringent regulatory requirements and audit
procedures
Fragmented Storage Environment
Lack of enterprise-wide hardware and software data storage strategy
and discipline
Budgets
Frozen or being cut
THE STRATEGIC GOALS OF THE DATA
MANAGEMENT FUNCTION
To understand the information needs of the enterprise
and all its stakeholders.
41
Other Data Management-Related Frameworks
COBIT is concerned with IT governance and
controls:
IT must implement internal controls around how it
operates
The systems IT delivers to the business and the
underlying business processes these systems actualise
must be controlled these are controls external to IT
To govern IT effectively, COBIT defines the activities and
risks within IT that need to be managed
COBIT has a process relating to data
management
Neither TOGAF nor COBIT are concerned with
detailed data management design and
implementation
41
DAMA BOK TOGAF - COBIT
DAMA BOK TOGAF - COBIT
TOGAF and Data Management
Phase C1 (subset
Phase A:
of Phase C) relates
Architecture
Vision
to defining a data
Phase H:
Architecture
Phase B: architecture
Business
Change
Architecture
Management
Phase C1:
Data
Architecture
Phase G: Phase C:
Requirements Information
Implementation
Management Systems
Governance
Architecture
Phase C2:
Solutions and
Application
Phase F: Phase D: Architecture
Migration Technology
Planning Architecture
Phase E:
Opportunities
and Solutions
March 8, 2010 44
TOGAF Phase C1: Information
Systems Architectures
Data Architecture - Objectves
Purpose is to define the major types and sources of data
necessary to support the business, in a way that is:
Understandable by stakeholders
Complete and consistent
Stable
Define the data enttes relevant to the enterprise
Not concerned with design of logical or physical storage
systems or databases
45
TOGAF Phase C1: Information
Systems Architectures
45
TOGAF Phase C1: Informaton Systems Architectures - Data Architecture -
Approach - Key Consideratons for Data Architecture
Data Management
Important to understand and address data management issues
Structured and comprehensive approach to data management enables the
effectve use of data to capitalise on its compettve advantages
Clear definiton of which applicaton components in the landscape will serve
as the system of record or reference for enterprise master data
Will there be an enterprise-wide standard that all applicaton components,
including software packages, need to adopt
Understand how data enttes are utlised by business functons, processes,
and services
Understand how and where enterprise data enttes are created, stored,
transported, and reported
Level and complexity of data transformatons required to support the
informaton exchange needs between applicatons
Requirement for software in supportng data integraton with external
organisatons
47
TOGAF Phase C1: Informaton Systems Architectures - Data Architecture -
Approach - Key Consideratons for Data Architecture
Data Migraton
Identfy data migraton requirements and also provide
indicators as to the level of transformaton for new/changed
applicatons
Ensure target applicaton has quality data when it is populated
Ensure enterprise-wide common data definiton is established
to support the transformaton
48
TOGAF Phase C1: Informaton Systems Architectures - Data Architecture -
Approach - Key Consideratons for Data Architecture
Data Governance
Ensures that the organisaton has the necessary dimensions in
place to enable the data transformaton
Structure ensures the organisaton has the necessary
structure and the standards bodies to manage data entty
aspects of the transformaton
Management System - ensures the organisaton has the
necessary management system and data-related programs to
manage the governance aspects of data enttes throughout its
lifecycle
People - addresses what data-related skills and roles the
organisaton requires for the transformaton
49
TOGAF Phase C1: Information Systems Architectures
- Data Architecture - Outputs
Refined and updated versions of the Architecture Vision phase deliverables
Statement of Architecture Work
Validated data principles, business goals, and business drivers
Draft Architecture Definition Document
Baseline Data Architecture
Target Data Architecture
Business data model
Logical data model
Data management process models
Data Entity/Business Function matrix
Views corresponding to the selected viewpoints addressing key
stakeholder concerns
Draft Architecture Requirements Specification
Gap analysis results
Data interoperability requirements
Relevant technical requirements
Constraints on the Technology Architecture about to be designed 50