View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:CATWOE AnalysisSpecification by ExampleATAM (Architecture Tradeoff Analysis Method)Architecture Communication Canvas
| Criterion |  Systems Thinking CATWOE Analysis |  Agile Specification by Example |  Architecture ATAM (Architecture Tradeoff Analysis Method) |  Architecture Architecture Communication Canvas |
|---|---|---|---|---|
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. | When business rules need to become precise, it ties language, example, and test together. It sorts work by value, risk, and delivery ability. The result is captured as an Example Table and Acceptance Tests. | 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 Architecture Communication Canvas plans architecture communication so the right people receive the right message. The method turns technical complexity into deliberate communication design. |
Complexitydifferent | Medium | Medium | High | Medium |
Timedifferent | 45-90 min | 60-90 min pro Feature | Several meetings plus preparation and analysis; total effort depends on scope | 60-120 min |
Participantsdifferent | 3-8 | 3-6 | Evaluation team, architects, and relevant stakeholders | 2-8 |
Formatdifferent | Workshop + async | Workshop | Workshop + async | Workshop + async |
Outputdifferent | CATWOE Canvas, Root Definition, Stakeholder Perspectives, Constraints | Example Table, Acceptance Tests | Prioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigations | Communication Canvas, Stakeholder Messages, Architecture Communication Plan |
Tagsno overlap | Systems thinkingFramingStakeholders | AgileRequirementsExamplesBehavior-Driven Development | ArchitectureQualityRiskTradeoffsStakeholders | ArchitectureCommunicationStakeholdersCanvas |