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 QuestionsQuality Attribute WorkshopFailure Mode and Effects AnalysisRisk Storming
| Criterion | ![]() Knowledge Modeling Competency Questions | ![]() Architecture Quality Attribute Workshop | ![]() Operations Failure Mode and Effects Analysis | ![]() Architecture Risk Storming |
|---|---|---|---|---|
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. | A Quality Attribute Workshop translates quality requirements into concrete scenarios and architecture impulses. The method brings product, engineering, and operations to the same view of desired properties. | 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. | Helps clarify architecture context, options, and consequences in concrete terms. It organizes technical context, alternatives, and consequences. The result is captured as an Annotated Diagram, a Prioritized Risk List, and an Action Backlog. |
Complexitydifferent | Medium | Medium | High | Low |
Timedifferent | 2-4 h | 2-4 h | 2-6 h | 60-90 min |
Participantsdifferent | 2-8 | 5-15 | 3-10 | 4-12 |
Formatdifferent | Workshop + async | Workshop | Workshop | Workshop |
Outputdifferent | Competency Question Set, Required Concepts, Test Queries, Coverage Matrix | Quality Scenarios, Priority List, Architecture Concerns | FMEA Table, Risk Priority, Mitigation Actions | Annotated Diagram, Prioritized Risk List, Action Backlog |
Tagsno overlap | OntologyKnowledge graphScopeRequirementsSemantic | RequirementsArchitectureWorkshop | RiskQualityOperationsRoot cause | RiskArchitectureWorkshopValidation |



