methodatlas
Compare

View methods side by side.

Choose up to four methods. Add them using the search and share the comparison by copying its link.

Criterion
Design sheets and interface cards connect to jointly written pseudocode with highlighted unresolved questions.
Architecture
ARID (Active Reviews for Intermediate Designs)
Paper illustration of a decision table with criteria rows, weighted ratings, and a narrowly leading alternative.
Decision Making
Decision Matrix
Paper illustration of ICE Scoring with its method-specific working model.
Product Strategy
ICE Scoring
Paper illustration: scenarios and architectural decisions are connected to identified risks.
Architecture
ATAM (Architecture Tradeoff Analysis Method)
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 several options collide with several criteria, comparison quickly becomes subjective. A Decision Matrix makes the trade-off visible and brings weighting, criteria, and options into a shared logic.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.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
MediumMediumLowHigh
Timedifferent
2–4 h review as a planning range; preparation and evaluation additional45-90 min30-60 minSeveral meetings plus preparation and analysis; total effort depends on scope
Participantsdifferent
Designers, developers as users, and facilitation2-82-8Evaluation team, architects, and relevant stakeholders
Formatsame
Workshop + asyncWorkshop + asyncWorkshop + asyncWorkshop + async
Outputdifferent
Prioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisionsDecision Matrix, Scoring Rationale, Selected OptionICE Table, Top Idea ListPrioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigations
Tagsno overlap
ArchitectureEngineeringFeedbackValidationTasks
DecisionCriteriaScoringTradeoffs
PrioritizationScoringGrowthDecision
ArchitectureQualityRiskTradeoffsStakeholders
Add more methods