View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:Specification by ExampleViews and BeyondArchitecture Decision RecordArchitecture Communication Canvas
| Criterion |  Agile Specification by Example |  Architecture Views and Beyond |  Architecture Architecture Decision Record |  Architecture Architecture Communication Canvas |
|---|---|---|---|---|
Purposedifferent | 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. | 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. | 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 | 60-90 min pro Feature | 1-3 Tage | 15-45 min | 60-120 min |
Participantsdifferent | 3-6 | 1-4 | 1-3 | 2-8 |
Formatdifferent | Workshop | Workshop + async | Async | Workshop + async |
Outputdifferent | Example Table, Acceptance Tests | Architecture Views, Cross-view Notes, Rationale | ADR File, Decision Log, Rationale | Communication Canvas, Stakeholder Messages, Architecture Communication Plan |
Tagsno overlap | AgileRequirementsExamplesBehavior-Driven Development | DocumentationStakeholdersArchitecture | ArchitectureRationaleDocumentationGovernance | ArchitectureCommunicationStakeholdersCanvas |