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 QuestionsRAID LogOntology Design PatternsATAM (Architecture Tradeoff Analysis Method)
| Criterion |  Knowledge Modeling Competency Questions |  Delivery RAID Log |  Knowledge Modeling Ontology Design Patterns |  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. | Helps clarify scope, sequence, and delivery flow in concrete terms. It makes work, boundaries, and order steerable. The result is captured as a RAID Log and a source for status reporting. | Ontology Design Patterns provide reusable building blocks for recurring modeling problems. The method brings structure to the search for clean concepts, relationships, and roles. | 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 | Low | Medium | High |
Timedifferent | 2-4 h | 30 min Setup, dann laufend | 1-3 h pro Pattern | Several meetings plus preparation and analysis; total effort depends on scope |
Participantsdifferent | 2-8 | 1-3 maintaining, briefing for everyone | 1-6 | Evaluation team, architects, and relevant stakeholders |
Formatdifferent | Workshop + async | Async | Workshop + async | Workshop + async |
Outputdifferent | Competency Question Set, Required Concepts, Test Queries, Coverage Matrix | RAID Log, Status Report Source | Selected Patterns, Adapted Schema Fragments, Pattern Documentation | 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 | RiskTrackingStakeholdersGovernance | OntologyPatternsReuseSemanticModeling | ArchitectureQualityRiskTradeoffsStakeholders |