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 Software Architecture Canvas |  Architecture C4 Model |  Systems Thinking CATWOE Analysis |  Systems Thinking Rich Picture |
|---|---|---|---|---|
Purposedifferent | The Software Architecture Canvas reduces a system to the most important architecture decisions, constraints, and interfaces. It is useful when teams need a resilient overall picture quickly. | 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. | 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. |
Complexitydifferent | Low | Low | Medium | Low |
Timedifferent | 1-2 h | 1-4 h | 45-90 min | 30-90 min |
Participantsdifferent | 3-10 | 1-5 | 3-8 | 2-10 |
Formatdifferent | Workshop | Workshop + async | Workshop + async | Workshop |
Outputdifferent | Architecture Canvas, Goals, Constraints, Quality Attributes | Context Diagram, Container Diagram, Component Diagram | CATWOE Canvas, Root Definition, Stakeholder Perspectives, Constraints | Rich Picture, Problem Framing Notes |
Tagsno overlap | CanvasArchitectureAlignmentWorkshop | ArchitectureCommunicationVisualization | Systems thinkingFramingStakeholders | Systems thinkingSoft systemsFramingVisualization |