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 Property Graph Schema Design |  Decision Making Argument Mapping |  Architecture C4 Model |  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. | 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. | The C4 Model makes a system legible across several resolution levels, from context down to code. It suits situations where different audiences need to understand the same architecture from different altitudes. | 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 | Medium | Low | Medium |
Timedifferent | 4-8 h initial, dann iterativ | 1-3 h | 1-4 h | 2-4 h |
Participantsdifferent | 1-6 | 1-8 | 1-5 | 2-8 |
Formatsame | Workshop + async | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Schema Diagram, Node and Relationship Catalog, Index Plan, Migration Scripts, Sample Queries | Argument Map, Evidence Gaps, Decision Rationale | Context Diagram, Container Diagram, Component Diagram | Competency Question Set, Required Concepts, Test Queries, Coverage Matrix |
Tagsno overlap | Knowledge graphModelingSemantic | SensemakingDecisionRationale | ArchitectureCommunicationVisualization | OntologyKnowledge graphScopeRequirementsSemantic |