View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:Architecture Decision RecordCompetency QuestionsFailure Mode and Effects AnalysisATAM (Architecture Tradeoff Analysis Method)
| Criterion |  Architecture Architecture Decision Record |  Knowledge Modeling Competency Questions |  Operations Failure Mode and Effects Analysis |  Architecture ATAM (Architecture Tradeoff Analysis Method) |
|---|---|---|---|---|
Purposedifferent | An ADR permanently records an architecture decision with context, trade-offs, and consequence. It creates continuity for later changes because the decision path stays traceable. | Competency Questions translate a domain model into concrete questions that it must be able to answer. The method keeps the model's scope clean and prevents pretty but useless structures. | 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. | 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 | Low | Medium | High | High |
Timedifferent | 15-45 min | 2-4 h | 2-6 h | Several meetings plus preparation and analysis; total effort depends on scope |
Participantsdifferent | 1-3 | 2-8 | 3-10 | Evaluation team, architects, and relevant stakeholders |
Formatdifferent | Async | Workshop + async | Workshop | Workshop + async |
Outputdifferent | ADR File, Decision Log, Rationale | Competency Question Set, Required Concepts, Test Queries, Coverage Matrix | FMEA Table, Risk Priority, Mitigation Actions | 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 | ArchitectureRationaleDocumentationGovernance | OntologyKnowledge graphScopeRequirementsSemantic | RiskQualityOperationsRoot cause | ArchitectureQualityRiskTradeoffsStakeholders |