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 Views and Beyond |  Agile Example Mapping |  Architecture Architecture Decision Record |  Agile Acceptance Criteria Workshop |
|---|---|---|---|---|
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. | 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. | 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 a story needs clear checkpoints before implementation, it sharpens expectation and scope together. It sorts work by value, risk, and delivery ability. The result is captured as Acceptance Criteria and a Story Update. |
Complexitydifferent | Medium | Low | Low | Low |
Timedifferent | 1-3 Tage | 30-60 min | 15-45 min | 20-40 min pro Story |
Participantsdifferent | 1-4 | 3-7 | 1-3 | 3-6 |
Formatdifferent | Workshop + async | Workshop | Async | Workshop |
Outputdifferent | Architecture Views, Cross-view Notes, Rationale | Example Map, Acceptance Criteria, Open Questions | ADR File, Decision Log, Rationale | Acceptance Criteria, Story Update |
Tagsno overlap | DocumentationStakeholdersArchitecture | Behavior-Driven DevelopmentRequirementsExamplesRefinement | ArchitectureRationaleDocumentationGovernance | AgileRequirementsRefinementBehavior-Driven Development |