View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Architecture Request for Comments |  Systems Thinking CATWOE Analysis |  Architecture C4 Model |  Systems Thinking Rich Picture |
|---|---|---|---|---|
Purposedifferent | An RFC clarifies architecture context, options, and consequences. It structures technical context, alternatives, tradeoffs, open questions, and review feedback, and captures the result as an RFC document, reviewer comments, and a decision rationale. | 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. | 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. | 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. |
Complexitydifferent | Medium | Medium | Low | Low |
Timedifferent | 1-3 Wochen vom Draft bis zur Entscheidung | 45-90 min | 1-4 h | 30-90 min |
Participantsdifferent | 3-20 Reviewer | 3-8 | 1-5 | 2-10 |
Formatdifferent | Async | Workshop + async | Workshop + async | Workshop |
Outputdifferent | RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets | CATWOE Canvas, Root Definition, Stakeholder Perspectives, Constraints | Context Diagram, Container Diagram, Component Diagram | Rich Picture, Problem Framing Notes |
Tagsno overlap | ArchitectureDecisionAsyncGovernance | Systems thinkingFramingStakeholders | ArchitectureCommunicationVisualization | Systems thinkingSoft systemsFramingVisualization |