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 Competency Questions |
|---|---|---|---|---|
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. | 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 | Low | Medium | Medium | Medium |
Timedifferent | 1-2 Tage | Wochen bis Monate | 60-90 min pro Feature | 2-4 h |
Participantsdifferent | 1-4 | 2-8 | 3-6 | 2-8 |
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 | Competency Question Set, Required Concepts, Test Queries, Coverage Matrix |
Tagsno overlap | ArchitectureDocumentationCommunication | OntologyMethodologyAgileSemantic | AgileRequirementsExamplesBehavior-Driven Development | OntologyKnowledge graphScopeRequirementsSemantic |