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)Delphi MethodSAAM (Software Architecture Analysis Method)Force Field Analysis
| Criterion |  Architecture ARID (Active Reviews for Intermediate Designs) |  Decision Making Delphi Method |  Architecture SAAM (Software Architecture Analysis Method) |  Decision Making Force Field 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. | When knowledge is distributed and direct dominance should be avoided, groups quickly fall under the sway of their opinion leaders. The Delphi Method gathers assessments iteratively and gradually brings expert judgments closer 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. | 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. |
Complexitydifferent | Medium | High | High | Low |
Timedifferent | 2–4 h review as a planning range; preparation and evaluation additional | 1-4 Wochen | Preparation, scenario analysis, and findings review; effort depends on scope | 45-90 min |
Participantsdifferent | Designers, developers as users, and facilitation | 6-30 Experten | Architecture experts and stakeholders for scenarios and weighting | 3-12 |
Formatdifferent | Workshop + async | Async | Workshop + async | Workshop |
Outputdifferent | Prioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisions | Expert Forecast, Consensus Range, Assumption 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 | Force Field Map, Change Levers, Risk Notes |
Tagsno overlap | ArchitectureEngineeringFeedbackValidationTasks | ForecastingExpertsDecisionStrategy | ArchitectureChangeAnalysisComparisonQuality | ChangeDecisionStrategy |