View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion | ![]() Knowledge Modeling PARA Method | ![]() Agile Example Mapping | ![]() Knowledge Modeling Linked Open Terms | ![]() Knowledge Modeling Competency Questions |
|---|---|---|---|---|
Purposedifferent | The PARA Method organizes knowledge into Projects, Areas, Resources, and Archives. It creates order when digital notes, files, and tasks no longer cleanly fit current work. | 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. | Linked Open Terms connects terminology work with linked-data thinking and makes terminology technically connectable. Vocabulary, meanings, and references can thereby be maintained consistently. | 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 | Medium | Low | Medium | Medium |
Timedifferent | 1-3 h Setup, laufend | 30-60 min | Wochen bis Monate | 2-4 h |
Participantsdifferent | 1 | 3-7 | 2-8 | 2-8 |
Formatdifferent | Async | Workshop | Workshop + async | Workshop + async |
Outputdifferent | PARA Structure, Project Notes, Knowledge Archive | Example Map, Acceptance Criteria, Open Questions | Ontology Requirements, Conceptual Model, Published Ontology, Documentation, Maintenance Plan | Competency Question Set, Required Concepts, Test Queries, Coverage Matrix |
Tagsno overlap | KnowledgeProductivityOrganization | Behavior-Driven DevelopmentRequirementsExamplesRefinement | OntologyMethodologyAgileSemantic | OntologyKnowledge graphScopeRequirementsSemantic |



