View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Engineering Fault Isolation |  Delivery RAID Log |  Business Strategy Value Chain Analysis |  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. | 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. | Value Chain Analysis shows where value is created, costs accrue, and differentiation becomes possible along the process. It compares strengths, risks, market logic, and courses of action. The result is captured as a value-chain map and lever list. | 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 | 30 min Setup, dann laufend | Half day | Several meetings plus preparation and analysis; total effort depends on scope |
Participantsdifferent | 1-6 | 1-3 maintaining, briefing for everyone | 3-8 | Evaluation team, architects, and relevant stakeholders |
Formatdifferent | Workshop + async | Async | Workshop | Workshop + async |
Outputdifferent | Fault Isolation Map, Test Log, Excluded Hypotheses, Narrowed Fault Area | RAID Log, Status Report Source | Value Chain Map, Lever List | 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 | RiskTrackingStakeholdersGovernance | StrategyBusiness modelDiagnosisAnalysis | ArchitectureQualityRiskTradeoffsStakeholders |