View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion | ![]() Architecture arc42 | ![]() Knowledge Modeling Competency Questions | ![]() Agile Example Mapping | ![]() Architecture Architecture Communication Canvas |
|---|---|---|---|---|
Purposedifferent | arc42 structures architecture knowledge so teams can document system, decisions, and risks consistently. The template builds a living understanding of the architecture instead of scattered notes. | 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. | When a story carries business rules and exceptions, it brings clarity before implementation. It makes examples, open questions, and boundaries visible enough that the logic becomes jointly sound. | 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 | Low | Medium | Low | Medium |
Timedifferent | 1-2 Tage | 2-4 h | 30-60 min | 60-120 min |
Participantsdifferent | 1-4 | 2-8 | 3-7 | 2-8 |
Formatdifferent | Workshop + async | Workshop + async | Workshop | Workshop + async |
Outputdifferent | Architecture Document, Context View, Runtime View, Deployment View | Competency Question Set, Required Concepts, Test Queries, Coverage Matrix | Example Map, Acceptance Criteria, Open Questions | Communication Canvas, Stakeholder Messages, Architecture Communication Plan |
Tagsno overlap | ArchitectureDocumentationCommunication | OntologyKnowledge graphScopeRequirementsSemantic | Behavior-Driven DevelopmentRequirementsExamplesRefinement | ArchitectureCommunicationStakeholdersCanvas |



