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 |  Systems Thinking Intervention Mapping |  Systems Thinking Evaporating Cloud |  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. | Intervention Mapping translates a need for change into a planned, evaluable program. The method connects target group, determinants, actions, and measurement into a traceable chain. | The method makes visible why two seemingly incompatible demands arise and which assumption must be tested to resolve the conflict. | 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 | Medium | Low |
Timedifferent | 1-4 h | 1-5 Tage | 60-120 min | 1-2 Tage |
Participantsdifferent | 1-5 | 4-12 | 2-8 | 1-4 |
Formatdifferent | Workshop + async | Workshop + async | Workshop | Workshop + async |
Outputdifferent | Context Diagram, Container Diagram, Component Diagram | Logic Model, Change Objectives, Intervention Components, Evaluation Plan | Conflict Cloud, Assumption List, Breakthrough Ideas, Next Experiments | Architecture Document, Context View, Runtime View, Deployment View |
Tagsno overlap | ArchitectureCommunicationVisualization | ChangeSystems thinkingCapability | Theory of ConstraintsAssumptionsSystems thinking | ArchitectureDocumentationCommunication |