View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:Hypothesis-Driven TroubleshootingC4 ModelCommunication PlanATAM (Architecture Tradeoff Analysis Method)
| Criterion |  Engineering Hypothesis-Driven Troubleshooting |  Architecture C4 Model |  Delivery Communication Plan |  Architecture ATAM (Architecture Tradeoff Analysis Method) |
|---|---|---|---|---|
Purposedifferent | When systems fail unexpectedly, spontaneous attempts often produce more noise than insight. Hypothesis-driven Troubleshooting translates symptoms into testable assumptions and makes troubleshooting learnable. | 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. | 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. |
Complexitydifferent | Medium | Low | Low | High |
Timedifferent | 30-240 min | 1-4 h | 45-90 min | Several meetings plus preparation and analysis; total effort depends on scope |
Participantsdifferent | 1-6 | 1-5 | 2-6 | Evaluation team, architects, and relevant stakeholders |
Formatsame | Workshop + async | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Hypothesis Log, Test Plan, Evidence Notes, Diagnosis Summary | Context Diagram, Container Diagram, Component Diagram | 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 |
Tagsno overlap | TroubleshootingProblem solvingDiagnosis | ArchitectureCommunicationVisualization | CommunicationStakeholdersDeliveryPlanning | ArchitectureQualityRiskTradeoffsStakeholders |