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 for Root Cause Tree Analysis
Operations
Root Cause Tree Analysis
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.For a problem with several suspected causes, the method builds a causal structure instead of a mere list. It makes visible how causes connect and where the strongest points of leverage lie.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
MediumMediumHigh
Timedifferent
2–4 h review as a planning range; preparation and evaluation additional1-3 hSeveral meetings plus preparation and analysis; total effort depends on scope
Participantsdifferent
Designers, developers as users, and facilitation2-8Evaluation team, architects, and relevant stakeholders
Formatdifferent
Workshop + asyncWorkshopWorkshop + async
Outputdifferent
Prioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisionsCause Tree, Evidence Notes, CountermeasuresPrioritized 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
Root causeTreeIncidentQuality
ArchitectureQualityRiskTradeoffsStakeholders
Add more methods

Often compared together

Methods with strong topical overlap with the current selection, not yet in the comparison.

Paper illustration for Failure Mode and Effects Analysis
Operations
Failure Mode and Effects Analysis
Four paper stations connect system purpose, quality goals, risk cards and focused investigation with a target and gap profile.
Architecture
LASR (Lightweight Approach for Software Reviews)
Paper illustration for Risk Storming.
Architecture
Risk Storming
Paper illustration for Root Cause Analysis.
Operations
Root Cause Analysis