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 Quality Attribute Workshop | ![]() Knowledge Modeling NeOn Methodology | ![]() Architecture Risk Storming | ![]() Knowledge Modeling Competency Questions |
|---|---|---|---|---|
Purposedifferent | 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. | The NeOn Methodology structures ontology work as a controlled process with reuse, scenarios, and reviews. It is useful when ontologies should not emerge ad hoc but modularly and reusably. | 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. | 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. |
Complexitydifferent | Medium | High | Low | Medium |
Timedifferent | 2-4 h | Mehrere Wochen bis Monate | 60-90 min | 2-4 h |
Participantsdifferent | 5-15 | 2-10 | 4-12 | 2-8 |
Formatdifferent | Workshop | Workshop + async | Workshop | Workshop + async |
Outputdifferent | Quality Scenarios, Priority List, Architecture Concerns | Ontology Requirements Specification, Reuse Plan, Ontology Modules, Evaluation Report | Annotated Diagram, Prioritized Risk List, Action Backlog | Competency Question Set, Required Concepts, Test Queries, Coverage Matrix |
Tagsno overlap | RequirementsArchitectureWorkshop | OntologyMethodologyReuseSemanticEngineering | RiskArchitectureWorkshopValidation | OntologyKnowledge graphScopeRequirementsSemantic |



