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 arc42 |  Agile Specification by Example |  Knowledge Modeling NeOn Methodology |  Agile Acceptance Criteria Workshop |
|---|---|---|---|---|
Purposedifferent | arc42 structures architecture knowledge so teams can document system, decisions, and risks consistently. The template builds a living understanding of the architecture instead of scattered notes. | When business rules need to become precise, it ties language, example, and test together. It sorts work by value, risk, and delivery ability. The result is captured as an Example Table and Acceptance Tests. | 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 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. |
Complexitydifferent | Low | Medium | High | Low |
Timedifferent | 1-2 Tage | 60-90 min pro Feature | Mehrere Wochen bis Monate | 20-40 min pro Story |
Participantsdifferent | 1-4 | 3-6 | 2-10 | 3-6 |
Formatdifferent | Workshop + async | Workshop | Workshop + async | Workshop |
Outputdifferent | Architecture Document, Context View, Runtime View, Deployment View | Example Table, Acceptance Tests | Ontology Requirements Specification, Reuse Plan, Ontology Modules, Evaluation Report | Acceptance Criteria, Story Update |
Tagsno overlap | ArchitectureDocumentationCommunication | AgileRequirementsExamplesBehavior-Driven Development | OntologyMethodologyReuseSemanticEngineering | AgileRequirementsRefinementBehavior-Driven Development |