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 RecordSpecification by ExampleArchitecture Communication CanvasViews and Beyond
| Criterion |  Architecture Architecture Decision Record |  Agile Specification by Example |  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. | 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. | 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 | 60-90 min pro Feature | 60-120 min | 1-3 Tage |
Participantsdifferent | 1-3 | 3-6 | 2-8 | 1-4 |
Formatdifferent | Async | Workshop | Workshop + async | Workshop + async |
Outputdifferent | ADR File, Decision Log, Rationale | Example Table, Acceptance Tests | Communication Canvas, Stakeholder Messages, Architecture Communication Plan | Architecture Views, Cross-view Notes, Rationale |
Tagsno overlap | ArchitectureRationaleDocumentationGovernance | AgileRequirementsExamplesBehavior-Driven Development | ArchitectureCommunicationStakeholdersCanvas | DocumentationStakeholdersArchitecture |