View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Delivery RAID Log |  Systems Thinking Rich Picture |  Architecture ATAM (Architecture Tradeoff Analysis Method) |  Systems Thinking CATWOE Analysis |
|---|---|---|---|---|
Purposedifferent | Helps clarify scope, sequence, and delivery flow in concrete terms. It makes work, boundaries, and order steerable. The result is captured as a RAID Log and a source for status reporting. | 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. | 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 | Low | Low | High | Medium |
Timedifferent | 30 min Setup, dann laufend | 30-90 min | Several meetings plus preparation and analysis; total effort depends on scope | 45-90 min |
Participantsdifferent | 1-3 maintaining, briefing for everyone | 2-10 | Evaluation team, architects, and relevant stakeholders | 3-8 |
Formatdifferent | Async | Workshop | Workshop + async | Workshop + async |
Outputdifferent | RAID Log, Status Report Source | Rich Picture, Problem Framing Notes | Prioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigations | CATWOE Canvas, Root Definition, Stakeholder Perspectives, Constraints |
Tagsno overlap | RiskTrackingStakeholdersGovernance | Systems thinkingSoft systemsFramingVisualization | ArchitectureQualityRiskTradeoffsStakeholders | Systems thinkingFramingStakeholders |