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 C4 Model |  Decision Making PERT Estimation |  Delivery RAID Log |  Architecture Architecture Decision Record |
|---|---|---|---|---|
Purposedifferent | 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. | On complex initiatives, a plain average tends to understate just how uncertain the outcome really is. It separates options, evaluation criteria, and open risks. The result is captured as a PERT Estimate, Expected Value, and Risk Notes. | Helps clarify scope, sequence, and delivery flow in concrete terms. It makes work, boundaries, and order steerable. The result is captured as a RAID Log and a source for status reporting. | An ADR permanently records an architecture decision with context, trade-offs, and consequence. It creates continuity for later changes because the decision path stays traceable. |
Complexitydifferent | Low | Medium | Low | Low |
Timedifferent | 1-4 h | 15-45 min | 30 min Setup, dann laufend | 15-45 min |
Participantsdifferent | 1-5 | 1-8 | 1-3 maintaining, briefing for everyone | 1-3 |
Formatdifferent | Workshop + async | Workshop + async | Async | Async |
Outputdifferent | Context Diagram, Container Diagram, Component Diagram | PERT Estimate, Expected Value, Risk Notes | RAID Log, Status Report Source | ADR File, Decision Log, Rationale |
Tagsno overlap | ArchitectureCommunicationVisualization | EstimationUncertaintyRisk | RiskTrackingStakeholdersGovernance | ArchitectureRationaleDocumentationGovernance |