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 Force Field Analysis |  Architecture arc42 |  Decision Making Delphi Method |
|---|---|---|---|---|
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. | In change initiatives, supporting and restraining forces sit at the table at the same time. Force Field Analysis makes these tensions explicit and shows where change can be pushed forward by strengthening or relieving. | 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 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. |
Complexitydifferent | Low | Low | Low | High |
Timedifferent | 1-4 h | 45-90 min | 1-2 Tage | 1-4 Wochen |
Participantsdifferent | 1-5 | 3-12 | 1-4 | 6-30 Experten |
Formatdifferent | Workshop + async | Workshop | Workshop + async | Async |
Outputdifferent | Context Diagram, Container Diagram, Component Diagram | Force Field Map, Change Levers, Risk Notes | Architecture Document, Context View, Runtime View, Deployment View | Expert Forecast, Consensus Range, Assumption Notes |
Tagsno overlap | ArchitectureCommunicationVisualization | ChangeDecisionStrategy | ArchitectureDocumentationCommunication | ForecastingExpertsDecisionStrategy |