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
Paper illustration of Cost of Delay with its method-specific working model.
Delivery
Cost of Delay
Paper illustration: scenarios and architectural decisions are connected to identified risks.
Architecture
ATAM (Architecture Tradeoff Analysis Method)
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 calibrated five-by-five risk matrix with response cards.
Decision Making
Risk Matrix
Purposedifferent
Helps clarify scope, order, and delivery flow in concrete terms. It makes work, constraints, and sequence manageable. The result is captured as a Cost of Delay table and prioritization sequence.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.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 a project faces many possible disruptions, it quickly becomes unclear which risks deserve attention first. It separates options, evaluation criteria, and open risks. The result is captured as a Risk Matrix and a Top Risk List.
Complexitydifferent
HighHighMediumLow
Timedifferent
90-180 minSeveral meetings plus preparation and analysis; total effort depends on scope2–4 h review as a planning range; preparation and evaluation additional30-60 min
Participantsdifferent
3-8Evaluation team, architects, and relevant stakeholdersDesigners, developers as users, and facilitation3-10
Formatdifferent
WorkshopWorkshop + asyncWorkshop + asyncWorkshop + async
Outputdifferent
CoD Table, Prioritization SequencePrioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigationsPrioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisionsRisk Matrix, Top Risk List
Tagsno overlap
PrioritizationDeliveryEconomicsDecision
ArchitectureQualityRiskTradeoffsStakeholders
ArchitectureEngineeringFeedbackValidationTasks
RiskDecisionPrioritizationAssessment
Add more methods