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 Communication CanvasSpecification by ExampleArchitecture Decision RecordViews and Beyond
| Criterion |  Architecture Architecture Communication Canvas |  Agile Specification by Example |  Architecture Architecture Decision Record |  Architecture Views and Beyond |
|---|---|---|---|---|
Purposedifferent | The Architecture Communication Canvas plans architecture communication so the right people receive the right message. The method turns technical complexity into deliberate communication design. | When business rules need to become precise, it ties language, example, and test together. It sorts work by value, risk, and delivery ability. The result is captured as an Example Table and Acceptance Tests. | 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. | 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 | Medium | Medium | Low | Medium |
Timedifferent | 60-120 min | 60-90 min pro Feature | 15-45 min | 1-3 Tage |
Participantsdifferent | 2-8 | 3-6 | 1-3 | 1-4 |
Formatdifferent | Workshop + async | Workshop | Async | Workshop + async |
Outputdifferent | Communication Canvas, Stakeholder Messages, Architecture Communication Plan | Example Table, Acceptance Tests | ADR File, Decision Log, Rationale | Architecture Views, Cross-view Notes, Rationale |
Tagsno overlap | ArchitectureCommunicationStakeholdersCanvas | AgileRequirementsExamplesBehavior-Driven Development | ArchitectureRationaleDocumentationGovernance | DocumentationStakeholdersArchitecture |