Phase C: Data Architecture Knowledge-Based Study

Study notes

1. Overview of Phase C in Establishing an Architecture Capability

   In the TOGAF Standard, 10th Edition, when the Architecture Development Method (ADM) is applied to establish or enhance an Enterprise Architecture (EA) Capability, the phases of the ADM are executed iteratively with a distinct focus on building the capability itself rather than designing enterprise-level business solutions.

   Within this context, Phase C: Information Systems Architectures – Data Architecture defines how architecture-related data, metadata, and artifacts are structured, stored, governed, and managed across the enterprise architecture practice.

   Key Objectives

   • Define the data entities and structures required to operate the Architecture Capability, including the architecture metamodel and repository content schemas.
   • Establish clear ownership, lifecycles, and governance policies for architecture assets, artifacts, and building blocks.
   • Ensure that architecture data can be effectively shared and integrated across governance bodies, stakeholder groups, and delivery projects.

   Core Concepts of Architecture Data

   Operating an effective Architecture Capability relies on treating architecture content as structured, governed enterprise data. In Phase C for an Architecture Capability, the primary deliverable is the definition of how architecture information is managed.

   The Architecture Metamodel

   The architecture metamodel provides the foundational data model for the enterprise architecture practice. It establishes:

   • Core Entities: Standard definitions for entities such as Business Capabilities, Application Components, Data Entities, and Work Packages.
   • Relationships: Explicit linkages between strategic objectives, architecture building blocks, and technical implementations.
   • Attributes: Mandatory metadata (such as lifecycle status, ownership, and sensitivity classification) required for architecture governance.

   Architecture Repository Content

   Phase C establishes the structure and taxonomies for storing architecture data within the Architecture Repository, distinguishing between reference models, architecture standards, and re-usable building blocks.

   Governing Architecture Data

   Just as operational business data requires stewardship, architecture data requires formal data governance to maintain accuracy, currency, and integrity over time.

   Key Governance Mechanisms in Phase C

   • Asset Stewardship: Assigning explicit data owners and stewards responsible for maintaining specific catalogs, matrices, and diagrams.
   • Version Control and Baseline Management: Defining protocols for draft, approved, active, and retired states of architecture artifacts.
   • Access Control and Classification: Protecting sensitive architectural insights (such as critical security configurations and strategic roadmaps) through appropriate authorization levels.
   • Data Quality Metrics: Monitoring consistency, completeness, and alignment across repository artifacts to prevent fragmentation.

   Distinguishing Enterprise Data from Architecture Capability Data

   A critical distinction in TOGAF 10th Edition Foundation relates to the scope of Phase C depending on the ADM iteration:

   • Standard Solution Iteration: Focuses on enterprise business data, customer records, transactional data stores, and business information models.
   • Capability Establishment Iteration: Focuses exclusively on metadata, architecture descriptions, repository structures, and tool schemas that enable the architecture team to deliver value.

   Sample Foundation Practice Question

   Question: When applying the ADM to establish an Enterprise Architecture Capability, what is the primary focus of Phase C: Data Architecture?

   • A: Modeling operational transaction data and database schemas for customer-facing systems.
   • B: Defining the structure, metamodel, and governance mechanisms for architecture content and repository data.
   • C: Selecting specific commercial off-the-shelf software tools for project portfolio management.
   • D: Documenting the business mission, strategic goals, and high-level operating model of the enterprise.

   Correct Answer: B

   Explanation: In the context of establishing an Architecture Capability, Phase C (Data Architecture) addresses the data required to run the practice itself—namely the architecture metamodel, repository structure, and governance of architecture assets. Option A addresses typical solution-level business data architecture; Option C is addressed in Technology/Tools architecture; and Option D is addressed in Preliminary and Phase A/B.