View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:ATAM (Architecture Tradeoff Analysis Method)Competency QuestionsSpecification by ExampleLinked Open Terms
| Criterion |  Architecture ATAM (Architecture Tradeoff Analysis Method) |  Knowledge Modeling Competency Questions |  Agile Specification by Example |  Knowledge Modeling Linked Open Terms |
|---|---|---|---|---|
Purposedifferent | 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. | 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. | When business rules need to become precise, it ties language, example, and test together. It sorts work by value, risk, and delivery ability. The result is captured as an Example Table and Acceptance Tests. | Linked Open Terms connects terminology work with linked-data thinking and makes terminology technically connectable. Vocabulary, meanings, and references can thereby be maintained consistently. |
Complexitydifferent | High | Medium | Medium | Medium |
Timedifferent | Several meetings plus preparation and analysis; total effort depends on scope | 2-4 h | 60-90 min pro Feature | Wochen bis Monate |
Participantsdifferent | Evaluation team, architects, and relevant stakeholders | 2-8 | 3-6 | 2-8 |
Formatdifferent | Workshop + async | Workshop + async | Workshop | Workshop + async |
Outputdifferent | Prioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigations | Competency Question Set, Required Concepts, Test Queries, Coverage Matrix | Example Table, Acceptance Tests | Ontology Requirements, Conceptual Model, Published Ontology, Documentation, Maintenance Plan |
Tagsno overlap | ArchitectureQualityRiskTradeoffsStakeholders | OntologyKnowledge graphScopeRequirementsSemantic | AgileRequirementsExamplesBehavior-Driven Development | OntologyMethodologyAgileSemantic |