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 Risk Storming.
Architecture
Risk Storming
Paper illustration of Business Model Stress Test with its method-specific working model.
Business Strategy
Business Model Stress Test
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.Helps clarify architecture context, options, and consequences in concrete terms. It organizes technical context, alternatives, and consequences. The result is captured as an Annotated Diagram, a Prioritized Risk List, and an Action Backlog.A Business Model Stress Test checks how well a business model holds up under pressure and headwinds. It compares strengths, risks, market logic, and courses of action. The result is captured as a stress-test report and action plan per scenario.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
MediumLowHighHigh
Timedifferent
2–4 h review as a planning range; preparation and evaluation additional60-90 minHalf daySeveral meetings plus preparation and analysis; total effort depends on scope
Participantsdifferent
Designers, developers as users, and facilitation4-123-8Evaluation team, architects, and relevant stakeholders
Formatdifferent
Workshop + asyncWorkshopWorkshopWorkshop + async
Outputdifferent
Prioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisionsAnnotated Diagram, Prioritized Risk List, Action BacklogStress Test Report, Action Plan per ScenarioPrioritized 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
RiskArchitectureWorkshopValidation
StrategyBusiness modelRiskDiagnosis
ArchitectureQualityRiskTradeoffsStakeholders
Add more methods