Guided Learning — Chapter 4 Data Architecture
This reading path converts the current Drive Guided Learning Guide into shorter GitHub lessons without shrinking the chapter into definitions.
Learning sequence
- Architecture mental model — what architecture means, why it exists, and the artifacts/activities/behavior triad.
- Enterprise Architecture domains & frameworks — Business/Data/Application/Technology and Zachman.
- EDM, Data Flow & linkage — enterprise meaning, movement, Subject Areas, vertical/horizontal lineage.
- States, roadmap & architecture practice — current/target/transition, 3–5 year evolution, quality/innovation, work streams.
- Project integration: buy, reuse, build — scope through implementation across delivery methods.
- Tools, lifecycle, governance & metrics — maintaining architecture as operational enterprise knowledge.
What mastery looks like
You can explain why each architecture artifact exists, classify a scenario by its deciding clue, and show how the chapter moves from strategy to enterprise blueprint to project implementation and feedback. You do not treat diagrams as the end product; you can explain the operating practice that makes them useful.