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)Example MappingFailure Mode and Effects AnalysisSpecification by Example
| Criterion |  Architecture ATAM (Architecture Tradeoff Analysis Method) |  Agile Example Mapping |  Operations Failure Mode and Effects Analysis |  Agile Specification by Example |
|---|---|---|---|---|
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. | When a story carries business rules and exceptions, it brings clarity before implementation. It makes examples, open questions, and boundaries visible enough that the logic becomes jointly sound. | 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. | 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. |
Complexitydifferent | High | Low | High | Medium |
Timedifferent | Several meetings plus preparation and analysis; total effort depends on scope | 30-60 min | 2-6 h | 60-90 min pro Feature |
Participantsdifferent | Evaluation team, architects, and relevant stakeholders | 3-7 | 3-10 | 3-6 |
Formatdifferent | Workshop + async | Workshop | Workshop | Workshop |
Outputdifferent | Prioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigations | Example Map, Acceptance Criteria, Open Questions | FMEA Table, Risk Priority, Mitigation Actions | Example Table, Acceptance Tests |
Tagsno overlap | ArchitectureQualityRiskTradeoffsStakeholders | Behavior-Driven DevelopmentRequirementsExamplesRefinement | RiskQualityOperationsRoot cause | AgileRequirementsExamplesBehavior-Driven Development |