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 Example Mapping |  Architecture C4 Model |  Agile Acceptance Criteria Workshop |  Architecture arc42 |
|---|---|---|---|---|
Purposedifferent | When a story carries business rules and exceptions, it brings clarity before implementation. It makes examples, open questions, and boundaries visible enough that the logic becomes jointly sound. | 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 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. |
Complexitysame | Low | Low | Low | Low |
Timedifferent | 30-60 min | 1-4 h | 20-40 min pro Story | 1-2 Tage |
Participantsdifferent | 3-7 | 1-5 | 3-6 | 1-4 |
Formatdifferent | Workshop | Workshop + async | Workshop | Workshop + async |
Outputdifferent | Example Map, Acceptance Criteria, Open Questions | Context Diagram, Container Diagram, Component Diagram | Acceptance Criteria, Story Update | Architecture Document, Context View, Runtime View, Deployment View |
Tagsno overlap | Behavior-Driven DevelopmentRequirementsExamplesRefinement | ArchitectureCommunicationVisualization | AgileRequirementsRefinementBehavior-Driven Development | ArchitectureDocumentationCommunication |