View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:SAAM (Software Architecture Analysis Method)Bounded Context CanvasForce Field AnalysisChange Analysis
| Criterion |  Architecture SAAM (Software Architecture Analysis Method) |  Domain Modeling Bounded Context Canvas |  Decision Making Force Field Analysis |  Operations Change Analysis |
|---|---|---|---|---|
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. | When a business context is still loosely outlined, it shapes language, responsibility, and integration space. It clarifies what belongs together and where a boundary needs to hold. | In change initiatives, supporting and restraining forces sit at the table at the same time. Force Field Analysis makes these tensions explicit and shows where change can be pushed forward by strengthening or relieving. | For a deviation after a change, the method isolates the influence of the altered condition. It narrows down which differences are relevant and which are just accompanying noise. |
Complexitydifferent | High | Medium | Low | Medium |
Timedifferent | Preparation, scenario analysis, and findings review; effort depends on scope | 1-3 h | 45-90 min | 45-120 min |
Participantsdifferent | Architecture experts and stakeholders for scenarios and weighting | 3-8 | 3-12 | 2-6 |
Formatdifferent | Workshop + async | 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 | Context Canvas, Glossary, Integration Notes | Force Field Map, Change Levers, Risk Notes | Change Matrix, Cause Hypotheses, Validation Questions, Action List |
Tagsno overlap | ArchitectureChangeAnalysisComparisonQuality | Domain-Driven DesignBoundariesModeling | ChangeDecisionStrategy | ChangeRoot causeTroubleshootingComparison |