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 |  Architecture arc42 |  Agile NoEstimates |  Decision Making Three-Point Estimation |
|---|---|---|---|---|
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. | 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. | When estimating slows a team down more than it helps, it shifts the focus to flow, small slices, and real lead time. It sorts work by value, risk, and delivery ability. The result is captured as Throughput Data, Flow Forecast, and Slicing Rules. | A single estimate for effort, time, or risk often looks too smooth for the real uncertainty behind it. It separates options, evaluation criteria, and open risks. The result is captured as a Three-Point Estimate, Risk Range, and Assumption Notes. |
Complexitydifferent | Low | Low | Medium | Medium |
Timedifferent | 1-4 h | 1-2 Tage | laufend | 10-30 min je Item |
Participantsdifferent | 1-5 | 1-4 | 2-12 | 1-8 |
Formatsame | Workshop + async | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Context Diagram, Container Diagram, Component Diagram | Architecture Document, Context View, Runtime View, Deployment View | Throughput Data, Flow Forecast, Slicing Rules | Three-Point Estimate, Risk Range, Assumption Notes |
Tagsno overlap | ArchitectureCommunicationVisualization | ArchitectureDocumentationCommunication | EstimationForecastingFlow | EstimationUncertaintyForecasting |