Visual Atlas — Maps 5–7
Map 5 — Data Flow Design / lineage context
SOURCE / ORIGIN
↓
MOVEMENT / INTEGRATION
↓
TRANSFORMATION / PROCESSING
↓
STORE / DESTINATION / CONSUMER
Context around the flow:
• business process • application • data store • CRUD role
• location • network/security segment • technical component
Interpretation: flow design adds operational traceability to enterprise meaning. It answers where data comes from, moves, changes, and is used.
Rebuild check: include at least a source, direction, movement/integration, store/consumer, and one contextual dimension. If you only drew entity relationships, you drew an EDM, not a flow.
Source: pp. 109–110; Figures 25–26.
Map 6 — Current → transition/roadmap → target
CURRENT STATE
what truly exists
↓ gap / dependency analysis
ROADMAP
roughly 3–5 years • milestones • resources • costs • dependencies
↓ implemented through
TRANSITION STATES / PROJECTS
intermediate architectures / coexistence / migration
↓
TARGET STATE
intended future architecture
Interpretation: the target is a destination, not the migration plan. Transition states make the route realistic.
Rebuild check: include current, target, roadmap/sequence, and at least one transition state. Do not turn the roadmap into a static target diagram.
Source: pp. 112–115.
Map 7 — Lifecycle projection statuses
Rebuild all eight source terms:
| Status | Memory cue |
|---|---|
| Current | supported/used now |
| Deployment Period | nearer-term planned deployment |
| Strategic Period | longer-horizon planned/expected use |
| Retirement | leaving service / planned exit |
| Preferred | broadly recommended |
| Containment | restrict expansion/use |
| Emerging | research/pilot |
| Reviewed | evaluated; not another status |
Four-way discrimination map
PREFERRED → grow / recommend
EMERGING → test / pilot
CONTAINMENT → limit / hold
RETIREMENT → exit / replace
Interpretation: lifecycle labels communicate architecture intent so “installed,” “recommended,” “pilot,” and “retiring” do not look equivalent.
Rebuild check: a pilot is Emerging, not Preferred. Existing legacy use can be Containment without being immediately retired.
Source: pp. 116–117.