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 Request for Comments |  Knowledge Modeling Linked Open Terms |  Decision Making Argument Mapping |  Knowledge Modeling Competency Questions |
|---|---|---|---|---|
Purposedifferent | An RFC clarifies architecture context, options, and consequences. It structures technical context, alternatives, tradeoffs, open questions, and review feedback, and captures the result as an RFC document, reviewer comments, and a decision rationale. | 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 statements, evidence, and counterarguments get mixed up, a debate quickly loses its structure. Argument Mapping breaks a thesis down into its reasoning and makes visible what it really rests on. | 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. |
Complexitysame | Medium | Medium | Medium | Medium |
Timedifferent | 1-3 Wochen vom Draft bis zur Entscheidung | Wochen bis Monate | 1-3 h | 2-4 h |
Participantsdifferent | 3-20 Reviewer | 2-8 | 1-8 | 2-8 |
Formatdifferent | Async | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets | Ontology Requirements, Conceptual Model, Published Ontology, Documentation, Maintenance Plan | Argument Map, Evidence Gaps, Decision Rationale | Competency Question Set, Required Concepts, Test Queries, Coverage Matrix |
Tagsno overlap | ArchitectureDecisionAsyncGovernance | OntologyMethodologyAgileSemantic | SensemakingDecisionRationale | OntologyKnowledge graphScopeRequirementsSemantic |