View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:ICE ScoringSAAM (Software Architecture Analysis Method)ARID (Active Reviews for Intermediate Designs)ATAM (Architecture Tradeoff Analysis Method)
| Criterion |  Product Strategy ICE Scoring |  Architecture SAAM (Software Architecture Analysis Method) |  Architecture ARID (Active Reviews for Intermediate Designs) |  Architecture ATAM (Architecture Tradeoff Analysis Method) |
|---|---|---|---|---|
Purposedifferent | When ideas need sorting quickly, it condenses impact, confidence, and effort into one compact score. It connects customer value, product logic, and decision priorities. The result is captured as an ICE table and top-ideas list. | 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. | 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 | Low | High | Medium | High |
Timedifferent | 30-60 min | Preparation, scenario analysis, and findings review; effort depends on scope | 2–4 h review as a planning range; preparation and evaluation additional | Several meetings plus preparation and analysis; total effort depends on scope |
Participantsdifferent | 2-8 | Architecture experts and stakeholders for scenarios and weighting | Designers, developers as users, and facilitation | Evaluation team, architects, and relevant stakeholders |
Formatsame | Workshop + async | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | ICE Table, Top Idea List | 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 | 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 | PrioritizationScoringGrowthDecision | ArchitectureChangeAnalysisComparisonQuality | ArchitectureEngineeringFeedbackValidationTasks | ArchitectureQualityRiskTradeoffsStakeholders |