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 Barrier Analysis with its method-specific working model.
Operations
Barrier Analysis
Paper illustration with architecture components and concrete change tasks for comparison.
Architecture
SAAM (Software Architecture Analysis Method)
Paper illustration for Fault Tree Analysis.
Operations
Fault Tree Analysis
Paper illustration: scenarios and architectural decisions are connected to identified risks.
Architecture
ATAM (Architecture Tradeoff Analysis Method)
Purposedifferent
For a risk that can only be managed through multiple layers of protection, the method examines the effectiveness of each barrier. It shows where safeguards are missing, too weak, or fail under real conditions.SAAM helps teams judge an architecture’s suitability for selected tasks and changes. It is particularly useful for examining modifiability and comparing architecture alternatives with clear reasoning.For a critical top event with several possible triggers, the method logically models failure paths. It makes visible which combinations of conditions can lead to damage.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
MediumHighHighHigh
Timedifferent
2-4 hPreparation, scenario analysis, and findings review; effort depends on scope2-6 hSeveral meetings plus preparation and analysis; total effort depends on scope
Participantsdifferent
2-6Architecture experts and stakeholders for scenarios and weighting3-8Evaluation team, architects, and relevant stakeholders
Formatsame
Workshop + asyncWorkshop + asyncWorkshop + asyncWorkshop + async
Outputdifferent
Barrier Inventory, Failure Analysis per Barrier, Action BacklogDomain functions mapped to components and connections, Quality attributes and evaluation criteria, Typical tasks and their effects on the architecture, Reasoned evaluation or comparison of alternativesFault Tree, Critical Paths, Cause Hypotheses, Control ActionsPrioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigations
Tagsno overlap
Root causeSafetyIncident
ArchitectureChangeAnalysisComparisonQuality
RiskRoot causeSafety
ArchitectureQualityRiskTradeoffsStakeholders
Add more methods