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 Evaporating Cloud.
Systems Thinking
Evaporating Cloud
Paper illustration: scenarios and architectural decisions are connected to identified risks.
Architecture
ATAM (Architecture Tradeoff Analysis Method)
A paper-based illustration representing arc42 with its core stages and visible working result.
Architecture
arc42
Paper illustration of two considered options leading to a decision record with a marked status and visible consequences.
Architecture
Architecture Decision Record
Purposedifferent
The method makes visible why two seemingly incompatible demands arise and which assumption must be tested to resolve the conflict.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.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.An ADR permanently records an architecture decision with context, trade-offs, and consequence. It creates continuity for later changes because the decision path stays traceable.
Complexitydifferent
MediumHighLowLow
Timedifferent
60-120 minSeveral meetings plus preparation and analysis; total effort depends on scope1-2 Tage15-45 min
Participantsdifferent
2-8Evaluation team, architects, and relevant stakeholders1-41-3
Formatdifferent
WorkshopWorkshop + asyncWorkshop + asyncAsync
Outputdifferent
Conflict Cloud, Assumption List, Breakthrough Ideas, Next ExperimentsPrioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigationsArchitecture Document, Context View, Runtime View, Deployment ViewADR File, Decision Log, Rationale
Tagsno overlap
Theory of ConstraintsAssumptionsSystems thinking
ArchitectureQualityRiskTradeoffsStakeholders
ArchitectureDocumentationCommunication
ArchitectureRationaleDocumentationGovernance
Add more methods