View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Architecture ATAM (Architecture Tradeoff Analysis Method) |  Knowledge Modeling IBIS |  Architecture Architecture Decision Record |  Delivery RAID Log |
|---|---|---|---|---|
Purposedifferent | 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. | IBIS structures thinking about complex questions as a sequence of issues, ideas, and arguments. The method keeps discussions open without forcing them into premature consensus. | An ADR permanently records an architecture decision with context, trade-offs, and consequence. It creates continuity for later changes because the decision path stays traceable. | 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. |
Complexitydifferent | High | Medium | Low | Low |
Timedifferent | Several meetings plus preparation and analysis; total effort depends on scope | 1-3 h | 15-45 min | 30 min Setup, dann laufend |
Participantsdifferent | Evaluation team, architects, and relevant stakeholders | 2-8 | 1-3 | 1-3 maintaining, briefing for everyone |
Formatdifferent | Workshop + async | Workshop + async | Async | Async |
Outputdifferent | Prioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigations | Issue Map, Positions, Argument Notes | ADR File, Decision Log, Rationale | RAID Log, Status Report Source |
Tagsno overlap | ArchitectureQualityRiskTradeoffsStakeholders | RationaleKnowledgeDecision | ArchitectureRationaleDocumentationGovernance | RiskTrackingStakeholdersGovernance |