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 |  Delivery Communication Plan |  Decision Making Constraint Analysis |  Architecture C4 Model |
|---|---|---|---|---|
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. | When many people need to be informed in parallel and messages would otherwise arrive unevenly or too late, a Communication Plan orders communication reliably. Channels, audiences, and cadences interlock so important information doesn't get lost. | 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. | 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. |
Complexitydifferent | Medium | Low | Low | Low |
Timedifferent | 1-3 Wochen vom Draft bis zur Entscheidung | 45-90 min | 30-90 min | 1-4 h |
Participantsdifferent | 3-20 Reviewer | 2-6 | 2-8 | 1-5 |
Formatdifferent | Async | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets | Communication Plan, Channel Matrix, Message Cadence | Constraint List, Hard/Soft Classification, Option Impact Notes, Decision Boundaries | Context Diagram, Container Diagram, Component Diagram |
Tagsno overlap | ArchitectureDecisionAsyncGovernance | CommunicationStakeholdersDeliveryPlanning | ConstraintsDecisionPlanningOptions | ArchitectureCommunicationVisualization |