View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:Fault IsolationStakeholder MappingSAAM (Software Architecture Analysis Method)ATAM (Architecture Tradeoff Analysis Method)
| Criterion |  Engineering Fault Isolation |  Facilitation Stakeholder Mapping |  Architecture SAAM (Software Architecture Analysis Method) |  Architecture ATAM (Architecture Tradeoff Analysis Method) |
|---|---|---|---|---|
Purposedifferent | In technical failures, the visible symptom often gets mixed up with the actual cause. Fault Isolation narrows the fault space and progressively reduces which part of the system is truly affected. | 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 | Medium | Low | High | High |
Timedifferent | 30-180 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 | 1-6 | 2-8 | Architecture experts and stakeholders for scenarios and weighting | Evaluation team, architects, and relevant stakeholders |
Formatsame | Workshop + async | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Fault Isolation Map, Test Log, Excluded Hypotheses, Narrowed Fault Area | 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 | TroubleshootingDiagnosisEngineering | StakeholdersAlignmentFacilitationChange | ArchitectureChangeAnalysisComparisonQuality | ArchitectureQualityRiskTradeoffsStakeholders |