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 a Polarity Map with two poles and four quadrants
Systems Thinking
Polarity Mapping
Paper illustration: scenarios and architectural decisions are connected to identified risks.
Architecture
ATAM (Architecture Tradeoff Analysis Method)
Paper illustration of Barrier Analysis with its method-specific working model.
Operations
Barrier Analysis
Paper illustration for Fault Tree Analysis.
Operations
Fault Tree Analysis
Purposedifferent
Polarity Mapping makes tensions between two opposing poles tangible, such as standardization and adaptation or control and autonomy. The method guards against making apparent either-or decisions prematurely.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 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.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.
Complexitydifferent
MediumHighMediumHigh
Timedifferent
1-2 hSeveral meetings plus preparation and analysis; total effort depends on scope2-4 h2-6 h
Participantsdifferent
3-12Evaluation team, architects, and relevant stakeholders2-63-8
Formatdifferent
WorkshopWorkshop + asyncWorkshop + asyncWorkshop + async
Outputdifferent
Polarity Map, Warning Signs, Balance ActionsPrioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigationsBarrier Inventory, Failure Analysis per Barrier, Action BacklogFault Tree, Critical Paths, Cause Hypotheses, Control Actions
Tagsno overlap
Systems thinkingTradeoffsLeadership
ArchitectureQualityRiskTradeoffsStakeholders
Root causeSafetyIncident
RiskRoot causeSafety
Add more methods