Visual Atlas — Maps 07–12
Map 7 — Low-Latency Accumulation
Draw three mini-pipelines and circle the accumulation point:
- Trickle feed → SOURCE accumulation/mini-batch.
- Messaging → BUS accumulation/distribution.
- Streaming → TARGET queue/buffer accumulation.
Answer check: Do not call every low-latency design “streaming.”
Source: pp. 372–374.
Map 8 — Six Chapter 11 Activities
NEED → ARCHITECT → BUILD → LOAD → DELIVER → EVOLVE
Replace with formal names: 1. Understand Requirements 2. Define and Maintain DW/BI Architecture 3. Develop DW and Data Marts 4. Populate DW 5. Implement BI Portfolio 6. Maintain Data Products
Interpretation: requirements precede technology; maintenance follows delivery.
Source: pp. 374–381.
Map 9 — Three Development Tracks
Draw parallel lanes:
DATA: sources → profiling → mapping → DQ → models/rules
TECHNOLOGY: integration → storage → orchestration → security → operations
BI: semantics → reports → dashboards → analysis experiences
Connect all three to the same release milestone.
Answer check: a warehouse is not “DB team finishes, then users arrive.”
Source: pp. 375–381.
Map 10 — Trust Chain
Source-to-Target Map → Business Rules → DQ/Remediation → Metadata → Lineage → Business UAT
Interpretation: each step explains what the data means, what happened to it, or why the business should accept it.
Rebuild: annotate remediation = fix defect; transformation = legitimate conversion/derivation.
Answer check: technical load success without understandable definitions, quality, lineage, and business validation is incomplete trust.
Source: pp. 375–379, 385–391.
Map 11 — Data Product Lifecycle
Backlog → Develop → Pilot/Sandbox → Business + IT Readiness → Production → Monitor/Tune → Backlog
Add release/configuration control across environments.
Production gate: acceptance + quality + security/governance + monitoring + support + controlled deployment.
Answer check: a successful pilot is not automatically production-ready.
Source: pp. 380–392.
Map 12 — Evidence of Value
Center: DW/BI VALUE
Spokes: - Usage / adoption - Subject-area coverage - Load/service support - Query/refresh performance - Customer satisfaction / trust
Interpretation: installed capacity, terabytes, licenses, or dashboard counts alone do not prove value.
Rebuild: write the management question beside each spoke: Use it? Cover it? Run it? Value it?
Source: pp. 391–393.
Final visual-recall test
Rebuild Maps 2, 3, 6, 7, 8, 10, and 11 without looking. For each, say the one fact that would change the exam answer.