View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:Architecture Decision RecordCompetency QuestionsArchitecture Communication CanvasViews and Beyond
| Criterion |  Architecture Architecture Decision Record |  Knowledge Modeling Competency Questions |  Architecture Architecture Communication Canvas |  Architecture Views and Beyond |
|---|---|---|---|---|
Purposedifferent | 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. | 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. | Views and Beyond organizes architecture into several views so no single diagram has to do everything at once. This makes it possible to choose the representation that fits the stakeholder's question. |
Complexitydifferent | Low | Medium | Medium | Medium |
Timedifferent | 15-45 min | 2-4 h | 60-120 min | 1-3 Tage |
Participantsdifferent | 1-3 | 2-8 | 2-8 | 1-4 |
Formatdifferent | Async | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | ADR File, Decision Log, Rationale | Competency Question Set, Required Concepts, Test Queries, Coverage Matrix | Communication Canvas, Stakeholder Messages, Architecture Communication Plan | Architecture Views, Cross-view Notes, Rationale |
Tagsno overlap | ArchitectureRationaleDocumentationGovernance | OntologyKnowledge graphScopeRequirementsSemantic | ArchitectureCommunicationStakeholdersCanvas | DocumentationStakeholdersArchitecture |