View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Delivery Cost of Delay |  Architecture C4 Model |  Architecture Request for Comments |  Architecture arc42 |
|---|---|---|---|---|
Purposedifferent | Helps clarify scope, order, and delivery flow in concrete terms. It makes work, constraints, and sequence manageable. The result is captured as a Cost of Delay table and prioritization sequence. | 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. | 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. | 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 | High | Low | Medium | Low |
Timedifferent | 90-180 min | 1-4 h | 1-3 Wochen vom Draft bis zur Entscheidung | 1-2 Tage |
Participantsdifferent | 3-8 | 1-5 | 3-20 Reviewer | 1-4 |
Formatdifferent | Workshop | Workshop + async | Async | Workshop + async |
Outputdifferent | CoD Table, Prioritization Sequence | Context Diagram, Container Diagram, Component Diagram | RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets | Architecture Document, Context View, Runtime View, Deployment View |
Tagsno overlap | PrioritizationDeliveryEconomicsDecision | ArchitectureCommunicationVisualization | ArchitectureDecisionAsyncGovernance | ArchitectureDocumentationCommunication |