View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:Property Graph Schema DesignArchitecture Decision RecordArgument MappingCompetency Questions
| Criterion |  Knowledge Modeling Property Graph Schema Design |  Architecture Architecture Decision Record |  Decision Making Argument Mapping |  Knowledge Modeling Competency Questions |
|---|---|---|---|---|
Purposedifferent | 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. | An ADR permanently records an architecture decision with context, trade-offs, and consequence. It creates continuity for later changes because the decision path stays traceable. | 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. |
Complexitydifferent | Medium | Low | Medium | Medium |
Timedifferent | 4-8 h initial, dann iterativ | 15-45 min | 1-3 h | 2-4 h |
Participantsdifferent | 1-6 | 1-3 | 1-8 | 2-8 |
Formatdifferent | Workshop + async | Async | Workshop + async | Workshop + async |
Outputdifferent | Schema Diagram, Node and Relationship Catalog, Index Plan, Migration Scripts, Sample Queries | ADR File, Decision Log, Rationale | Argument Map, Evidence Gaps, Decision Rationale | Competency Question Set, Required Concepts, Test Queries, Coverage Matrix |
Tagsno overlap | Knowledge graphModelingSemantic | ArchitectureRationaleDocumentationGovernance | SensemakingDecisionRationale | OntologyKnowledge graphScopeRequirementsSemantic |