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 Architecture Communication Canvas |  Architecture C4 Model |  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 Architecture Communication Canvas plans architecture communication so the right people receive the right message. The method turns technical complexity into deliberate communication design. | 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. | 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 | Medium | Low | Low |
Timedifferent | 60-90 min pro Feature | 60-120 min | 1-4 h | 1-2 Tage |
Participantsdifferent | 3-6 | 2-8 | 1-5 | 1-4 |
Formatdifferent | Workshop | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Example Table, Acceptance Tests | Communication Canvas, Stakeholder Messages, Architecture Communication Plan | Context Diagram, Container Diagram, Component Diagram | Architecture Document, Context View, Runtime View, Deployment View |
Tagsno overlap | AgileRequirementsExamplesBehavior-Driven Development | ArchitectureCommunicationStakeholdersCanvas | ArchitectureCommunicationVisualization | ArchitectureDocumentationCommunication |