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
A/B Testing workspace showing the question, observations, and next decision.
Growth
A/B Testing
Design sheets and interface cards connect to jointly written pseudocode with highlighted unresolved questions.
Architecture
ARID (Active Reviews for Intermediate Designs)
Paper illustration of Competency Questions with its method-specific working model.
Knowledge Modeling
Competency Questions
Paper illustration of NeOn Methodology with its method-specific working model.
Knowledge Modeling
NeOn Methodology
Purposedifferent
When two variants compete, discussions quickly decide by taste rather than effect. A/B Testing checks behavior under controlled conditions and separates real improvement from chance or expectation effects.ARID examines how well developers can work with a technical design. It focuses on a part of the system that can still be revised, between the architecture overview and the detailed specification.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.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.
Complexitydifferent
HighMediumMediumHigh
Timedifferent
1-4 Wochen2–4 h review as a planning range; preparation and evaluation additional2-4 hMehrere Wochen bis Monate
Participantsdifferent
1-6Designers, developers as users, and facilitation2-82-10
Formatdifferent
AsyncWorkshop + asyncWorkshop + asyncWorkshop + async
Outputdifferent
Experiment results, Decision log, Learning summaryPrioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisionsCompetency Question Set, Required Concepts, Test Queries, Coverage MatrixOntology Requirements Specification, Reuse Plan, Ontology Modules, Evaluation Report
Tagsno overlap
ExperimentsGrowthAnalyticsValidation
ArchitectureEngineeringFeedbackValidationTasks
OntologyKnowledge graphScopeRequirementsSemantic
OntologyMethodologyReuseSemanticEngineering
Add more methods