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)ARID (Active Reviews for Intermediate Designs)
| Criterion |  Operations Change Analysis |  Knowledge Modeling Shape-First Modeling |  Architecture SAAM (Software Architecture Analysis Method) |  Architecture ARID (Active Reviews for Intermediate Designs) |
|---|---|---|---|---|
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. | ARID examines how well developers can work with a technical design. It focuses on a part of the system that can still be revised, between the architecture overview and the detailed specification. |
Complexitydifferent | Medium | Medium | High | Medium |
Timedifferent | 45-120 min | Halber Tag pro Domain Slice | Preparation, scenario analysis, and findings review; effort depends on scope | 2–4 h review as a planning range; preparation and evaluation additional |
Participantsdifferent | 2-6 | 1-4 | Architecture experts and stakeholders for scenarios and weighting | Designers, developers as users, and facilitation |
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 development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisions |
Tagsno overlap | ChangeRoot causeTroubleshootingComparison | Knowledge graphValidationSemantic | ArchitectureChangeAnalysisComparisonQuality | ArchitectureEngineeringFeedbackValidationTasks |