- Shopping Bag ( 0 items )
Other sellers (Paperback)
-
All (21) from $11.03
-
New (8) from $36.1
-
Used (13) from $11.03
More About This Textbook
Overview
The definitive best-practices guide to enterprise data-management strategy.
You can no longer manage enterprise data "piecemeal." To maximize the business value of your data assets, you must define a coherent, enterprise-wide data strategy that reflects all the ways you capture, store, manage, and use information.
In this book, three renowned data management experts walk you through creating the optimal data strategy for your organization. Using their proven techniques, you can reduce hardware and maintenance costs, and rein in out-of-control data spending. You can build new systems with less risk, higher quality, and improve data access. Best of all, you can learn how to integrate new applications that support your key business objectives.
Drawing on real enterprise case studies and proven best practices, the author team covers everything from goal-setting through managing security and performance. You'll learn how to:
Product Details
Related Subjects
Meet the Author
Sid Adelman is a principal in Sid Adelman & Associates, an organization specializing in planning and implementing data warehouses, in data warehouse and BI assessments, and in establishing effective data architectures and strategies. He is a regular speaker at the Data Warehouse Institute and IBM's DB2 and Data Warehouse Conference. Sid also speaks often at DAMA conferences. He chairs the "Ask the Experts" column on http://www.dmreview.com.
Sid is a founding member of the Business Intelligence Alliance. Its members include Colin White, Herb Edelstein, Larry English, David Foote, Douglas Hackney, Pieter Mimno, Neil Raden, and David Marco. Sid is also a frequent contributor to journals that focus on data warehouse and data-related topics. He co-authored Data Warehouse Project Management with Larissa Moss. He is the primary author of Impossible Data Warehouse Situations with Solutions from the Experts.
Sid can be reached at sidadelman@aol.com. His web site is http://www.sidadelman.com.
Larissa Moss is president of Method Focus Inc., a corporation specializing in enterprise information management. She frequently lectures at data warehouse and data quality conferences worldwide on the topics of data warehousing, business intelligence, and other enterprise architecture and data strategy topics, such as data integration, data modeling, data quality, and metadata. Larissa is a senior consultant of the Cutter Consortium and a member of Friends of NCR-Teradata and the IBM Gold Group. Her present and past associations also include membership in DAMA, part-time faculty member at the Extended University of California Polytechnic University Pomona, associate of the Relational Institute and the Codd & Date Consulting Group, and lecturer for TDWI, DCI, MIS Training Institute, and PESG.
Larissa has authored and co-authored numerous books, white papers, and articles on business intelligence, project management, information asset management, development methodologies, data quality, and organizational realignments. She can be reached at methodfocus@earthlink.net. Her web-site is http://www.methodfocus.com.
Majid Abai is President of Seena Technologies, a Santa Monica, California consultancy dedicated to delivery of holistic data and enterprise solutions to various organizations. Majid's two decades of IT experience have been primarily focused on solution architecture, data strategies, and business intelligence systems for organizations facing challenges with the management of massive amounts of data. Majid has developed and teaches a class in Business Intelligence at the University of California, Los Angeles (UCLA) and several other seminars and lectures for national and international corporations. He can be reached at majid@seenatech.com. Seena Technologies website is http://www.seenatech.com.
© Copyright Pearson Education. All rights reserved.
Read an Excerpt
Foreword
Data strategy is one of the most ubiquitous and misunderstood topics in the information technology (IT) industry. Most corporations' data strategy and IT infrastructure were not planned, but grew out of "stovepipe" applications over time with little to no regard for the goals and objectives of the enterprise. This stovepipe approach has produced the highly convoluted and inflexible IT architectures so prevalent in corporations today. This architecture—or rather the lack thereof—creates a significant stumbling block because it is exceedingly time consuming and costly to modify existing systems. In fact, I have seen situations in which a chief marketing officer could not initiate a desired marketing campaign because the opportunity to do so would have grown stale by the time the systems were modified to implement the new campaign.
Besides inflexibility, the lack of enterprise IT planning has lead to epidemic levels of data redundancy. In my experience, most major corporations and large government organizations have three- to four-fold "needless data redundancy"—data that exists for no other reason than failure to properly plan and implement. This issue has become so pressing that it has entered into the chief executive officer (CEO)'s key corporate objectives. I have personally witnessed several CEOs declare that their organization must simplify its IT portfolio, so that redundant data and applications can be removed.
Many organizations target enterprise data strategy as one of the key initiatives to reduce data redundancy, simplify IT portfolios, and ease the strain on the architectures of applications. Through metadata management, an enterprise data strategy identifies how data should be constructed, what data exists, and what the meaning of that data is. This helps organizations address data redundancy by showing when a proposed new system will replicate existing applications. This is a critical aspect of data strategy because many companies want to consolidate existing redundant applications, but processes are not in place to prevent new redundancy from entering the IT environment. Thus, an effective enterprise data strategy can save organizations that currently operate as the proverbial sinking ships whose crews are bailing water, but cannot plug the leaks. A sound enterprise data strategy not only "bails water" by affording IT staff the means and methods for reducing existing redundant data, but it can "plug the leaks" by ensuring that new redundancies stop flowing into the organization.
Sid Adelman, Larissa Moss, and Majid Abai's book represents an outstanding achievement in defining the key activities for implementing a successful enterprise data strategy. Their real-world experience assisting companies shines throughout the book and makes it a must read for any IT professional.
—David Marco, President of EWSolutions
© Copyright Pearson Education. All rights reserved.
Table of Contents
Acknowledgments.
About the Authors.
Foreword.
1. Introduction.
Current Status in Contemporary Organizations.
Why a Data strategy Is Needed.
Value of Data as an Organizational Asset.
Vision and Goals of the Enterprise.
Support of the IT Strategy.
Components of a Data Strategy.
Data Integration.
Data Quality.
Metadata.
Data Modeling.
Organizational Roles and Responsibilities.
Performance and Measurement.
Security and Privacy.
DBMS Selection.
Business Intelligence.
Unstructured Data.
Business Value of Data and ROI.
How Will You Develop and Implement a Data Strategy?
Data Environment Assessment.
References.
2. Data Integration.
Ineffective “Silver-Bullet” Technology Solutions.
Enterprise Resource Planning (ERP).
Data Warehousing (DW).
Customer Relationship Management (CRM).
Enterprise Application Integration (EAI).
Gaining Management Support.
Business Case for Data Integration.
Integrating Business Data.
Know Your Business Entities.
Mergers and Acquisitions.
Data Redundancy.
Data Lineage.
Multiple DBMSs and Their Impact.
Deciding What Data Should Be Integrated.
Data Integration Prioritization.
Risks of Data Integration.
Consolidation and Federation.
Data Consolidation.
Data Federation.
Data Integration Strategy Capability Maturity Model.
Getting Started.
Conclusion.
References.
3. Data Quality.
Current State of Data Quality.
Recognizing Dirty Data.
Data Quality Rules.
Business Entity Rules.
Business Attribute Rules.
Data Dependency Rules.
Data Validity Rules.
Data Quality Improvement Practices.
Data Profiling.
Data Cleansing.
Data Defect Prevention.
Enterprise-Wide Data Quality Disciplines.
Data Quality Maturity Levels.
Standards and Guidelines.
Development Methodology.
Data Naming and Abbreviations.
Metadata.
Data Modeling.
Data Quality.
Testing.
Reconciliation.
Security.
Data Quality Metrics.
Enterprise Architecture.
Data Quality Improvement Process.
Business Sponsorship.
Business Responsibility for Data Quality.
Conclusion.
References.
4. Metadata.
Why Metadata Is Critical to the Business.
Metadata as the Keystone.
Management Support for Metadata.
Starting a Metadata Management Initiative.
Metadata Categories.
Business Metadata.
Technical Metadata.
Process Metadata.
Usage Metadata.
Metadata Sources.
Metadata Repository.
Buying a Metadata Repository Product.
Building a Metadata Repository.
Centralized Metadata Repository.
Distributed Metadata Repository.
XML-Enabled Metadata Repository.
Developing a Metadata Repository.
Justification.
Planning.
Analysis.
Design.
Construction.
Deployment.
Managed Metadata Environment.
Metadata Sourcing.
Metadata Integration.
Metadata Management.
Metadata Marts.
Metadata Delivery.
Communicating and Selling Metadata.
Conclusion.
References.
5. Data Modeling.
Origins of Data Modeling.
Significance of Data Modeling.
Logical Data Modeling Concepts.
Process-Independence.
Business-Focused Data Analysis.
Data Integration (Single Version of Truth).
Data Quality.
Enterprise Logical Data Model.
Big-Bang Versus Incremental.
Top-Down versus Bottom-Up.
Physical Data Modeling Concepts.
Process-Dependence.
Database Design.
Physical Data Modeling Techniques.
Denormalization.
Surrogate Keys.
Indexing.
Partitioning.
Database Views.
Dimensionality.
Star Schema.
Snowflake.
Starflake.
Factors that Influence the Physical Data Model.
Guideline 1 :High Degree of Normalization for Robustness.
Guideline 2 :Denormalization for Short-Term Solutions.
Guideline 3 :Usage of Views on Powerful Servers.
Guideline 4 :Usage of Views on Powerful RDBMS Software.
Guideline 5 :Cultural Influence on Database Design.
Guideline 6 :Modeling Expertise Affects Database Design.
Guideline 7 :User-Friendly Structures.
Guideline 8 :Metric Facts Determine Database Design.
Guideline 9 :When to Mimic Source Database Design.
Conclusion.
References.
6. Organizational Roles and Responsibilities.
Building the Teams Who Create and Maintain the Strategy.
Resistance to Change.
Existing Organization.
Resistance to Standards.
“Reasons” for Resistance.
Optimal Organizational Structures.
Distributed Organizations.
Outsourced Personnel.
Training.
Who Should Attend.
Mindset.
Choice of Class.
Timing.
Roles and Responsibilities.
Data Strategist.
Database Administrator.
Data Administrator.
Metadata Administrator.
Data Quality Steward.
Consultants and Contractors.
Security Officer.
Sharing Data.
Strategic Data Architect.
Technical Services.
Data Ownership.
Domains.
Security and Privacy.
Availability Requirements.
Timeliness and Periodicity Requirements.
Performance Requirements.
Data Quality Requirements.
Business Rules.
Information Stewardship.
Steward Deliverables.
Key Skills and Competencies.
Worst Practices.
Agenda for Weekly Data Strategy Team Meeting.
Conclusion.
7. Performance.
Performance Requirements.
Service Level Agreements.
Response Time.
Capacity Planning: Performance Modeling.
Capacity Planning: Benchmarks.
Why Pursue a Benchmark?
Benchmark Team.
Benefits of a Good Benchmark: Goals and Objectives.
Problems with “Standard” Benchmarks.
The Cost of Running a Benchmark.
Identifying and Securing Data.
Establishing Benchmark Criteria and Methodology.
Evaluating and Measuring Results.
Verifying and Reconciling Results.
Communicating Results Effectively.
Application Packages: Enterprise Resource Planning (ERPs).
Designing, Coding, and Implementing.
Designing.
Coding.
Implementation.
Design Reviews.
Setting User Expectations.
Monitoring (Measurement).
Conformance to Measures of Success191
Types of Metrics191
Responsibility for Measurement.
Means to Measure.
Use of Measurements.
Return on Investment (ROI).
Reporting Results to Management.
Tuning.
Tuning Options.
Reporting Performance Results.
Selling Management on Performance.
Case Studies.
Performance Tasks.
Conclusion.
References.
8. Security and Privacy of Data.
Data Identification for Security and Privacy.
User Role.
Roles and Responsibilities.
Security Officer.
Data Owner.
System Administrator.
Regulatory Compliance.
Auditing Procedures.
Security Audits.
External Users of Your Data.
Design Solutions.
Database Controls.
Security Databases.
Test and Production Data.
Data Encryption.
Standards for Data Usage.
Impact of the Data Warehouse.
Vendor Issues.
Software.
External Data.
Communicating and Selling Security.
Security and Privacy Indoctrination.
Monitoring Employees.
Training.
Communication.
Best Practices and Worst Practices.
Identify Your Own Sensitive Data Exercise.
Conclusion.
9. DBMS Selection.
Existing Environment.
Capabilities and Functions.
DBMS Choices.
Why Standardize the DBMS?
Integration Problems.
Greater Staff Expense.
Software Expense.
Total Cost of Ownership.
Hardware.
Network Usage.
DBMS.
Consultants and Contractors.
Internal Staff.
Help Desk Support.
Operations and System Administration.
IT Training.
Application Packages and ERPs.
Criteria for Selection.
Selection Process.
Reference Checking.
Alternatives to Reference Checking.
Selecting and Gathering References.
Desired Types of References.
The Process of Reference Checking.
Questions to Ask.
RFPs for DBMSs.
RFP Best Practices.
Response Format.
Evaluating Vendors.
Dealing with the Vendor.
Performance.
Vendor’s Level of Service.
Early Code.
Rules of Engagement.
Set the Agenda for Meetings and Presentations.
Professional Employee Information.
Financial Information.
Selection Matrix—–Categorize Capabilities and Functions.
Exercise–How Well Are You Using Your DBMS?255
Conclusion.
References.
10. Business Intelligence.
What Is Business Intelligence?
A Brief History.
Importance of BI.
BI Components.
Data Warehouse.
Metadata Repository.
Data Transformation and Cleansing.
OLAP and Analytics.
Data Presentation and Visualization.
Important BI Tools and Processes.
Data Mining.
Rule-Based Analytics.
Balanced Scorecard.
Digital Dashboard.
Emerging Trends and Technologies.
Mining Structured and Unstructured Data.
Radio Frequency Identification.
BI Myths and Pitfalls.
Conclusion.
References.
11. Strategies for Managing Unstructured Data.
What Is Unstructured Data?
A Brief History.
Why Now?
Current State of Unstructured Data in Organizations.
A Unified Content Strategy for the Organization.
Definition of a Unified Content Strategy.
Storage and Administration.
Content Reusability.
Search and Delivery.
Combining Structured and Unstructured Data.
Emerging Technologies.
Digital Asset Management Software.
Digital Rights Management Software.
Electronic Medical Records.
Conclusion.
References.
12. Business Value of Data and ROI.
The Business Value of Data.
Companies that Sell Customer Data.
Internal Information Gathered About Customers.
Call Center Data.
Click-Stream Data.
Demographics.
Channel Preferences.
Direct Retailers.
Loyalty Cards.
Travel Data.
Align Data with Strategic Goals.
ROI Process.
The Cost of Developing a Data Strategy.
Data Warehouse.
Hardware.
Software.
Personnel Costs.
Training.
Operations and System Administration.
Total Cost of Ownership.
Benefits of a Data Strategy.
The Data Warehouse.
Estimating Tangible Benefits.
Estimating Intangible Benefits.
Post-Implementation Benefits Measurement.
Conclusion.
Reference.
Appendix A: ROI Calculation Process, Cost Template, and Intangible Benefits Template.
Cost of Capital.
Risk.
ROI Example.
Net Present Value.
Internal Rate of Return.
Payback Period.
Cost Calculation Template.
Intangible Benefits Calculation Template.
Reference.
Appendix B: Resources.
Publications.
Websites.
Index.
Preface
Data strategy is one of the most ubiquitous and misunderstood topics in the information technology (IT) industry. Most corporations' data strategy and IT infrastructure were not planned, but grew out of "stovepipe" applications over time with little to no regard for the goals and objectives of the enterprise. This stovepipe approach has produced the highly convoluted and inflexible IT architectures so prevalent in corporations today. This architecture—or rather the lack thereof—creates a significant stumbling block because it is exceedingly time consuming and costly to modify existing systems. In fact, I have seen situations in which a chief marketing officer could not initiate a desired marketing campaign because the opportunity to do so would have grown stale by the time the systems were modified to implement the new campaign.
Besides inflexibility, the lack of enterprise IT planning has lead to epidemic levels of data redundancy. In my experience, most major corporations and large government organizations have three- to four-fold "needless data redundancy"—data that exists for no other reason than failure to properly plan and implement. This issue has become so pressing that it has entered into the chief executive officer (CEO)'s key corporate objectives. I have personally witnessed several CEOs declare that their organization must simplify its IT portfolio, so that redundant data and applications can be removed.
Many organizations target enterprise data strategy as one of the key initiatives to reduce data redundancy, simplify IT portfolios, and ease the strain on the architectures of applications. Through metadata management, an enterprise data strategy identifies how data should be constructed, what data exists, and what the meaning of that data is. This helps organizations address data redundancy by showing when a proposed new system will replicate existing applications. This is a critical aspect of data strategy because many companies want to consolidate existing redundant applications, but processes are not in place to prevent new redundancy from entering the IT environment. Thus, an effective enterprise data strategy can save organizations that currently operate as the proverbial sinking ships whose crews are bailing water, but cannot plug the leaks. A sound enterprise data strategy not only "bails water" by affording IT staff the means and methods for reducing existing redundant data, but it can "plug the leaks" by ensuring that new redundancies stop flowing into the organization.
Sid Adelman, Larissa Moss, and Majid Abai's book represents an outstanding achievement in defining the key activities for implementing a successful enterprise data strategy. Their real-world experience assisting companies shines throughout the book and makes it a must read for any IT professional.
—David Marco, President of EWSolutions
© Copyright Pearson Education. All rights reserved.