I need to make something clear to start with – I am a long-time DAMA member and have made good use of the Data Management Body of Knowledge (DMBOK) framework before it became the basis of the current book. My efforts to create and explain data strategies have been organized around the DMBOK topics, so I had high expectations for this guide, given that some of our industry’s best talents have contributed to the book. Thankfully, I was not disappointed. The book is a must-have, and one that I plan to consult frequently as I explain and improve data architectures. In addition, I will be referring to the companion book, The DAMA Dictionary of Data Management, which provides definitions and descriptions of more than 800 data management terms.

The clear audience for this book is the data management professional. Data architects, data modelers, data stewards and data administrators will find this book to be very useful. In addition, students and others who want to enter the ranks of data management professionals will benefit. The book should appeal to a diverse audience beyond the data management professional including: data stewards, managers, business intelligence people, business analysts, educators, researchers and consultants.

The book is clearly written and well illustrated. Editors Mark Mosley, Michael Brackett and Susan Earley have done an exceptional job in producing a book with a consistent style. This is amazing considering the hundreds of people who have contributed their ideas and expertise to this work. A data management hub-and-spoke diagram gives a unifying view to what could be complex and diverse subject. The organization and approach is patterned on other books of knowledge such as the Project Management Book of Knowledge (PMBOK).

Looking Inside

Chapter 1 introduces data and the data management functions. Data is an enterprise asset and provides the basis for information, knowledge, and in the end, fact-based action. The book emphasizes that data has value as an asset only when it is used to produce business value. This part of the data lifecycle includes planning, specifying, enabling, creating and acquiring, maintaining and using, archiving and retrieving, and finally purging. The DAMA-DMBOK Functional Framework consists of data management functions (data governance, data development, etc.) mapped to environmental factors (goals and principles, primary deliverables, technology, etc.).

Chapter 2 explains the functions of data management. The stage is set by describing the definition, missions and goals of data management as well as guiding principles in the conduct of data management. The chapter is organized around the Data Management Context Diagram, which centers on data management functions and includes inputs, suppliers, participants, tools, primary deliverables, consumers, and metrics. Helpful explanations are provided about IT roles and business roles, particularly roles of different types of data stewards.

Chapter 3 describes the concepts, activities and roles needed for successful data governance. In fact, data governance is placed in the center of the DMBOK data functional diagram. Data governance is defined as “the exercise of authority and control (planning, monitoring, and enforcement) over the management of data assets.” Shared decision-making by business and IT management is critical to data governance success. The accountability for data specifications and data quality of assigned business domains is assigned to the data stewards who are in turn organized into groups such as the data stewardship committees and data governance council. Each role and activity is described.

In chapter 4, data architecture is the data management function that supplies the blueprints for managing data assets that satisfy enterprise requirements. I can relate to this topic because I am an enterprise architect with data architecture responsibilities. Deliverables produced by data architects include: the enterprise data model, the information value chain analysis, database architecture, data integration architecture, business intelligence architecture, document control architecture and metadata architecture. The data architect establishes a common vocabulary that defines critical business entities and their data attributes. These deliverables are mapped to other architectural deliverables such as process definitions, application portfolios and technology platforms through information value chain analysis. This chapter provides a very good explanation of the Zachman Enterprise Framework.

Chapter 5 focuses on data development and explains data design and build approaches. This is where data management meets the IT systems development lifecycle (SDLC). Data specification activities support the SDLC activities of plan, analyze, design solution, and detail design while data enabling activities support the SDLC activities of build, test, prepare and deploy. This chapter provides a good high-level overview of data modeling, which includes notations and approaches.

Chapter 6 is about data operations management and describes concepts and activities related to database support and data technology management. In this chapter, support provided by production database administrators comes to the forefront. It is the role of data operations management to protect the integrity of data, manage data availability and optimize database performance. Protecting the integrity of data includes backup and recovery mechanisms as well as data archiving. Optimizing database performance includes performance turning, monitoring, and error reporting. This is a rich chapter which gave me insights into the physical side of data.

Chapter 7 explains the critical tasks and policies needed to secure data in the modern environment. Performing this function well requires a balance between protecting and securing data on the one hand while enabling user access to needed data on the other hand. This must be based on enterprise goals, requirements, and strategies. Data security management produces data security policies, data privacy and confidentiality standards and well-documented classifications. Execution is needed beyond these policies, standards and classifications. This means managing user profiles, passwords, memberships security permissions and access views, and performing data security audits.

Chapter 8, on reference and master data management, addresses the need to provide a 360-degree view of information about critical business entities such as customers. It describes and illustrates the concepts and activities required for the ongoing reconciliation and maintenance of reference and master data. Reference data consists of domain values such as codes with associated descriptions. Master data is data that describes essential business entities such as customers, products, locations, and financial accounts. MDM seeks to build and make available a “golden record” of the most critical shared data. Activities include identifying requirements, developing data models and documentation and improving data quality. The chapter presents numerous reference data examples as well as descriptions of major MDM data subjects. In addition, data architecture for an MDM data hub is presented.

Chapter 9 provides a great overview of data warehousing and business intelligence management, with emphasis on the work of pioneering thought leaders Ralph Kimball and Bill Inmon. I am impressed that this field can be summarized so well in 40 pages. DMBOK defines DW-BIM as “the collection, integration, and presentation of data to knowledge workers for the purposes of business analysis and decision making,” which I find to be very useful. Architectures are presented for both the Inmon Corporate Information Factory approach and the Kimball DW Chess Pieces approach; dimensional modeling (star schema) is illustrated and explained; and BI tool categories and their appropriate users are identified. The performance dashboards work of Wayne Eckerson inspires me to learn more about that subject.

Chapter 10 defines and describes the two related concepts of document and content management. Document management includes the people, processes and technologies used to store, inventory and control electronic and paper documents. Content management is complementary to document management. It includes the people, processes and technologies for organizing, categorizing and structuring access to content so that it can be effectively retrieved and reused. Taxonomies, which are information content architectures, help structure and organize content. The chapter identifies multiple taxonomy groupings, which is helpful. This leads to topics such as the semantic Web and XML-capable content management.

Chapter 11 describes the process of managing metadata, “the card catalog in a managed data environment.” Utilizing metadata can provide benefits including: increasing the strategic value of information, cutting training costs, improving communication and speeding up system development time. Metadata is more than data about data; it can be data about business rules, data mapping, data quality, document content management, data models, process models, system portfolios and service-oriented architectures. This chapter identifies: examples of metadata, roles that support and use metadata, metadata history and metadata strategy. Also included is a good section on metadata standards including references to standards and standards organizations. Plus, there is a nice summary of roles, tools and techniques for managing metadata.

Chapter 12 is on data quality management. DQM goes beyond correcting data to managing data throughout its lifecycle to meet the information needs of data stakeholders both inside and outside the enterprise. DQM is an institutionalized process that works best when incorporated in the data governance framework. It seeks to correct immediate data quality issues while at the same time eliminating the root causes of those issues. DQM is a continuous process which includes activities such as: defining business requirements and data rules, identifying data problems, instituting data quality processes, cleansing and consolidating data, and meeting data quality service level agreements. Data quality is a hot topic today, and for good reason. Without needed DQ, our enterprises would not be able to make fact-based decisions, and data stakeholders would lose faith in data.

Chapter 13 provides some very good career development advice to data management professionals and prospective data management professionals. Beyond advice to participate in DAMA and become familiar with the DAMA-DMBOK, this chapter advises: continuous education, data-related certifications and ethical conduct. The chapter lists DAMA members who have been recognized for lifetime and professional achievements such as John Zachman, Michael Brackett, Claudia Imhoff, Graeme Simsion and Dr. Gordon Everest, to name a few. DAMA International and the DAMA chapters continue to perform a great service to the professional development of data management professionals.

Appendices support the main text by providing detail.

In the end, the DAMA DMBOK Guide and its companion book, The DAMA Dictionary of Data Management, are must-have additions to the data management professional's bookshelf. The material is well organized, to the point and covers the critical subjects of 21st century data
management.

Register or login for access to this item and much more

All Information Management content is archived after seven days.

Community members receive:
  • All recent and archived articles
  • Conference offers and updates
  • A full menu of enewsletter options
  • Web seminars, white papers, ebooks

Don't have an account? Register for Free Unlimited Access