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 Three Amigos |  Architecture C4 Model |  Agile Specification by Example |  Architecture arc42 |
|---|---|---|---|---|
Purposedifferent | When story, test, and implementation could drift apart, it brings business perspective, engineering, and quality together early. It prevents a story from being read differently only late in the process. | 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. | 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 | Low | Medium | Low |
Timedifferent | 15-30 min | 1-4 h | 60-90 min pro Feature | 1-2 Tage |
Participantsdifferent | 3 | 1-5 | 3-6 | 1-4 |
Formatdifferent | Workshop + async | Workshop + async | Workshop | Workshop + async |
Outputdifferent | Clarified Story, Test Examples, Open Questions | Context Diagram, Container Diagram, Component Diagram | Example Table, Acceptance Tests | Architecture Document, Context View, Runtime View, Deployment View |
Tagsno overlap | CollaborationBehavior-Driven DevelopmentQualityRefinement | ArchitectureCommunicationVisualization | AgileRequirementsExamplesBehavior-Driven Development | ArchitectureDocumentationCommunication |