View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Operations Change Analysis |  Knowledge Modeling Shape-First Modeling |  Architecture SAAM (Software Architecture Analysis Method) |
|---|---|---|---|
Purposedifferent | 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. | Shape-First Modeling defines data quality through shapes before implementation or integration frays at the edges. The approach fits when validation and data contracts should be part of the design from the start. | 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 | High |
Timedifferent | 45-120 min | Halber Tag pro Domain Slice | Preparation, scenario analysis, and findings review; effort depends on scope |
Participantsdifferent | 2-6 | 1-4 | Architecture experts and stakeholders for scenarios and weighting |
Formatsame | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Change Matrix, Cause Hypotheses, Validation Questions, Action List | SHACL or ShEx Shapes, Validation Reports, Data Contracts, Shape Documentation | 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 | ChangeRoot causeTroubleshootingComparison | Knowledge graphValidationSemantic | ArchitectureChangeAnalysisComparisonQuality |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
