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)Problem Framing WorkshopSAAM (Software Architecture Analysis Method)3-Circle Venn Diagram
| Criterion |  Architecture ATAM (Architecture Tradeoff Analysis Method) |  Facilitation Problem Framing Workshop |  Architecture SAAM (Software Architecture Analysis Method) |  Facilitation 3-Circle Venn Diagram |
|---|---|---|---|---|
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. | When a team works on symptoms but the real question stays fuzzy, a Problem Framing Workshop sharpens the view of the right problem. It separates observation, interpretation, and target picture from each other. | 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 three perspectives matter at the same time, a Three-Circle Venn Diagram shows the overlaps and remainders precisely. It makes visible where shared effect arises and where only a partial perspective applies. |
Complexitydifferent | High | Low | High | Low |
Timedifferent | Several meetings plus preparation and analysis; total effort depends on scope | 60-120 min | Preparation, scenario analysis, and findings review; effort depends on scope | 15-45 min |
Participantsdifferent | Evaluation team, architects, and relevant stakeholders | 4-10 | Architecture experts and stakeholders for scenarios and weighting | 2-8 |
Formatdifferent | Workshop + async | Workshop | 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 | Problem Statement, Scope Boundaries, Assumption List, Next Analysis Questions | 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 | Venn Diagram, Overlap Notes, Differentiators |
Tagsno overlap | ArchitectureQualityRiskTradeoffsStakeholders | FacilitationAlignmentDiscovery | ArchitectureChangeAnalysisComparisonQuality | ComparisonFacilitationAlignment |