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 CATWOE Analysis.
Systems Thinking
CATWOE Analysis
Paper illustration for 8D Problem Solving.
Operations
8D Problem Solving
A paper-based illustration representing arc42 with its core stages and visible working result.
Architecture
arc42
Paper illustration: scenarios and architectural decisions are connected to identified risks.
Architecture
ATAM (Architecture Tradeoff Analysis Method)
Purposedifferent
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.For an acute quality or delivery problem, the method structures immediate protection and root cause work together. It keeps the situation stable while the actual cause is investigated cleanly.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.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.
Complexitydifferent
MediumHighLowHigh
Timedifferent
45-90 min1-6 Wochen1-2 TageSeveral meetings plus preparation and analysis; total effort depends on scope
Participantsdifferent
3-84-101-4Evaluation team, architects, and relevant stakeholders
Formatsame
Workshop + asyncWorkshop + asyncWorkshop + asyncWorkshop + async
Outputdifferent
CATWOE Canvas, Root Definition, Stakeholder Perspectives, Constraints8D Report, Containment Plan, Root Cause Evidence, Corrective Action PlanArchitecture Document, Context View, Runtime View, Deployment ViewPrioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigations
Tagsno overlap
Systems thinkingFramingStakeholders
QualityProblem solvingRoot cause
ArchitectureDocumentationCommunication
ArchitectureQualityRiskTradeoffsStakeholders
Add more methods