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 Request for Comments |  Architecture Architecture Communication Canvas |  Agile Specification by Example |  Architecture arc42 |
|---|---|---|---|---|
Purposedifferent | An RFC clarifies architecture context, options, and consequences. It structures technical context, alternatives, tradeoffs, open questions, and review feedback, and captures the result as an RFC document, reviewer comments, and a decision rationale. | The Architecture Communication Canvas plans architecture communication so the right people receive the right message. The method turns technical complexity into deliberate communication design. | 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 | Medium | Medium | Medium | Low |
Timedifferent | 1-3 Wochen vom Draft bis zur Entscheidung | 60-120 min | 60-90 min pro Feature | 1-2 Tage |
Participantsdifferent | 3-20 Reviewer | 2-8 | 3-6 | 1-4 |
Formatdifferent | Async | Workshop + async | Workshop | Workshop + async |
Outputdifferent | RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets | Communication Canvas, Stakeholder Messages, Architecture Communication Plan | Example Table, Acceptance Tests | Architecture Document, Context View, Runtime View, Deployment View |
Tagsno overlap | ArchitectureDecisionAsyncGovernance | ArchitectureCommunicationStakeholdersCanvas | AgileRequirementsExamplesBehavior-Driven Development | ArchitectureDocumentationCommunication |