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 Three Amigos |  Agile Specification by Example |  Architecture Architecture Decision Record |
|---|---|---|---|---|
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 story, test, and implementation could drift apart, it brings business perspective, engineering, and quality together early. It prevents a story from being read differently only late in the process. | 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. |
Complexitydifferent | Low | Low | Medium | Low |
Timedifferent | 1-2 Tage | 15-30 min | 60-90 min pro Feature | 15-45 min |
Participantsdifferent | 1-4 | 3 | 3-6 | 1-3 |
Formatdifferent | Workshop + async | Workshop + async | Workshop | Async |
Outputdifferent | Architecture Document, Context View, Runtime View, Deployment View | Clarified Story, Test Examples, Open Questions | Example Table, Acceptance Tests | ADR File, Decision Log, Rationale |
Tagsno overlap | ArchitectureDocumentationCommunication | CollaborationBehavior-Driven DevelopmentQualityRefinement | AgileRequirementsExamplesBehavior-Driven Development | ArchitectureRationaleDocumentationGovernance |