View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:Change AnalysisShape-First ModelingSAAM (Software Architecture Analysis Method)ATAM (Architecture Tradeoff Analysis Method)
| Criterion |  Operations Change Analysis |  Knowledge Modeling Shape-First Modeling |  Architecture SAAM (Software Architecture Analysis Method) |  Architecture ATAM (Architecture Tradeoff 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. | ATAM helps teams weigh architecture decisions when quality goals compete. The team considers business goals, stakeholder expectations, and technical decisions together. The evaluation shows which risks need further investigation. |
Complexitydifferent | Medium | Medium | High | High |
Timedifferent | 45-120 min | Halber Tag pro Domain Slice | Preparation, scenario analysis, and findings review; effort depends on scope | Several meetings plus preparation and analysis; total effort depends on scope |
Participantsdifferent | 2-6 | 1-4 | Architecture experts and stakeholders for scenarios and weighting | Evaluation team, architects, and relevant stakeholders |
Formatsame | Workshop + async | 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 | Prioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigations |
Tagsno overlap | ChangeRoot causeTroubleshootingComparison | Knowledge graphValidationSemantic | ArchitectureChangeAnalysisComparisonQuality | ArchitectureQualityRiskTradeoffsStakeholders |