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 Architecture Decision Record |  Decision Making Constraint Analysis |  Architecture arc42 |  Decision Making Argument Mapping |
|---|---|---|---|---|
Purposedifferent | 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 an initiative stalls, the limit often lies not in the idea but in hard or soft boundary conditions. Constraint Analysis separates these limits and shows which of them can actually be shaped. | 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 statements, evidence, and counterarguments get mixed up, a debate quickly loses its structure. Argument Mapping breaks a thesis down into its reasoning and makes visible what it really rests on. |
Complexitydifferent | Low | Low | Low | Medium |
Timedifferent | 15-45 min | 30-90 min | 1-2 Tage | 1-3 h |
Participantsdifferent | 1-3 | 2-8 | 1-4 | 1-8 |
Formatdifferent | Async | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | ADR File, Decision Log, Rationale | Constraint List, Hard/Soft Classification, Option Impact Notes, Decision Boundaries | Architecture Document, Context View, Runtime View, Deployment View | Argument Map, Evidence Gaps, Decision Rationale |
Tagsno overlap | ArchitectureRationaleDocumentationGovernance | ConstraintsDecisionPlanningOptions | ArchitectureDocumentationCommunication | SensemakingDecisionRationale |