Skip to content

Visual Atlas — Maps 8–10

Map 8 — Vertical vs horizontal model linkage

             ENTERPRISE CONCEPT
                    ↑ ↓
            ENTERPRISE LOGICAL
                    ↑ ↓       ↔ peer model/entity
             PROJECT LOGICAL  ↔ same-level model
                    ↑ ↓
             PROJECT PHYSICAL

VERTICAL = changes abstraction altitude
HORIZONTAL = stays at same abstraction level

Interpretation: vertical mapping creates traceability from implementation to enterprise meaning. Horizontal mapping preserves same-level cross-model/Subject Area relationships.

Source: pp. 107–108.


Map 9 — Project architecture loop

SCOPE
  enterprise alignment • reuse • dependencies
   ↓
REQUIREMENTS
  entities • sources • availability • quality • value
   ↓
DESIGN
  enterprise constructs • standards • target specifications
   ↓
IMPLEMENT
  BUY | REUSE | BUILD
   ↓
FEED BACK
  return reusable/new enterprise knowledge to architecture
   ↺

Interpretation: architecture is not a gate that appears at the end. It shapes project decisions and harvests valid enterprise learning from delivery.

Rebuild check: under Implement, classify Buy/Reuse/Build correctly.

Source: pp. 114–115.


Map 10 — Architecture governance alignment

Role / mechanism Primary architecture connection
Data Architect Business liaison; enterprise requirements, blueprints, standards, design oversight.
Data Steward Business meaning, Subject Area/entity accountability, governance alignment.
Project Team Uses/improves architecture assets and implements solutions to applicable standards.
Portfolio / Enterprise Architecture Sequences priorities so funded change moves toward target architecture.
Data Governance Decision rights, oversight, standards, visible exception paths.
Business / Governance intent
       ↕
Architect ↔ Steward
   ↕         ↕
Project delivery ↔ Portfolio / EA
       ↺ reusable knowledge + governed decisions

Interpretation: no single actor owns everything. Architects do not become the business meaning owner or the project implementation team. Governance does not replace architecture execution.

Source: pp. 115–116, 120.

Final visual test

Without looking, rebuild Maps 4, 5, 6, 7, and 9, then state one changed fact that would change a classification in each.

← Maps 5–7 · Battle Cards →