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 arc42 |  UX Research Empathy Mapping |  Domain Modeling EventStorming |  Architecture Architecture Decision Record |
|---|---|---|---|---|
Purposedifferent | 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 a lot is assumed about a target group but little is seen jointly, empathy mapping makes knowledge and gaps directly comparable. The picture also shows which assumptions hold up and where evidence is missing. | When a domain consists of many events, rules, and states, it creates a shared modeling space for the team. It bundles language, flows, and boundaries before domain knowledge fragments into siloed views. | 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. |
Complexitydifferent | Low | Low | Medium | Low |
Timedifferent | 1-2 Tage | 30–60 min | 2-8 h | 15-45 min |
Participantsdifferent | 1-4 | 4-8 | 5-12 | 1-3 |
Formatdifferent | Workshop + async | Workshop | Workshop | Async |
Outputdifferent | Architecture Document, Context View, Runtime View, Deployment View | Empathy Map, Assumptions List, Research Gaps | Event Timeline, Ubiquitous Language, Boundaries, Open Questions | ADR File, Decision Log, Rationale |
Tagsno overlap | ArchitectureDocumentationCommunication | SynthesisQualitativeWorkshop | Domain-Driven DesignEventsDiscoveryWorkshop | ArchitectureRationaleDocumentationGovernance |