Rebuild & Blank-Page Drills
Part II — 3-minute rebuilds
T1 — Strategy bridge
Draw: Business Strategy → Data Architecture → Technology Execution
Add at least three architecture outputs and explain the arrows.
T2 — Four EA domains
Draw Business, Data, Application, Technology Architecture and one dependency/primary question for each.
T3 — Zachman header
Write the six columns from memory: What / How / Where / Who / When / Why. Explain why multiple perspective rows exist and write ontology, not methodology.
T4 — EDM stack
Rebuild enterprise conceptual → Subject Area → enterprise logical → project logical → project physical. Mark vertical and horizontal mappings.
T5 — Data flow
Draw a source-to-consumer flow and label at least: application/process, data store, CRUD role, location, and network/security context.
T6 — States and roadmap
Build current → gap/dependencies → roadmap/transition projects → target. Explain target vs transition.
T7 — Practice work streams + project influence
Reconstruct the five work streams and then list how architecture influences project Scope, Requirements, Design, Implement, Feedback.
T8 — Buy / Reuse / Build
Create a three-column decision table with trigger, architecture action, and main risk for each path.
T9 — Lifecycle statuses
Write all eight statuses and one-line meanings. Then circle Preferred, Emerging, Containment, and Retirement and explain the switch clue among them.
T10 — Governance + metrics
On one page, connect the four architecture governance activities to the three metric families.
Part III — 5-minute blank-page reconstructions
B1 — Full Chapter 4 skeleton
Reconstruct: definition → EA domains/frameworks → EDM/flows → practice/activities → current/target/roadmap → project integration → tools/techniques/lifecycle → implementation/culture → governance/metrics.
B2 — Four-way discipline comparison
Teach the difference among: - Data Architecture, - Data Modeling & Design, - Application Architecture, - Technology Architecture.
Use one Customer example and change the deciding fact for each.
B3 — Architecture artifact map
Show how EDM, Subject Area models, enterprise/project logical models, physical models, flows, data value chains, and the roadmap relate without pretending they are interchangeable.
B4 — Moving from current to target
Explain how a company moves from current architecture to target through roadmap sequencing and transition projects without losing enterprise alignment or ignoring business urgency.
B5 — Why great diagrams can still fail
Teach how an accurate, beautiful architecture can still fail because: - working methods do not use it, - governance does not enforce/approve exceptions, - projects do not reuse it, - culture remains local/application-centered, - executives contradict it, - metrics do not demonstrate value.
Compression teach-back
5 minutes: teach the full chapter.
2 minutes: keep only the major discriminators and implementation logic.
30 seconds: state the professional rule: architecture connects enterprise need, blueprint, project execution, governance, and behavior so enterprise data evolves coherently.