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 |  Agile Acceptance Criteria Workshop |  Architecture Architecture Decision Record |  Agile Specification by Example |
|---|---|---|---|---|
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. | 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. | 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. |
Complexitydifferent | Low | Low | Low | Medium |
Timedifferent | 1-2 Tage | 20-40 min pro Story | 15-45 min | 60-90 min pro Feature |
Participantsdifferent | 1-4 | 3-6 | 1-3 | 3-6 |
Formatdifferent | Workshop + async | Workshop | Async | Workshop |
Outputdifferent | Architecture Document, Context View, Runtime View, Deployment View | Acceptance Criteria, Story Update | ADR File, Decision Log, Rationale | Example Table, Acceptance Tests |
Tagsno overlap | ArchitectureDocumentationCommunication | AgileRequirementsRefinementBehavior-Driven Development | ArchitectureRationaleDocumentationGovernance | AgileRequirementsExamplesBehavior-Driven Development |