Deep Battle Cards E–H
Deep Card E — Zachman Ontology vs Methodology
Definition
Zachman classifies architecture artifacts and perspectives. A methodology tells people how to perform or sequence work.
Purpose
Zachman supports completeness and stakeholder views without dictating a project process.
Deciding distinction
What descriptions exist vs how to produce them.
Scenario
A PM asks Zachman to prescribe sprint order. That is misuse. If the question instead asks which “Who” artifact/perspective is represented, Zachman becomes directly relevant.
Memory hook: Zachman catalogs; it does not conduct.
Source: pp. 104–105.
Deep Card F — Buy vs Reuse vs Build
Definition - Buy: external package/COTS; understand/map vendor structures and gaps. - Reuse: existing enterprise/application capability; map structures, processes, CRUD, authoritative sources. - Build: new storage/integration implementation to architecture standards.
Purpose
Select an implementation path without abandoning enterprise meaning and standards.
Deciding distinction
External package vs existing internal asset vs new implementation.
Scenario
Vendor refuses a data model → Buy + reverse engineering/mapping as needed.
Existing governed Customer service already meets the need → Reuse.
No suitable capability exists → Build.
Exam trap: “Buy” does not mean vendor semantics automatically become enterprise semantics.
Memory hook: Buy learns vendor; Reuse maps existing; Build creates new.
Source: pp. 114–115.
Deep Card G — Preferred vs Emerging vs Containment vs Retirement
Definition - Preferred — broadly recommended. - Emerging — research/pilot for possible future use. - Containment — restrict expansion/use. - Retirement — planned exit/end of use.
Purpose
Make architecture investment/lifecycle intent explicit.
Deciding distinction
Expand, experiment, restrict, or exit.
Scenario
Database is allowed only in legacy apps while migration proceeds → Containment.
New platform is being piloted → Emerging.
Approved default for new solutions → Preferred.
Replacement/removal planned → Retirement.
Exam trap: do not infer the status from age alone; use the stated governance intent.
Memory hook: Preferred grow; Emerging test; Containment limit; Retirement leave.
Source: pp. 116–117.
Deep Card H — Compliance vs Implementation Trends vs Business Value Metrics
Definition - Compliance: adherence to architecture standards/engagement. - Implementation trends: execution patterns—use/reuse/replace/retire, efficiency. - Business value: enterprise outcomes—agility, quality, cost, risk, environment/business benefit.
Purpose
Measure three different management questions: Is architecture followed? Is the estate changing as intended? Is it producing value?
Deciding distinction
Followed rules vs changed estate vs improved outcome.
Scenario - 92% of projects passed architecture review → Compliance. - duplicate platforms reduced 30% → Implementation trend. - product-launch time improved because shared data services are reusable → Business value.
Exam trap: counting diagrams, meetings, or review hours does not automatically prove business value.
Memory hook: COMPLY → CHANGE → VALUE.
Source: pp. 120–121.
Deep-card self-test
For every card above, state one changed fact that switches the answer to another concept in the comparison.