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 ATAM (Architecture Tradeoff Analysis Method) |  Architecture arc42 |  Operations Runbook |  Operations Failure Mode and Effects Analysis |
|---|---|---|---|---|
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. | arc42 structures architecture knowledge so teams can document system, decisions, and risks consistently. The template builds a living understanding of the architecture instead of scattered notes. | For recurring operational tasks or incidents, the method keeps solid action logic ready. It reduces uncertainty when time pressure, role changes, or rare situations demand fast access. | 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 | High | Low | Low | High |
Timedifferent | Several meetings plus preparation and analysis; total effort depends on scope | 1-2 Tage | 20-60 min | 2-6 h |
Participantsdifferent | Evaluation team, architects, and relevant stakeholders | 1-4 | 1-4 | 3-10 |
Formatdifferent | Workshop + async | Workshop + async | Async | 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 | Architecture Document, Context View, Runtime View, Deployment View | Runbook, Checklist, Escalation Path | FMEA Table, Risk Priority, Mitigation Actions |
Tagsno overlap | ArchitectureQualityRiskTradeoffsStakeholders | ArchitectureDocumentationCommunication | OperationsReliabilityDocumentation | RiskQualityOperationsRoot cause |