View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:ATAM (Architecture Tradeoff Analysis Method)Intervention MappingSAAM (Software Architecture Analysis Method)CATWOE Analysis
| Criterion |  Architecture ATAM (Architecture Tradeoff Analysis Method) |  Systems Thinking Intervention Mapping |  Architecture SAAM (Software Architecture Analysis Method) |  Systems Thinking CATWOE Analysis |
|---|---|---|---|---|
Purposedifferent | ATAM helps teams weigh architecture decisions when quality goals compete. The team considers business goals, stakeholder expectations, and technical decisions together. The evaluation shows which risks need further investigation. | Intervention Mapping translates a need for change into a planned, evaluable program. The method connects target group, determinants, actions, and measurement into a traceable chain. | 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. | CATWOE structures a problem from six viewpoints and prevents too narrow a view of the situation. Different experiences of the system become comparably discussable this way. |
Complexitydifferent | High | High | High | Medium |
Timedifferent | Several meetings plus preparation and analysis; total effort depends on scope | 1-5 Tage | Preparation, scenario analysis, and findings review; effort depends on scope | 45-90 min |
Participantsdifferent | Evaluation team, architects, and relevant stakeholders | 4-12 | Architecture experts and stakeholders for scenarios and weighting | 3-8 |
Formatsame | Workshop + async | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Prioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigations | Logic Model, Change Objectives, Intervention Components, Evaluation Plan | 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 | CATWOE Canvas, Root Definition, Stakeholder Perspectives, Constraints |
Tagsno overlap | ArchitectureQualityRiskTradeoffsStakeholders | ChangeSystems thinkingCapability | ArchitectureChangeAnalysisComparisonQuality | Systems thinkingFramingStakeholders |