View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:Change AnalysisSpecification by ExampleATAM (Architecture Tradeoff Analysis Method)Failure Mode and Effects Analysis
| Criterion |  Operations Change Analysis |  Agile Specification by Example |  Architecture ATAM (Architecture Tradeoff Analysis Method) |  Operations Failure Mode and Effects Analysis |
|---|---|---|---|---|
Purposedifferent | For a deviation after a change, the method isolates the influence of the altered condition. It narrows down which differences are relevant and which are just accompanying noise. | When business rules need to become precise, it ties language, example, and test together. It sorts work by value, risk, and delivery ability. The result is captured as an Example Table and Acceptance Tests. | 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. | For a process, product, or service with noticeable failure risks, the method assesses possible failure modes in advance. It directs attention to combinations of occurrence, effect, and detectability. |
Complexitydifferent | Medium | Medium | High | High |
Timedifferent | 45-120 min | 60-90 min pro Feature | Several meetings plus preparation and analysis; total effort depends on scope | 2-6 h |
Participantsdifferent | 2-6 | 3-6 | Evaluation team, architects, and relevant stakeholders | 3-10 |
Formatdifferent | Workshop + async | Workshop | Workshop + async | Workshop |
Outputdifferent | Change Matrix, Cause Hypotheses, Validation Questions, Action List | Example Table, Acceptance Tests | Prioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigations | FMEA Table, Risk Priority, Mitigation Actions |
Tagsno overlap | ChangeRoot causeTroubleshootingComparison | AgileRequirementsExamplesBehavior-Driven Development | ArchitectureQualityRiskTradeoffsStakeholders | RiskQualityOperationsRoot cause |