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 Competency Questions | ![]() Architecture Views and Beyond | ![]() Knowledge Modeling Linked Open Terms | ![]() Architecture Architecture Communication Canvas |
|---|---|---|---|---|
Purposedifferent | 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. | Views and Beyond organizes architecture into several views so no single diagram has to do everything at once. This makes it possible to choose the representation that fits the stakeholder's question. | Linked Open Terms connects terminology work with linked-data thinking and makes terminology technically connectable. Vocabulary, meanings, and references can thereby be maintained consistently. | The Architecture Communication Canvas plans architecture communication so the right people receive the right message. The method turns technical complexity into deliberate communication design. |
Complexitysame | Medium | Medium | Medium | Medium |
Timedifferent | 2-4 h | 1-3 Tage | Wochen bis Monate | 60-120 min |
Participantsdifferent | 2-8 | 1-4 | 2-8 | 2-8 |
Formatsame | Workshop + async | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Competency Question Set, Required Concepts, Test Queries, Coverage Matrix | Architecture Views, Cross-view Notes, Rationale | Ontology Requirements, Conceptual Model, Published Ontology, Documentation, Maintenance Plan | Communication Canvas, Stakeholder Messages, Architecture Communication Plan |
Tagsno overlap | OntologyKnowledge graphScopeRequirementsSemantic | DocumentationStakeholdersArchitecture | OntologyMethodologyAgileSemantic | ArchitectureCommunicationStakeholdersCanvas |



