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 C4 Model |  Decision Making Constraint Analysis |  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 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 an initiative stalls, the limit often lies not in the idea but in hard or soft boundary conditions. Constraint Analysis separates these limits and shows which of them can actually be shaped. | 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 | 1-3 Wochen vom Draft bis zur Entscheidung | 1-4 h | 30-90 min | 1-2 Tage |
Participantsdifferent | 3-20 Reviewer | 1-5 | 2-8 | 1-4 |
Formatdifferent | Async | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets | Context Diagram, Container Diagram, Component Diagram | Constraint List, Hard/Soft Classification, Option Impact Notes, Decision Boundaries | Architecture Document, Context View, Runtime View, Deployment View |
Tagsno overlap | ArchitectureDecisionAsyncGovernance | ArchitectureCommunicationVisualization | ConstraintsDecisionPlanningOptions | ArchitectureDocumentationCommunication |