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 RAID Log |  Architecture arc42 |  Decision Making PERT Estimation |  Architecture C4 Model |
|---|---|---|---|---|
Purposedifferent | 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. | 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. | 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. | 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 | Low | Low | Medium | Low |
Timedifferent | 30 min Setup, dann laufend | 1-2 Tage | 15-45 min | 1-4 h |
Participantsdifferent | 1-3 maintaining, briefing for everyone | 1-4 | 1-8 | 1-5 |
Formatdifferent | Async | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | RAID Log, Status Report Source | Architecture Document, Context View, Runtime View, Deployment View | PERT Estimate, Expected Value, Risk Notes | Context Diagram, Container Diagram, Component Diagram |
Tagsno overlap | RiskTrackingStakeholdersGovernance | ArchitectureDocumentationCommunication | EstimationUncertaintyRisk | ArchitectureCommunicationVisualization |