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 LogRequest for CommentsForce Field AnalysisATAM (Architecture Tradeoff Analysis Method)
| Criterion |  Delivery RAID Log |  Architecture Request for Comments |  Decision Making Force Field Analysis |  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. | An RFC clarifies architecture context, options, and consequences. It structures technical context, alternatives, tradeoffs, open questions, and review feedback, and captures the result as an RFC document, reviewer comments, and a decision rationale. | In change initiatives, supporting and restraining forces sit at the table at the same time. Force Field Analysis makes these tensions explicit and shows where change can be pushed forward by strengthening or relieving. | 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 | Medium | Low | High |
Timedifferent | 30 min Setup, dann laufend | 1-3 Wochen vom Draft bis zur Entscheidung | 45-90 min | Several meetings plus preparation and analysis; total effort depends on scope |
Participantsdifferent | 1-3 maintaining, briefing for everyone | 3-20 Reviewer | 3-12 | Evaluation team, architects, and relevant stakeholders |
Formatdifferent | Async | Async | Workshop | Workshop + async |
Outputdifferent | RAID Log, Status Report Source | RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets | Force Field Map, Change Levers, Risk Notes | 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 | ArchitectureDecisionAsyncGovernance | ChangeDecisionStrategy | ArchitectureQualityRiskTradeoffsStakeholders |