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 |  Business Strategy Scenario Planning |  Architecture arc42 |  Business Strategy GAP Analysis |
|---|---|---|---|---|
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. | Scenario Planning opens the view to several plausible futures instead of a single forecast. The method protects strategies from depending on too narrow an expected path. | 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. | GAP Analysis compares the current state with a target picture and makes the distance manageable. It becomes useful when, ahead of new initiatives, it must become clear which capabilities, processes, or resources are missing. |
Complexitydifferent | Low | High | Low | Medium |
Timedifferent | 1-4 h | 0.5-2 Tage | 1-2 Tage | 1-3 h |
Participantsdifferent | 1-5 | 4-12 | 1-4 | 2-8 |
Formatdifferent | Workshop + async | Workshop | Workshop + async | Workshop + async |
Outputdifferent | Context Diagram, Container Diagram, Component Diagram | Scenario Set, Strategic Implications, Robust Options | Architecture Document, Context View, Runtime View, Deployment View | Gap Matrix, Action Plan, Risk Notes |
Tagsno overlap | ArchitectureCommunicationVisualization | StrategyUncertaintyPlanning | ArchitectureDocumentationCommunication | StrategyAnalysisPlanning |