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.

Selected:RICE ScoringPareto Analysisarc42ATAM (Architecture Tradeoff Analysis Method)
Criterion
Paper illustration of a scoring table with four factor columns, a calculator and three ordered initiative cards.
Product Strategy
RICE Scoring
Paper illustration for Pareto Analysis
Decision Making
Pareto Analysis
A paper-based illustration representing arc42 with its core stages and visible working result.
Architecture
arc42
Paper illustration: scenarios and architectural decisions are connected to identified risks.
Architecture
ATAM (Architecture Tradeoff Analysis Method)
Purposedifferent
When many initiatives compete for the same resources, it brings reach, impact, confidence, and effort into one shared ranking. It makes prioritization economically connectable.In many problem situations, effect is distributed unequally across many causes. A Pareto Analysis separates the few drivers with high leverage from the long remainder and focuses attention on what measurably moves the needle.arc42 structures architecture knowledge so teams can document system, decisions, and risks consistently. The template builds a living understanding of the architecture instead of scattered notes.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
MediumLowLowHigh
Timedifferent
60-90 min30-60 min1-2 TageSeveral meetings plus preparation and analysis; total effort depends on scope
Participantsdifferent
2-101-61-4Evaluation team, architects, and relevant stakeholders
Formatsame
Workshop + asyncWorkshop + asyncWorkshop + asyncWorkshop + async
Outputdifferent
RICE Scores, Ranked List, Assumption LogPareto Chart, Top Causes, Focus ListArchitecture Document, Context View, Runtime View, Deployment ViewPrioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigations
Tagsno overlap
PrioritizationScoringRoadmapTradeoffs
PrioritizationQualityFocusRoot cause
ArchitectureDocumentationCommunication
ArchitectureQualityRiskTradeoffsStakeholders
Add more methods