View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:Competency QuestionsArchitecture Communication CanvasArchitecture Decision RecordATAM (Architecture Tradeoff Analysis Method)
| Criterion |  Knowledge Modeling Competency Questions |  Architecture Architecture Communication Canvas |  Architecture Architecture Decision Record |  Architecture ATAM (Architecture Tradeoff Analysis Method) |
|---|---|---|---|---|
Purposedifferent | Competency Questions translate a domain model into concrete questions that it must be able to answer. The method keeps the model's scope clean and prevents pretty but useless structures. | The Architecture Communication Canvas plans architecture communication so the right people receive the right message. The method turns technical complexity into deliberate communication design. | An ADR permanently records an architecture decision with context, trade-offs, and consequence. It creates continuity for later changes because the decision path stays traceable. | ATAM helps teams weigh architecture decisions when quality goals compete. The team considers business goals, stakeholder expectations, and technical decisions together. The evaluation shows which risks need further investigation. |
Complexitydifferent | Medium | Medium | Low | High |
Timedifferent | 2-4 h | 60-120 min | 15-45 min | Several meetings plus preparation and analysis; total effort depends on scope |
Participantsdifferent | 2-8 | 2-8 | 1-3 | Evaluation team, architects, and relevant stakeholders |
Formatdifferent | Workshop + async | Workshop + async | Async | Workshop + async |
Outputdifferent | Competency Question Set, Required Concepts, Test Queries, Coverage Matrix | Communication Canvas, Stakeholder Messages, Architecture Communication Plan | ADR File, Decision Log, Rationale | Prioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigations |
Tagsno overlap | OntologyKnowledge graphScopeRequirementsSemantic | ArchitectureCommunicationStakeholdersCanvas | ArchitectureRationaleDocumentationGovernance | ArchitectureQualityRiskTradeoffsStakeholders |