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: scenarios and architectural decisions are connected to identified risks.
Architecture
ATAM (Architecture Tradeoff Analysis Method)
Rich Picture workspace showing the question, observations, and next decision.
Systems Thinking
Rich Picture
A paper-based illustration representing arc42 with its core stages and visible working result.
Architecture
arc42
Paper illustration for CATWOE Analysis.
Systems Thinking
CATWOE Analysis
Purposedifferent
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.A Rich Picture brings an unclear situation onto a shared drawing. It captures actors, tensions, information flows, and blind spots before the team jumps to solutions too early.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.CATWOE structures a problem from six viewpoints and prevents too narrow a view of the situation. Different experiences of the system become comparably discussable this way.
Complexitydifferent
HighLowLowMedium
Timedifferent
Several meetings plus preparation and analysis; total effort depends on scope30-90 min1-2 Tage45-90 min
Participantsdifferent
Evaluation team, architects, and relevant stakeholders2-101-43-8
Formatdifferent
Workshop + asyncWorkshopWorkshop + asyncWorkshop + async
Outputdifferent
Prioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigationsRich Picture, Problem Framing NotesArchitecture Document, Context View, Runtime View, Deployment ViewCATWOE Canvas, Root Definition, Stakeholder Perspectives, Constraints
Tagsno overlap
ArchitectureQualityRiskTradeoffsStakeholders
Systems thinkingSoft systemsFramingVisualization
ArchitectureDocumentationCommunication
Systems thinkingFramingStakeholders
Add more methods