View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:Views and BeyondCompetency QuestionsArchitecture Decision RecordArchitecture Communication Canvas
| Criterion | ![]() Architecture Views and Beyond | ![]() Knowledge Modeling Competency Questions | ![]() Architecture Architecture Decision Record | ![]() Architecture Architecture Communication Canvas |
|---|---|---|---|---|
Purposedifferent | 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. | 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. | 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. | The Architecture Communication Canvas plans architecture communication so the right people receive the right message. The method turns technical complexity into deliberate communication design. |
Complexitydifferent | Medium | Medium | Low | Medium |
Timedifferent | 1-3 Tage | 2-4 h | 15-45 min | 60-120 min |
Participantsdifferent | 1-4 | 2-8 | 1-3 | 2-8 |
Formatdifferent | Workshop + async | Workshop + async | Async | Workshop + async |
Outputdifferent | Architecture Views, Cross-view Notes, Rationale | Competency Question Set, Required Concepts, Test Queries, Coverage Matrix | ADR File, Decision Log, Rationale | Communication Canvas, Stakeholder Messages, Architecture Communication Plan |
Tagsno overlap | DocumentationStakeholdersArchitecture | OntologyKnowledge graphScopeRequirementsSemantic | ArchitectureRationaleDocumentationGovernance | ArchitectureCommunicationStakeholdersCanvas |



