View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:RAID LogSAAM (Software Architecture Analysis Method)Views and BeyondATAM (Architecture Tradeoff Analysis Method)
| Criterion |  Delivery RAID Log |  Architecture SAAM (Software Architecture Analysis Method) |  Architecture Views and Beyond |  Architecture ATAM (Architecture Tradeoff Analysis Method) |
|---|---|---|---|---|
Purposedifferent | Helps clarify scope, sequence, and delivery flow in concrete terms. It makes work, boundaries, and order steerable. The result is captured as a RAID Log and a source for status reporting. | 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. | Views and Beyond organizes architecture into several views so no single diagram has to do everything at once. This makes it possible to choose the representation that fits the stakeholder's question. | 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 | Low | High | Medium | High |
Timedifferent | 30 min Setup, dann laufend | Preparation, scenario analysis, and findings review; effort depends on scope | 1-3 Tage | Several meetings plus preparation and analysis; total effort depends on scope |
Participantsdifferent | 1-3 maintaining, briefing for everyone | Architecture experts and stakeholders for scenarios and weighting | 1-4 | Evaluation team, architects, and relevant stakeholders |
Formatdifferent | Async | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | RAID Log, Status Report Source | 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 | Architecture Views, Cross-view Notes, Rationale | 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 | RiskTrackingStakeholdersGovernance | ArchitectureChangeAnalysisComparisonQuality | DocumentationStakeholdersArchitecture | ArchitectureQualityRiskTradeoffsStakeholders |