Concept and mechanism
Supporting techniques turn scattered information into justified decisions. A capability assessment can reveal missing skills; gap analysis exposes required work; a business scenario clarifies actors, environment, and outcome. Choose the technique for the unresolved question. A detailed diagram does not independently resolve an ownership dispute. Keep terminology consistent and distinguish abstract need from concrete choice: federated authentication is a capability, while a specific product configuration is one possible realization. A template can organize work, but completing every section does not demonstrate architecture fitness.
Guided application
In a decision exercise, two options obtain similar weighted-matrix scores. Examine sensitivity to weights and estimate uncertainty before announcing a winner. Check mandatory constraints first: an infeasible option does not become acceptable by scoring well on cost. Record assumptions and consequences in a simple format linked to evidence. For Practitioner study, practice choosing the best response across the complete context. The official exam uses gradient scoring and integrated reference access; this course’s internal assessment uses the usual dr.pt mechanism and does not reproduce that scale. Do not interpret an internal percentage as a certification prediction. Practice should improve explanations of choices and recognition of missing information.
An option violating a mandatory constraint does not win by being cheaper.
Common pitfalls
Template treated as approval; numeric precision treated as certainty; product treated as need.
Related topics: Context, mandate, and value · Stakeholders, conflicts, and views · Vision, scope, and feasibility
Choose techniques that answer the decision and document limitations.
Reference: Template deliverables by standard edition · OGEA-102; TOGAF Standard, 10th Edition