methodatlas
Compare

View methods side by side.

Choose up to four methods. Add them using the search and share the comparison by copying its link.

Criterion
Paper illustration: scenarios and architectural decisions are connected to identified risks.
Architecture
ATAM (Architecture Tradeoff Analysis Method)
Paper illustration of Acceptance Criteria Workshop with a method-specific labelled workspace.
Agile
Acceptance Criteria Workshop
Paper illustration of NeOn Methodology with its method-specific working model.
Knowledge Modeling
NeOn Methodology
Paper illustration of Competency Questions with its method-specific working model.
Knowledge Modeling
Competency Questions
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.When a story needs clear checkpoints before implementation, it sharpens expectation and scope together. It sorts work by value, risk, and delivery ability. The result is captured as Acceptance Criteria and a Story Update.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.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.
Complexitydifferent
HighLowHighMedium
Timedifferent
Several meetings plus preparation and analysis; total effort depends on scope20-40 min pro StoryMehrere Wochen bis Monate2-4 h
Participantsdifferent
Evaluation team, architects, and relevant stakeholders3-62-102-8
Formatdifferent
Workshop + asyncWorkshopWorkshop + asyncWorkshop + async
Outputdifferent
Prioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigationsAcceptance Criteria, Story UpdateOntology Requirements Specification, Reuse Plan, Ontology Modules, Evaluation ReportCompetency Question Set, Required Concepts, Test Queries, Coverage Matrix
Tagsno overlap
ArchitectureQualityRiskTradeoffsStakeholders
AgileRequirementsRefinementBehavior-Driven Development
OntologyMethodologyReuseSemanticEngineering
OntologyKnowledge graphScopeRequirementsSemantic
Add more methods