View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:Competency QuestionsChange AnalysisProperty Graph Schema DesignSAAM (Software Architecture Analysis Method)
| Criterion |  Knowledge Modeling Competency Questions |  Operations Change Analysis |  Knowledge Modeling Property Graph Schema Design |  Architecture SAAM (Software Architecture Analysis Method) |
|---|---|---|---|---|
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. | For a deviation after a change, the method isolates the influence of the altered condition. It narrows down which differences are relevant and which are just accompanying noise. | 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. |
Complexitydifferent | Medium | Medium | Medium | High |
Timedifferent | 2-4 h | 45-120 min | 4-8 h initial, dann iterativ | Preparation, scenario analysis, and findings review; effort depends on scope |
Participantsdifferent | 2-8 | 2-6 | 1-6 | Architecture experts and stakeholders for scenarios and weighting |
Formatsame | Workshop + async | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Competency Question Set, Required Concepts, Test Queries, Coverage Matrix | Change Matrix, Cause Hypotheses, Validation Questions, Action List | 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 |
Tagsno overlap | OntologyKnowledge graphScopeRequirementsSemantic | ChangeRoot causeTroubleshootingComparison | Knowledge graphModelingSemantic | ArchitectureChangeAnalysisComparisonQuality |