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 DesignSAAM (Software Architecture Analysis Method)Competency Questions
| Criterion |  Knowledge Modeling Property Graph Schema Design |  Architecture SAAM (Software Architecture Analysis Method) |  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. | SAAM helps teams judge an architecture’s suitability for selected tasks and changes. It is particularly useful for examining modifiability and comparing architecture alternatives with clear reasoning. | 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 | High | Medium |
Timedifferent | 4-8 h initial, dann iterativ | Preparation, scenario analysis, and findings review; effort depends on scope | 2-4 h |
Participantsdifferent | 1-6 | Architecture experts and stakeholders for scenarios and weighting | 2-8 |
Formatsame | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Schema Diagram, Node and Relationship Catalog, Index Plan, Migration Scripts, Sample Queries | Domain functions mapped to components and connections, Quality attributes and evaluation criteria, Typical tasks and their effects on the architecture, Reasoned evaluation or comparison of alternatives | Competency Question Set, Required Concepts, Test Queries, Coverage Matrix |
Tagsno overlap | Knowledge graphModelingSemantic | ArchitectureChangeAnalysisComparisonQuality | OntologyKnowledge graphScopeRequirementsSemantic |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
