View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:ARID (Active Reviews for Intermediate Designs)Force Field AnalysisSAAM (Software Architecture Analysis Method)Change Analysis
| Criterion |  Architecture ARID (Active Reviews for Intermediate Designs) |  Decision Making Force Field Analysis |  Architecture SAAM (Software Architecture Analysis Method) |  Operations Change Analysis |
|---|---|---|---|---|
Purposedifferent | 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. | In change initiatives, supporting and restraining forces sit at the table at the same time. Force Field Analysis makes these tensions explicit and shows where change can be pushed forward by strengthening or relieving. | 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. | 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. |
Complexitydifferent | Medium | Low | High | Medium |
Timedifferent | 2–4 h review as a planning range; preparation and evaluation additional | 45-90 min | Preparation, scenario analysis, and findings review; effort depends on scope | 45-120 min |
Participantsdifferent | Designers, developers as users, and facilitation | 3-12 | Architecture experts and stakeholders for scenarios and weighting | 2-6 |
Formatdifferent | Workshop + async | Workshop | Workshop + async | Workshop + async |
Outputdifferent | Prioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisions | Force Field Map, Change Levers, Risk Notes | 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 | Change Matrix, Cause Hypotheses, Validation Questions, Action List |
Tagsno overlap | ArchitectureEngineeringFeedbackValidationTasks | ChangeDecisionStrategy | ArchitectureChangeAnalysisComparisonQuality | ChangeRoot causeTroubleshootingComparison |