View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Domain Modeling Context Map |  Architecture SAAM (Software Architecture Analysis Method) |  Architecture Architecture Decision Record |
|---|---|---|---|
Purposedifferent | 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. | SAAM helps teams judge an architecture’s suitability for selected tasks and changes. It is particularly useful for examining modifiability and comparing architecture alternatives with clear reasoning. | 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 | Medium | High | Low |
Timedifferent | 1-3 h | Preparation, scenario analysis, and findings review; effort depends on scope | 15-45 min |
Participantsdifferent | 2-8 | Architecture experts and stakeholders for scenarios and weighting | 1-3 |
Formatdifferent | Workshop + async | Workshop + async | Async |
Outputdifferent | Context Map, Integration Patterns, Boundary Notes | Domain functions mapped to components and connections, Quality attributes and evaluation criteria, Typical tasks and their effects on the architecture, Reasoned evaluation or comparison of alternatives | ADR File, Decision Log, Rationale |
Tagsno overlap | Domain-Driven DesignBoundariesStrategy | ArchitectureChangeAnalysisComparisonQuality | ArchitectureRationaleDocumentationGovernance |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
