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 Acceptance Criteria Workshop |  Architecture arc42 |  Agile Specification by Example |  Architecture C4 Model |
|---|---|---|---|---|
Purposedifferent | 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. | 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 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. | 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 | Low | Low | Medium | Low |
Timedifferent | 20-40 min pro Story | 1-2 Tage | 60-90 min pro Feature | 1-4 h |
Participantsdifferent | 3-6 | 1-4 | 3-6 | 1-5 |
Formatdifferent | Workshop | Workshop + async | Workshop | Workshop + async |
Outputdifferent | Acceptance Criteria, Story Update | Architecture Document, Context View, Runtime View, Deployment View | Example Table, Acceptance Tests | Context Diagram, Container Diagram, Component Diagram |
Tagsno overlap | AgileRequirementsRefinementBehavior-Driven Development | ArchitectureDocumentationCommunication | AgileRequirementsExamplesBehavior-Driven Development | ArchitectureCommunicationVisualization |