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 arc42 | ![]() Knowledge Modeling Property Graph Schema Design |
|---|---|---|---|
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. | 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. | Property Graph Schema Design turns business and technical requirements into a robust graph schema. It fits when query patterns, constraints, and migrations need to be thought about together. |
Complexitydifferent | Medium | Low | Medium |
Timedifferent | 2-4 h | 1-2 Tage | 4-8 h initial, dann iterativ |
Participantsdifferent | 2-8 | 1-4 | 1-6 |
Formatsame | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Competency Question Set, Required Concepts, Test Queries, Coverage Matrix | Architecture Document, Context View, Runtime View, Deployment View | Schema Diagram, Node and Relationship Catalog, Index Plan, Migration Scripts, Sample Queries |
Tagsno overlap | OntologyKnowledge graphScopeRequirementsSemantic | ArchitectureDocumentationCommunication | Knowledge graphModelingSemantic |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.






