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 Competency Questions | ![]() Architecture Architecture Decision Record | ![]() Knowledge Modeling NeOn Methodology |
|---|---|---|---|---|
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. | 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. | 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. | 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. |
Complexitydifferent | Medium | Medium | Low | High |
Timedifferent | 2-4 h | 2-4 h | 15-45 min | Mehrere Wochen bis Monate |
Participantsdifferent | 5-15 | 2-8 | 1-3 | 2-10 |
Formatdifferent | Workshop | Workshop + async | Async | Workshop + async |
Outputdifferent | Quality Scenarios, Priority List, Architecture Concerns | Competency Question Set, Required Concepts, Test Queries, Coverage Matrix | ADR File, Decision Log, Rationale | Ontology Requirements Specification, Reuse Plan, Ontology Modules, Evaluation Report |
Tagsno overlap | RequirementsArchitectureWorkshop | OntologyKnowledge graphScopeRequirementsSemantic | ArchitectureRationaleDocumentationGovernance | OntologyMethodologyReuseSemanticEngineering |



