The Common Data Architecture in Perspective
Michael Brackett
Founder and Consulting Data Architect
Data Resource Design and Remodeling
The idea of a Common Data Architecture began about 20 years ago when the author was trying to understand and manage massive quantities of disparate data across multiple jurisdictions. The traditional concepts of file transfer formats and cross-walking were not working and did not provide a thorough understanding of the existing data. As a result, most attempts at integrating disparate data were not fully successful. The problem, as most of us know, has grown much worse over the last 20 years.
The Common Data Architecture has continued to evolve to the point where it is a robust set of concepts, principles, and techniques for formally understanding and managing an organization's data resource. It transcends all data at an organization's disposal, provides a way to understand and resolve existing disparate data, and promotes formal management of a high-quality data resource through an enterprise data architecture. It is the discipline for managing an organization's data resource within Column 1 of the Zachman Framework.
Attendees will learn:
- How the Common Data Architecture has evolved.
- How it provides the means to formally develop a high-quality data resource.
- New terms, concepts, and principles.
- Merging of the Common Data Architecture into the Zachman Framework.
Comments (0)
You don't have permission to comment on this page.