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 for Behavior Over Time Graph.
Systems Thinking
Behavior Over Time Graph
Paper illustration for Failure Mode and Effects Analysis
Operations
Failure Mode and Effects Analysis
Paper illustration: scenarios and architectural decisions are connected to identified risks.
Architecture
ATAM (Architecture Tradeoff Analysis Method)
Iceberg Model method illustration showing its working structure
Systems Thinking
Iceberg Model
Purposedifferent
A Behavior Over Time Graph shows how a metric or observation develops over time. The method makes trends, breaks, and recurring patterns visible that get lost in snapshots.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.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.The Iceberg Model separates visible events from patterns, structures, and mental models. This turns a single observation into a deeper understanding of why a problem keeps recurring.
Complexitydifferent
LowHighHighLow
Timedifferent
20-45 min2-6 hSeveral meetings plus preparation and analysis; total effort depends on scope30-60 min
Participantsdifferent
1-103-10Evaluation team, architects, and relevant stakeholders2-10
Formatdifferent
Workshop + asyncWorkshopWorkshop + asyncWorkshop + async
Outputdifferent
Behavior Over Time Graph, Trend Hypotheses, Key EventsFMEA Table, Risk Priority, Mitigation ActionsPrioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigationsIceberg Worksheet, Pattern Notes, Intervention Ideas
Tagsno overlap
Systems thinkingPatternsDynamics
RiskQualityOperationsRoot cause
ArchitectureQualityRiskTradeoffsStakeholders
Systems thinkingRoot causePatterns
Add more methods