View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:SAAM (Software Architecture Analysis Method)ARID (Active Reviews for Intermediate Designs)Delphi MethodATAM (Architecture Tradeoff Analysis Method)
| Criterion |  Architecture SAAM (Software Architecture Analysis Method) |  Architecture ARID (Active Reviews for Intermediate Designs) |  Decision Making Delphi Method |  Architecture ATAM (Architecture Tradeoff Analysis Method) |
|---|---|---|---|---|
Purposedifferent | 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. | 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. | 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 | High | Medium | High | High |
Timedifferent | Preparation, scenario analysis, and findings review; effort depends on scope | 2–4 h review as a planning range; preparation and evaluation additional | 1-4 Wochen | Several meetings plus preparation and analysis; total effort depends on scope |
Participantsdifferent | Architecture experts and stakeholders for scenarios and weighting | Designers, developers as users, and facilitation | 6-30 Experten | Evaluation team, architects, and relevant stakeholders |
Formatdifferent | Workshop + async | Workshop + async | Async | Workshop + async |
Outputdifferent | 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 | Expert Forecast, Consensus Range, Assumption Notes | 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 | ArchitectureChangeAnalysisComparisonQuality | ArchitectureEngineeringFeedbackValidationTasks | ForecastingExpertsDecisionStrategy | ArchitectureQualityRiskTradeoffsStakeholders |