Compare

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)Soft Systems Methodology Stakeholder Salience Model

Criterion	Architecture ATAM (Architecture Tradeoff Analysis Method)	Systems Thinking Soft Systems Methodology	Facilitation Stakeholder Salience Model
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.	Soft Systems Methodology helps explore unclear or politically charged problems systematically. Instead of forcing a quick answer, the method builds a shared understanding of perspectives and room for action.	When stakeholders appear to matter very differently, the Stakeholder Salience Model rates their actual priority through power, legitimacy, and urgency. It turns individual contributions into a visible selection. The result is captured as a Salience diagram and a class-based strategy.
Complexitydifferent	High	High	Medium
Timedifferent	Several meetings plus preparation and analysis; total effort depends on scope	0.5-3 Tage	60-90 min
Participantsdifferent	Evaluation team, architects, and relevant stakeholders	5-15	3-6
Formatdifferent	Workshop + async	Workshop	Workshop
Outputdifferent	Prioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigations	Rich Picture, Root Definitions, Conceptual Models, Change Agenda	Salience Diagram, Strategy per Class
Tagsno overlap	ArchitectureQualityRiskTradeoffsStakeholders	Soft systemsComplexitySensemakingSystems thinking	StakeholdersFacilitationAlignmentGovernance