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 ATAM (Architecture Tradeoff Analysis Method) |  Knowledge Modeling NeOn Methodology |  Agile Example Mapping |
|---|---|---|---|
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. | 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. |
Complexitydifferent | High | High | Low |
Timedifferent | Several meetings plus preparation and analysis; total effort depends on scope | Mehrere Wochen bis Monate | 30-60 min |
Participantsdifferent | Evaluation team, architects, and relevant stakeholders | 2-10 | 3-7 |
Formatdifferent | Workshop + async | Workshop + async | Workshop |
Outputdifferent | 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 Specification, Reuse Plan, Ontology Modules, Evaluation Report | Example Map, Acceptance Criteria, Open Questions |
Tagsno overlap | ArchitectureQualityRiskTradeoffsStakeholders | OntologyMethodologyReuseSemanticEngineering | Behavior-Driven DevelopmentRequirementsExamplesRefinement |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
