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 C4 Model |  Agile Example Mapping |  Architecture arc42 |
|---|---|---|---|---|
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. | 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 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. | 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 | Medium | Low | Low | Low |
Timedifferent | 60-90 min pro Feature | 1-4 h | 30-60 min | 1-2 Tage |
Participantsdifferent | 3-6 | 1-5 | 3-7 | 1-4 |
Formatdifferent | Workshop | Workshop + async | Workshop | Workshop + async |
Outputdifferent | Example Table, Acceptance Tests | Context Diagram, Container Diagram, Component Diagram | Example Map, Acceptance Criteria, Open Questions | Architecture Document, Context View, Runtime View, Deployment View |
Tagsno overlap | AgileRequirementsExamplesBehavior-Driven Development | ArchitectureCommunicationVisualization | Behavior-Driven DevelopmentRequirementsExamplesRefinement | ArchitectureDocumentationCommunication |