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 MethodologyStakeholder Salience ModelRAID Log
| Criterion |  Architecture ATAM (Architecture Tradeoff Analysis Method) |  Systems Thinking Soft Systems Methodology |  Facilitation Stakeholder Salience Model |  Delivery RAID Log |
|---|---|---|---|---|
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. | Helps clarify scope, sequence, and delivery flow in concrete terms. It makes work, boundaries, and order steerable. The result is captured as a RAID Log and a source for status reporting. |
Complexitydifferent | High | High | Medium | Low |
Timedifferent | Several meetings plus preparation and analysis; total effort depends on scope | 0.5-3 Tage | 60-90 min | 30 min Setup, dann laufend |
Participantsdifferent | Evaluation team, architects, and relevant stakeholders | 5-15 | 3-6 | 1-3 maintaining, briefing for everyone |
Formatdifferent | Workshop + async | Workshop | 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 | Rich Picture, Root Definitions, Conceptual Models, Change Agenda | Salience Diagram, Strategy per Class | RAID Log, Status Report Source |
Tagsno overlap | ArchitectureQualityRiskTradeoffsStakeholders | Soft systemsComplexitySensemakingSystems thinking | StakeholdersFacilitationAlignmentGovernance | RiskTrackingStakeholdersGovernance |