View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Systems Thinking Systems Mapping |  Architecture Architecture Decision Record |  Domain Modeling Context Map |  Architecture arc42 |
|---|---|---|---|---|
Purposedifferent | Systems Mapping arranges elements, relationships, and boundaries so a complex field becomes legible at a glance. The overview stabilizes the overall picture before detail work or steering begins. | An ADR permanently records an architecture decision with context, trade-offs, and consequence. It creates continuity for later changes because the decision path stays traceable. | When several contexts need to talk to each other, it makes their relationships and dependencies legible. It helps sort integration pressure and responsibilities across system boundaries. | 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 | Medium | Low | Medium | Low |
Timedifferent | 1-3 h | 15-45 min | 1-3 h | 1-2 Tage |
Participantsdifferent | 3-12 | 1-3 | 2-8 | 1-4 |
Formatdifferent | Workshop + async | Async | Workshop + async | Workshop + async |
Outputdifferent | System Map, Dependencies, Leverage Points | ADR File, Decision Log, Rationale | Context Map, Integration Patterns, Boundary Notes | Architecture Document, Context View, Runtime View, Deployment View |
Tagsno overlap | Systems thinkingMappingBoundariesChange | ArchitectureRationaleDocumentationGovernance | Domain-Driven DesignBoundariesStrategy | ArchitectureDocumentationCommunication |