Menu
Log in



  • Home
  • News
  • DMBoK Figure 21 Context Diagram : Data Architecture


DMBoK Figure 21 Context Diagram : Data Architecture

10/11/2023 7:30 AM | Anonymous member (Administrator)


Primary Data Architecture outcomes include:

  • Data storage and processing requirements

  • Designs of structures and plans that meet the current and long-term data requirements of the enterprise

Architects seek to design in a way that brings value to the organization. this values comes through an optimal technical footprint, operational and project efficiencies, and the increased ability of the organization to use its data. to get there requires good design, planning, and the ability to ensure that the designs and plans are executed effectively.

To reach these goals, Data Architects define and maintain specifications that:

  • Define the current state of data in the organization

  • Provide a standard business vocabulary for data and components

  • Align Data Architecture with enterprise strategy and business architecture

  • Express strategic data requirements

  • Outline high-level integrated designs to meet these requirements

  • Integrate with overall enterprise architecture roadmap

An overall Data Architecture practice includes:

  • Using Data Architecture artifacts (master blueprints) to define data requirements, guide data integration, control data assets, and align data investments with business strategy

  • Collaborating with, learning from and influencing various stakeholders that are engaged with improving the business or IT systems development

  • Using Data Architecture to establish the semantics of an enterprise, via a common business vocabulary


Powered by Wild Apricot Membership Software