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
Design sheets and interface cards connect to jointly written pseudocode with highlighted unresolved questions.
Architecture
ARID (Active Reviews for Intermediate Designs)
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 a yellow story card, blue rule cards, green example cards and a red question card on a light workspace.
Agile
Example Mapping
Purposedifferent
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.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.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
MediumLowHighLow
Timedifferent
2–4 h review as a planning range; preparation and evaluation additional20-40 min pro StoryMehrere Wochen bis Monate30-60 min
Participantsdifferent
Designers, developers as users, and facilitation3-62-103-7
Formatdifferent
Workshop + asyncWorkshopWorkshop + asyncWorkshop
Outputdifferent
Prioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisionsAcceptance Criteria, Story UpdateOntology Requirements Specification, Reuse Plan, Ontology Modules, Evaluation ReportExample Map, Acceptance Criteria, Open Questions
Tagsno overlap
ArchitectureEngineeringFeedbackValidationTasks
AgileRequirementsRefinementBehavior-Driven Development
OntologyMethodologyReuseSemanticEngineering
Behavior-Driven DevelopmentRequirementsExamplesRefinement
Add more methods