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 TroubleshootingCommunication Planarc42ATAM (Architecture Tradeoff Analysis Method)
| Criterion |  Engineering Hypothesis-Driven Troubleshooting |  Delivery Communication Plan |  Architecture arc42 |  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. | 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. | arc42 structures architecture knowledge so teams can document system, decisions, and risks consistently. The template builds a living understanding of the architecture instead of scattered notes. | 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 | 45-90 min | 1-2 Tage | Several meetings plus preparation and analysis; total effort depends on scope |
Participantsdifferent | 1-6 | 2-6 | 1-4 | Evaluation team, architects, and relevant stakeholders |
Formatsame | Workshop + async | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Hypothesis Log, Test Plan, Evidence Notes, Diagnosis Summary | Communication Plan, Channel Matrix, Message Cadence | Architecture Document, Context View, Runtime View, Deployment View | 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 | CommunicationStakeholdersDeliveryPlanning | ArchitectureDocumentationCommunication | ArchitectureQualityRiskTradeoffsStakeholders |