View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:Problem Framing WorkshopStakeholder MappingSAAM (Software Architecture Analysis Method)ATAM (Architecture Tradeoff Analysis Method)
| Criterion |  Facilitation Problem Framing Workshop |  Facilitation Stakeholder Mapping |  Architecture SAAM (Software Architecture Analysis Method) |  Architecture ATAM (Architecture Tradeoff Analysis Method) |
|---|---|---|---|---|
Purposedifferent | 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. | When an initiative depends on many people, interests, and power dynamics, Stakeholder Mapping systematically orders the environment. It shows who influences, who is affected, and where relationship management or safeguarding matters first. | 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. | 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. |
Complexitydifferent | Low | Low | High | High |
Timedifferent | 60-120 min | 60–90 min | Preparation, scenario analysis, and findings review; effort depends on scope | Several meetings plus preparation and analysis; total effort depends on scope |
Participantsdifferent | 4-10 | 2-8 | Architecture experts and stakeholders for scenarios and weighting | Evaluation team, architects, and relevant stakeholders |
Formatdifferent | Workshop | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Problem Statement, Scope Boundaries, Assumption List, Next Analysis Questions | Stakeholder Map, Engagement Plan, Risk 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 | Prioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigations |
Tagsno overlap | FacilitationAlignmentDiscovery | StakeholdersAlignmentFacilitationChange | ArchitectureChangeAnalysisComparisonQuality | ArchitectureQualityRiskTradeoffsStakeholders |