Study guide

7.2 Data Architecture Domain: Data Entities, Storage & Data Management

TOGAF Enterprise Architecture Study Guide Exam

Track your progress as you read

Finished sections get a check mark.

1 Chapter 1: Introduction to TOGAF & Enterprise Architecture Concepts

1.1 Overview of TOGAF Standard 10th Edition & Enterprise Architecture Concepts 1.2 The Structure of the TOGAF Standard (Easily Navigated Body of Knowledge) 1.3 Core Concepts: Enterprise, Architecture, Deliverables, Artifacts, and Building Blocks 1.4 TOGAF Certification Paths & the OGEA-101 Exam Plan

2 Chapter 2: ADM Foundation & Preliminary Phase

2.1 The Architecture Development Method (ADM) Cycle & Requirements Management 2.2 Preliminary Phase: Scope, Principles, and Architecture Capability Setup 2.3 Tailoring the ADM & Applying Iteration / Architecture Levels 2.4 Applying the ADM: The TOGAF Library, Purpose-Based Architecture Projects & the Digital Enterprise

3 Chapter 3: ADM Architecture Vision & Business Architecture

3.1 Phase A: Architecture Vision, Stakeholder Management & Value Proposition 3.2 Business Architecture Scope, Strategy & Capability Mapping 3.3 Phase B: Business Architecture Inputs, Steps, Outputs & Artifacts 3.4 Business Scenarios & Value Stream Modeling

4 Chapter 4: ADM Information Systems Architectures (Phase C)

4.1 Information Systems Architectures Overview & Phase C Strategy 4.2 Phase C Data Architecture: Principles, Data Models & Governance 4.3 Phase C Application Architecture: Logical Components, Services & Interfaces 4.4 Data and Application Integration, Migration & Interoperability

5 Chapter 5: ADM Technology Architecture & Solution Realization (Phases D, E, F)

5.1 Phase D: Technology Architecture, Platform Services & Infrastructure 5.2 Phase E: Opportunities and Solutions & Initial Implementation Strategy 5.3 Phase F: Migration Planning, Roadmap Development & Portfolio Prioritization 5.4 Transition Architectures & Implementation Dependencies

6 Chapter 6: ADM Governance, Change & Requirements Management (Phases G, H)

6.1 Phase G: Implementation Governance & Architecture Compliance 6.2 Phase H: Architecture Change Management & Driver Monitoring 6.3 Requirements Management: Central Flow, Impact Analysis & Traceability 6.4 Architecture Contracts, Dispensations & Compliance Reviews

7 Chapter 7: BDAT Architecture Domains Deep-Dive

7.1 Business Architecture Domain: Functions, Processes & Value Streams 7.2 Data Architecture Domain: Data Entities, Storage & Data Management 7.3 Application Architecture Domain: Application Services, Systems & Integration Patterns 7.4 Technology Architecture Domain: Hardware, Software, Cloud & Network Platforms

8 Chapter 8: Architecture Content — Content Framework, Enterprise Metamodel & Artifacts

8.1 Architecture Content Framework Overview & Deliverables vs Artifacts vs Building Blocks 8.2 Architecture Building Blocks (ABBs) vs Solution Building Blocks (SBBs) 8.3 The Enterprise Metamodel: Core Concepts, Entities & Attributes 8.4 Architecture Catalogs, Matrices & Diagrams (Visual Representation) 8.5 Stakeholders, Concerns, Architecture Views & Viewpoints

9 Chapter 9: Architecture Governance, Capability & Maturity

9.1 Architecture Governance Framework & The Role of the Architecture Board 9.2 Establishing an Architecture Capability & Organizational Structure 9.3 Architecture Skills Framework, Roles & Competency Levels 9.4 Architecture Maturity Models & Capability Assessments

10 Chapter 10: Enterprise Continuum, Reference Models & Key Techniques

10.1 Enterprise Continuum, Architecture Repository & Landscape Partitioning 10.2 Technical Reference Model (TRM) & Integrated Information Infrastructure Reference Model (III-RM) 10.3 Core EA Techniques: Gap Analysis, Interoperability, Risk, Capability-Based Planning & Architecture Patterns

7.2 Data Architecture Domain: Data Entities, Storage & Data Management

Key Takeaways Explain This Topic AI

Data Architecture structures an enterprise's data assets across three primary modeling levels: Conceptual (business semantics), Logical (attributes and normalization), and Physical (database schemas and storage engines).

Logical Data Components encapsulate domain data entities, whereas Physical Data Components embody concrete databases, data warehouses, data lakes, and storage repositories.

System of Record (SoR) and CRUD (Create, Read, Update, Delete) matrices establish clear data ownership, eliminating redundant data modification and preserving data integrity.

Data Governance frameworks enforce data quality criteria, stewardship roles, and regulatory compliance standards such as GDPR, CCPA, and HIPAA across the data lifecycle.

Key Data Architecture deliverables in TOGAF Phase C include Data Entity Catalogs, Entity-Relationship Diagrams, Data Lifecycle Diagrams, and Data Dissemination Matrices.

Last updated: August 2026

7.2 Data Architecture Domain: Data Entities, Storage & Data Management

Data Architecture constitutes a critical component of Phase C (Information Systems Architectures) in the TOGAF ADM. It defines the structure, governance, storage, movement, and lifecycle of an enterprise's logical and physical data assets and data management resources. Because data outlives individual software applications, establishing a rigorous Data Architecture ensures that enterprise data remains accurate, accessible, secure, and aligned with strategic business capabilities.

Data Architecture provides the blueprint for transforming raw operational transactions into trusted analytical insights and strategic decision-making assets across the enterprise.

The Three Abstraction Levels of Data Models

TOGAF structures Data Architecture artifacts across three distinct levels of modeling abstraction: Conceptual Data Models , Logical Data Models , and Physical Data Models . Each level targets a specific stakeholder audience and serves a unique architectural purpose.

Model Level Target Audience Primary Focus Key Content & Constructs Implementation Dependency

Conceptual Data Model Business Executive & Domain Owners High-Level Business Semantics Major Data Entities (Subject Areas), high-level relationships, business definitions. Completely Technology & Vendor Independent

Logical Data Model Data Architects & Business Analysts Structural Integrity & Rules Normalized entities, attributes, primary/foreign keys, cardinality, validation rules. DBMS Engine Independent (Relational/NoSQL neutral)

Physical Data Model Database Administrators & Software Engineers Storage Performance & Execution Tables, columns, datatypes, indexes, partitions, storage engines, foreign key constraints. Database Engine Specific (PostgreSQL, Oracle, Snowflake, MongoDB)

1. Conceptual Data Model: Business Semantics

The Conceptual Data Model captures high-level business data concepts (Data Entities) and their primary interrelationships. It establishes a common business vocabulary (Business Glossary) to eliminate ambiguity across business domains.

Key Constructs: High-level entities such as Customer , Account , Product , Order , and Supplier .

Scope: Covers broad enterprise subject areas without detailing attributes, data types, or database technicalities.

2. Logical Data Model: Structural Rigor & Normalization

The Logical Data Model expands the conceptual model by defining specific attributes, relationships, cardinalities (e.g., 1-to-Many, Many-to-Many), and data integrity rules. Logical models typically adhere to database normalization standards (e.g., Third Normal Form - 3NF) to eliminate redundant data attributes and prevent update anomalies.

Key Constructs: Entity attributes (e.g., Customer_Tax_ID , Order_Placement_Timestamp ), relationship cardinalities, domain constraints, and candidate keys.

Neutrality: Remains independent of whether data will eventually be stored in a relational RDBMS, document database, or graph store.

3. Physical Data Model: DBMS Execution & Storage

The Physical Data Model translates the logical model into concrete technical implementations optimized for specific storage engines and performance requirements. Physical modeling balances normalization with controlled denormalization to achieve target query latency, throughput, and storage efficiency.

Key Constructs: Physical table schemas, column data types (e.g., VARCHAR(255) , UUID ), primary key indexes, B-tree/LSM indexes, table partitioning schemes, and sharding keys.

Storage Paradigms: Encompasses relational databases (OLTP), columnar analytical data warehouses (OLAP), document stores, key-value caches, and distributed object storage. +---------------------------------------------------------------------------------+

  • | CONCEPTUAL MODEL: [Customer] -------- (Places) --------> [Order] |
  • +---------------------------------------------------------------------------------+
  • |
  • v
  • +---------------------------------------------------------------------------------+
  • | LOGICAL MODEL: Customer (ID, Name, Email) 1---* Order (ID, CustID, Date, Amt)|
  • +---------------------------------------------------------------------------------+
  • |
  • v
  • +---------------------------------------------------------------------------------+
  • | PHYSICAL MODEL: CREATE TABLE tbl_customer (cust_id UUID PRIMARY KEY, ...) |
  • | CREATE TABLE tbl_order (order_id BIGINT, cust_id UUID, ...) |
  • +---------------------------------------------------------------------------------+
  • Logical vs. Physical Data Components

In TOGAF, Data Architecture categorizes data repositories into Data Components :

Logical Data Components: Boundary definitions that group logically related data entities serving specific business capabilities (e.g., Customer Master Data Component , Financial Ledger Data Component ).

Physical Data Components: Actual physical software systems, database instances, or storage clusters hosting the data (e.g., PostgreSQL Customer DB Cluster , AWS S3 Analytics Data Lake , Snowflake Financial Warehouse ).

Core Data Management & Governance Principles

Data Architecture must define explicit operational principles governing data ownership, consistency, and compliance across the enterprise lifecycle:

1. System of Record (SoR) & Golden Source

For every enterprise data entity, Data Architecture must designate a single System of Record (SoR) . The System of Record is the authoritative, canonical source responsible for creating and updating that entity. All other downstream applications, data marts, and caches consume read-only replicas or synchronized feeds from the System of Record, preventing conflicting data edits across systems.

2. CRUD Matrix (Create, Read, Update, Delete)

A CRUD Matrix maps Application Components to Data Entities, explicitly declaring which application holds authority to C reate, R ead, U pdate, or D elete specific data entities. Enforcing strict CRUD boundaries prevents unauthorized applications from directly modifying underlying database tables. +-----------------------+------------------+------------------+------------------+

  • | Application / Entity | Customer Entity | Order Entity | Product Catalog |
  • +-----------------------+------------------+------------------+------------------+
  • | CRM Portal | CREATE / UPDATE | READ | READ |
  • | Order Engine | READ | CREATE / UPDATE | READ |
  • | Inventory System | NO ACCESS | READ | CREATE / UPDATE |
  • | Billing Gateway | READ | UPDATE | NO ACCESS |
  • +-----------------------+------------------+------------------+------------------+
  • 3. Data Privacy and Regulatory Compliance

Modern Data Architecture must bake regulatory compliance directly into data storage and flow models. Architectures must address:

Data Classification: Categorizing data into Public, Internal, Confidential, and Restricted (PII / PHI).

Regulatory Frameworks: Enforcing GDPR (Right to be Forgotten, Data Minimization), CCPA, and HIPAA requirements.

Security Controls: Implementing field-level encryption at rest (AES-256), TLS encryption in transit, data masking, pseudonymization, and role-based access control (RBAC).

Key Data Architecture Deliverables in TOGAF

During Phase C, the data architecture team produces standardized architectural deliverables stored in the Enterprise Architecture Repository:

Data Entity Catalog: Master inventory of all enterprise data entities, definitions, owners, and classification levels.

Data Entity / Data Component Matrix: Matrix mapping logical data entities to physical storage systems.

Data Dissemination Diagram: Visual mapping showing how data flows between source systems, integration hubs, and destination data stores.

Data Lifecycle Diagram: Diagram depicting the lifecycle stages of critical data entities from creation, ingestion, transformation, storage, archiving, to purge/deletion.