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
Rich Picture workspace showing the question, observations, and next decision.
Systems Thinking
Rich Picture
Paper illustration: scenarios and architectural decisions are connected to identified risks.
Architecture
ATAM (Architecture Tradeoff Analysis Method)
A paper-based illustration representing C4 Model with its core stages and visible working result.
Architecture
C4 Model
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.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.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 C4 Model makes a system legible across several resolution levels, from context down to code. It suits situations where different audiences need to understand the same architecture from different altitudes.
Complexitydifferent
MediumLowHighLow
Timedifferent
45-90 min30-90 minSeveral meetings plus preparation and analysis; total effort depends on scope1-4 h
Participantsdifferent
3-82-10Evaluation team, architects, and relevant stakeholders1-5
Formatdifferent
Workshop + asyncWorkshopWorkshop + asyncWorkshop + async
Outputdifferent
CATWOE Canvas, Root Definition, Stakeholder Perspectives, ConstraintsRich Picture, Problem Framing NotesPrioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigationsContext Diagram, Container Diagram, Component Diagram
Tagsno overlap
Systems thinkingFramingStakeholders
Systems thinkingSoft systemsFramingVisualization
ArchitectureQualityRiskTradeoffsStakeholders
ArchitectureCommunicationVisualization
Add more methods