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 |  Facilitation Stakeholder Salience Model |  Architecture arc42 |  Facilitation Alignment Mapping |
|---|---|---|---|---|
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 stakeholders appear to matter very differently, the Stakeholder Salience Model rates their actual priority through power, legitimacy, and urgency. It turns individual contributions into a visible selection. The result is captured as a Salience diagram and a class-based strategy. | 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 several people work toward one goal but hold different mental maps, Alignment Mapping makes the discrepancies visible. It arranges goals, assumptions, and priorities so shared direction becomes verifiable. |
Complexitydifferent | Low | Medium | Low | Medium |
Timedifferent | 1-4 h | 60-90 min | 1-2 Tage | 1-2 h |
Participantsdifferent | 1-5 | 3-6 | 1-4 | 4-12 |
Formatdifferent | Workshop + async | Workshop | Workshop + async | Workshop |
Outputdifferent | Context Diagram, Container Diagram, Component Diagram | Salience Diagram, Strategy per Class | Architecture Document, Context View, Runtime View, Deployment View | Alignment Map, Open Issues, Decision Questions |
Tagsno overlap | ArchitectureCommunicationVisualization | StakeholdersFacilitationAlignmentGovernance | ArchitectureDocumentationCommunication | AlignmentStakeholdersStrategyFacilitation |