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