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 |  Knowledge Modeling Linked Open Terms |  Agile Specification by Example |  Knowledge Modeling NeOn Methodology |
|---|---|---|---|---|
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. | Linked Open Terms connects terminology work with linked-data thinking and makes terminology technically connectable. Vocabulary, meanings, and references can thereby be maintained consistently. | 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. |
Complexitydifferent | Low | Medium | Medium | High |
Timedifferent | 1-2 Tage | Wochen bis Monate | 60-90 min pro Feature | Mehrere Wochen bis Monate |
Participantsdifferent | 1-4 | 2-8 | 3-6 | 2-10 |
Formatdifferent | Workshop + async | Workshop + async | Workshop | Workshop + async |
Outputdifferent | Architecture Document, Context View, Runtime View, Deployment View | Ontology Requirements, Conceptual Model, Published Ontology, Documentation, Maintenance Plan | Example Table, Acceptance Tests | Ontology Requirements Specification, Reuse Plan, Ontology Modules, Evaluation Report |
Tagsno overlap | ArchitectureDocumentationCommunication | OntologyMethodologyAgileSemantic | AgileRequirementsExamplesBehavior-Driven Development | OntologyMethodologyReuseSemanticEngineering |