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 SAAM (Software Architecture Analysis Method) |  Business Strategy Value Chain Analysis |  Domain Modeling Context Map |
|---|---|---|---|
Purposedifferent | 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. | Value Chain Analysis shows where value is created, costs accrue, and differentiation becomes possible along the process. It compares strengths, risks, market logic, and courses of action. The result is captured as a value-chain map and lever list. | 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. |
Complexitydifferent | High | High | Medium |
Timedifferent | Preparation, scenario analysis, and findings review; effort depends on scope | Half day | 1-3 h |
Participantsdifferent | Architecture experts and stakeholders for scenarios and weighting | 3-8 | 2-8 |
Formatdifferent | Workshop + async | Workshop | Workshop + async |
Outputdifferent | 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 | Value Chain Map, Lever List | Context Map, Integration Patterns, Boundary Notes |
Tagsno overlap | ArchitectureChangeAnalysisComparisonQuality | StrategyBusiness modelDiagnosisAnalysis | Domain-Driven DesignBoundariesStrategy |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
