View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Architecture SAAM (Software Architecture Analysis Method) |  Decision Making Assumption Surfacing |  Operations Fishbone Diagram |
|---|---|---|---|
Purposedifferent | 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. | Plans often contain assumptions that were never openly stated and remain dangerous precisely because of that. Assumption Surfacing makes these silent premises visible and prioritizes which of them carry the initiative or could sink it. | When a problem has several possible contributing factors, the method sorts causes by cause areas. It prevents an initial hunch from blocking the view of other plausible drivers. |
Complexitydifferent | High | Low | Low |
Timedifferent | Preparation, scenario analysis, and findings review; effort depends on scope | 45-90 min | 30-60 min |
Participantsdifferent | Architecture experts and stakeholders for scenarios and weighting | 2-8 | 2-8 |
Formatdifferent | Workshop + async | Workshop + async | Workshop |
Outputdifferent | 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 | Assumption List, Critical Assumptions, Learning Plan | Fishbone Diagram, Cause Categories, Investigation Backlog |
Tagsno overlap | ArchitectureChangeAnalysisComparisonQuality | AssumptionsRiskDecisionDiscovery | Root causeQualityOperations |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
