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
A paper-based illustration representing arc42 with its core stages and visible working result.
Architecture
arc42
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)
Paper illustration for Failure Mode and Effects Analysis
Operations
Failure Mode and Effects Analysis
Purposedifferent
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.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.For a process, product, or service with noticeable failure risks, the method assesses possible failure modes in advance. It directs attention to combinations of occurrence, effect, and detectability.
Complexitydifferent
LowMediumHighHigh
Timedifferent
1-2 Tage1-3 hSeveral meetings plus preparation and analysis; total effort depends on scope2-6 h
Participantsdifferent
1-42-8Evaluation team, architects, and relevant stakeholders3-10
Formatdifferent
Workshop + asyncWorkshopWorkshop + asyncWorkshop
Outputdifferent
Architecture Document, Context View, Runtime View, Deployment ViewCause 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 investigationsFMEA Table, Risk Priority, Mitigation Actions
Tagsno overlap
ArchitectureDocumentationCommunication
Root causeTreeIncidentQuality
ArchitectureQualityRiskTradeoffsStakeholders
RiskQualityOperationsRoot cause
Add more methods