View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:Competency QuestionsFailure Mode and Effects AnalysisScatter DiagramATAM (Architecture Tradeoff Analysis Method)
| Criterion | ![]() Knowledge Modeling Competency Questions | ![]() Operations Failure Mode and Effects Analysis | ![]() Operations Scatter Diagram | ![]() Architecture ATAM (Architecture Tradeoff Analysis Method) |
|---|---|---|---|---|
Purposedifferent | 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. | When the question is whether two measures are related, the method makes patterns in the data picture visible. It separates felt correlations from relationships that actually show up in the data. | 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 | High | Low | High |
Timedifferent | 2-4 h | 2-6 h | 30-90 min | Several meetings plus preparation and analysis; total effort depends on scope |
Participantsdifferent | 2-8 | 3-10 | 1-4 | Evaluation team, architects, and relevant stakeholders |
Formatdifferent | Workshop + async | Workshop | Workshop + async | Workshop + async |
Outputdifferent | Competency Question Set, Required Concepts, Test Queries, Coverage Matrix | FMEA Table, Risk Priority, Mitigation Actions | Scatter Plot, Korrelationsnotiz, Hypothesenliste | 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 | OntologyKnowledge graphScopeRequirementsSemantic | RiskQualityOperationsRoot cause | Root causeQualityVisualization | ArchitectureQualityRiskTradeoffsStakeholders |



