View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Agile Specification by Example |  Architecture arc42 |  Architecture Architecture Decision Record |  Architecture C4 Model |
|---|---|---|---|---|
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. | 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. | 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 C4 Model makes a system legible across several resolution levels, from context down to code. It suits situations where different audiences need to understand the same architecture from different altitudes. |
Complexitydifferent | Medium | Low | Low | Low |
Timedifferent | 60-90 min pro Feature | 1-2 Tage | 15-45 min | 1-4 h |
Participantsdifferent | 3-6 | 1-4 | 1-3 | 1-5 |
Formatdifferent | Workshop | Workshop + async | Async | Workshop + async |
Outputdifferent | Example Table, Acceptance Tests | Architecture Document, Context View, Runtime View, Deployment View | ADR File, Decision Log, Rationale | Context Diagram, Container Diagram, Component Diagram |
Tagsno overlap | AgileRequirementsExamplesBehavior-Driven Development | ArchitectureDocumentationCommunication | ArchitectureRationaleDocumentationGovernance | ArchitectureCommunicationVisualization |