Rapid Battle Cards 1–9
Card 1 — Data Architecture vs Data Modeling & Design
Core distinction: Architecture identifies enterprise needs and maintains master blueprints; Modeling & Design develops specific models and implementation designs.
Deciding clue: enterprise scope / target / roadmap / integration / standards → Architecture. Modeling technique / normalization / keys / physical schema → Modeling & Design.
Source: pp. 100, 106–109.
Card 2 — EDM vs Data Flow Design
Core distinction: EDM gives shared enterprise concepts and relationships; Data Flow Design gives movement, storage, processing, transformation, and context.
Deciding clue: what the data means → EDM. Where/how it moves → Flow.
Source: p. 106.
Card 3 — Enterprise conceptual model vs Subject Area model
Core distinction: enterprise conceptual view summarizes the enterprise’s major semantic regions; Subject Area model expands one bounded subject into major entities/relationships.
Deciding clue: whole-enterprise overview → enterprise conceptual. One bounded business subject → Subject Area.
Source: pp. 107–109.
Card 4 — Enterprise logical model vs project physical model
Core distinction: enterprise logical is detailed but implementation-independent; project physical is technology/storage specific.
Deciding clue: enterprise semantics → logical enterprise view. Tables/indexes/storage choices for one implementation → project physical.
Source: pp. 107–108.
Card 5 — Vertical vs horizontal mappings
Core distinction: vertical links abstraction levels; horizontal links peer models/entities at the same level.
Deciding clue: up/down lineage → vertical. Side-to-side cross-Subject Area/model relationship → horizontal.
Source: pp. 107–108.
Card 6 — Top-down vs bottom-up EDM
Core distinction: top-down starts by forming Subject Areas; bottom-up starts from existing models and derives enterprise structure.
Deciding clue: structure-first → top-down. Existing-model-first → bottom-up.
Source: p. 108.
Card 7 — Current vs target architecture
Core distinction: current describes the as-is landscape; target describes the intentional future.
Deciding clue: what exists → current. What the enterprise wants to become → target.
Source: pp. 99–100, 106.
Card 8 — Target vs transition state
Core distinction: target is the desired end-state; transition is an intermediate architecture during migration.
Deciding clue: destination → target. Temporary coexistence/stepping-stone → transition.
Source: p. 106; pp. 112–115.
Card 9 — Framework vs roadmap
Core distinction: framework organizes architecture viewpoints/classifications; roadmap sequences evolution through time.
Deciding clue: structure for thinking → framework. Milestones/dependencies/resources/sequence → roadmap.
Source: pp. 104, 112–113.