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
Iceberg Model method illustration showing its working structure
Systems Thinking
Iceberg Model
Paper illustration: scenarios and architectural decisions are connected to identified risks.
Architecture
ATAM (Architecture Tradeoff Analysis Method)
Views and Beyond method illustration showing its working structure
Architecture
Views and Beyond
Paper illustration for Failure Mode and Effects Analysis
Operations
Failure Mode and Effects Analysis
Purposedifferent
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.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.Views and Beyond organizes architecture into several views so no single diagram has to do everything at once. This makes it possible to choose the representation that fits the stakeholder's question.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
LowHighMediumHigh
Timedifferent
30-60 minSeveral meetings plus preparation and analysis; total effort depends on scope1-3 Tage2-6 h
Participantsdifferent
2-10Evaluation team, architects, and relevant stakeholders1-43-10
Formatdifferent
Workshop + asyncWorkshop + asyncWorkshop + asyncWorkshop
Outputdifferent
Iceberg Worksheet, Pattern Notes, Intervention IdeasPrioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigationsArchitecture Views, Cross-view Notes, RationaleFMEA Table, Risk Priority, Mitigation Actions
Tagsno overlap
Systems thinkingRoot causePatterns
ArchitectureQualityRiskTradeoffsStakeholders
DocumentationStakeholdersArchitecture
RiskQualityOperationsRoot cause
Add more methods