Rapid Battle Cards 10–18
Card 10 — Zachman ontology vs methodology
Core distinction: ontology classifies architecture descriptions; methodology prescribes how work is performed. Chapter 4 describes Zachman as the former.
Deciding clue: if an answer says Zachman dictates modeling/project steps, reject it.
Source: pp. 104–105.
Card 11 — Business vs Data Architecture
Core distinction: Business Architecture explains value, capabilities, and processes; Data Architecture explains how data should be organized and managed.
Deciding clue: what the enterprise does/how it creates value → Business. Meaning/organization/flow of data → Data.
Source: pp. 103–104.
Card 12 — Application vs Technology Architecture
Core distinction: Application = business systems/software/database functionality; Technology = physical platforms, networks, infrastructure, security, integration technology.
Deciding clue: software structure/function → Application. Infrastructure/platform → Technology.
Source: pp. 103–104.
Card 13 — Quality-oriented vs innovation-oriented architecture
Core distinction: quality protects coherence and improves execution; innovation supports transformation and new opportunities.
Deciding clue: standardization/reuse/prevent deterioration → quality. Disruptive product/technology/new business model → innovation.
Source: p. 111.
Card 14 — Evaluate specifications vs develop roadmap
Core distinction: evaluation establishes a trusted current state; roadmap plans future evolution.
Deciding clue: “What do we really have?” → evaluate. “How do we move to target?” → roadmap.
Source: pp. 112–113.
Card 15 — Buy vs reuse vs build
Core distinction: Buy maps a vendor/COTS model; Reuse maps existing enterprise capability; Build creates new structures to standards.
Deciding clue: external package → Buy. Existing internal governed asset → Reuse. New custom structure → Build.
Source: p. 115.
Card 16 — Preferred vs Containment
Core distinction: Preferred encourages broad appropriate use; Containment limits expansion.
Deciding clue: use more → Preferred. Keep only where needed / discourage new use → Containment.
Source: pp. 116–117.
Card 17 — Emerging vs Reviewed
Core distinction: Emerging is actively being researched/piloted for potential use; Reviewed has been evaluated but is not placed in another lifecycle state.
Deciding clue: active trial → Emerging. Evaluation complete/no other status → Reviewed.
Source: pp. 116–117.
Card 18 — Architecture compliance vs business-value metric
Core distinction: compliance measures adherence to architecture/engagement processes; business value measures enterprise outcome benefit.
Deciding clue: “Did we follow the architecture?” → compliance. “Did business improve?” → value.
Source: pp. 120–121.
Rapid discrimination mini-drill
- Project table is checked against enterprise logical model → architecture design review / enterprise requirements within projects.
- CRM → integration → shared store → analytics → Data Flow Design.
- Platform is being piloted → Emerging.
- Team is checking whether old architecture docs match reality → Evaluate Existing Data Architecture Specifications.
- Four-year sequence of milestones/resources/costs → Implementation roadmap.
- Enterprise concepts/relationships with no storage technology → conceptual/logical, not physical.