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 Delphi Method |  Architecture Risk Storming |  Architecture arc42 |
|---|---|---|---|---|
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. | When knowledge is distributed and direct dominance should be avoided, groups quickly fall under the sway of their opinion leaders. The Delphi Method gathers assessments iteratively and gradually brings expert judgments closer together. | Helps clarify architecture context, options, and consequences in concrete terms. It organizes technical context, alternatives, and consequences. The result is captured as an Annotated Diagram, a Prioritized Risk List, and an Action Backlog. | 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 | Low | High | Low | Low |
Timedifferent | 1-4 h | 1-4 Wochen | 60-90 min | 1-2 Tage |
Participantsdifferent | 1-5 | 6-30 Experten | 4-12 | 1-4 |
Formatdifferent | Workshop + async | Async | Workshop | Workshop + async |
Outputdifferent | Context Diagram, Container Diagram, Component Diagram | Expert Forecast, Consensus Range, Assumption Notes | Annotated Diagram, Prioritized Risk List, Action Backlog | Architecture Document, Context View, Runtime View, Deployment View |
Tagsno overlap | ArchitectureCommunicationVisualization | ForecastingExpertsDecisionStrategy | RiskArchitectureWorkshopValidation | ArchitectureDocumentationCommunication |