View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:Communication PlanATAM (Architecture Tradeoff Analysis Method)SAAM (Software Architecture Analysis Method)C4 Model
| Criterion |  Delivery Communication Plan |  Architecture ATAM (Architecture Tradeoff Analysis Method) |  Architecture SAAM (Software Architecture Analysis Method) |  Architecture C4 Model |
|---|---|---|---|---|
Purposedifferent | When many people need to be informed in parallel and messages would otherwise arrive unevenly or too late, a Communication Plan orders communication reliably. Channels, audiences, and cadences interlock so important information doesn't get lost. | 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. | SAAM helps teams judge an architecture’s suitability for selected tasks and changes. It is particularly useful for examining modifiability and comparing architecture alternatives with clear reasoning. | 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 | Low | High | High | Low |
Timedifferent | 45-90 min | Several meetings plus preparation and analysis; total effort depends on scope | Preparation, scenario analysis, and findings review; effort depends on scope | 1-4 h |
Participantsdifferent | 2-6 | Evaluation team, architects, and relevant stakeholders | Architecture experts and stakeholders for scenarios and weighting | 1-5 |
Formatsame | Workshop + async | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Communication Plan, Channel Matrix, Message Cadence | Prioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigations | Domain functions mapped to components and connections, Quality attributes and evaluation criteria, Typical tasks and their effects on the architecture, Reasoned evaluation or comparison of alternatives | Context Diagram, Container Diagram, Component Diagram |
Tagsno overlap | CommunicationStakeholdersDeliveryPlanning | ArchitectureQualityRiskTradeoffsStakeholders | ArchitectureChangeAnalysisComparisonQuality | ArchitectureCommunicationVisualization |