Classification Drills & Keys
Classify each without looking at the key.
C1
Holistic enterprise conceptual/logical view of key data entities and relationships.
Your classification: ____
C2
Blueprint of movement/storage/processing across systems and roles.
Your classification: ____
C3
Link from project physical model upward to enterprise logical/conceptual model.
Your classification: ____
C4
Relationship between entities across Subject Area models at the same abstraction level.
Your classification: ____
C5
Framework that classifies What/How/Where/Who/When/Why across perspectives.
Your classification: ____
C6
Technology being piloted for possible future deployment.
Your classification: ____
C7
Technology restricted to certain applications.
Your classification: ____
C8
A 3–5 year architecture development path.
Your classification: ____
C9
Activity that checks whether existing architecture documents are accurate and complete.
Your classification: ____
C10
Implementation path that reverse engineers/maps a COTS product.
Your classification: ____
C11
Implementation path that maps existing application data to common structures, CRUD, and authoritative-source logic.
Your classification: ____
C12
Metric measuring adherence to architecture standards/engagement processes.
Your classification: ____
C13
Metric measuring reuse/replace/retire and project efficiency.
Your classification: ____
C14
Metric measuring business agility/quality/operational/environment outcomes.
Your classification: ____
Classification key
| Prompt | Answer | Deciding clue |
|---|---|---|
| C1 | Enterprise Data Model (EDM) | enterprise meaning/relationships |
| C2 | Data Flow Design | movement/storage/processing/context |
| C3 | Vertical mapping / model lineage | crosses abstraction levels |
| C4 | Horizontal mapping | same-level relationship |
| C5 | Zachman Framework | six interrogatives × perspectives |
| C6 | Emerging | active research/pilot |
| C7 | Containment | restricted expansion/use |
| C8 | Data Architecture roadmap | multi-year sequenced evolution |
| C9 | Evaluate Existing Data Architecture Specifications | trusted current-state validation |
| C10 | Buy | vendor/COTS mapping/reverse engineering |
| C11 | Reuse | existing enterprise capability + CRUD/authority mapping |
| C12 | Architecture-standard compliance | adherence |
| C13 | Implementation trends | estate/project evolution |
| C14 | Business value | outcome benefit |
Changed-fact challenge
For C1–C14, invent one change to the prompt that would make a different answer correct. If you cannot create the changed fact, return to the relevant Battle Card.