View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:NeOn MethodologyExample MappingATAM (Architecture Tradeoff Analysis Method)Linked Open Terms
| Criterion |  Knowledge Modeling NeOn Methodology |  Agile Example Mapping |  Architecture ATAM (Architecture Tradeoff Analysis Method) |  Knowledge Modeling Linked Open Terms |
|---|---|---|---|---|
Purposedifferent | 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. | When a story carries business rules and exceptions, it brings clarity before implementation. It makes examples, open questions, and boundaries visible enough that the logic becomes jointly sound. | 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. | 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 | Low | High | Medium |
Timedifferent | Mehrere Wochen bis Monate | 30-60 min | Several meetings plus preparation and analysis; total effort depends on scope | Wochen bis Monate |
Participantsdifferent | 2-10 | 3-7 | Evaluation team, architects, and relevant stakeholders | 2-8 |
Formatdifferent | Workshop + async | Workshop | Workshop + async | Workshop + async |
Outputdifferent | Ontology Requirements Specification, Reuse Plan, Ontology Modules, Evaluation Report | Example Map, Acceptance Criteria, Open Questions | Prioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigations | Ontology Requirements, Conceptual Model, Published Ontology, Documentation, Maintenance Plan |
Tagsno overlap | OntologyMethodologyReuseSemanticEngineering | Behavior-Driven DevelopmentRequirementsExamplesRefinement | ArchitectureQualityRiskTradeoffsStakeholders | OntologyMethodologyAgileSemantic |