View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:Architecture Decision RecordRequest for CommentsSAAM (Software Architecture Analysis Method)
| Criterion |  Architecture Architecture Decision Record |  Architecture Request for Comments |  Architecture SAAM (Software Architecture Analysis Method) |
|---|---|---|---|
Purposedifferent | 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. | 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. | 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. |
Complexitydifferent | Low | Medium | High |
Timedifferent | 15-45 min | 1-3 Wochen vom Draft bis zur Entscheidung | Preparation, scenario analysis, and findings review; effort depends on scope |
Participantsdifferent | 1-3 | 3-20 Reviewer | Architecture experts and stakeholders for scenarios and weighting |
Formatdifferent | Async | Async | Workshop + async |
Outputdifferent | ADR File, Decision Log, Rationale | RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets | 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 |
Tags1 shared | ArchitectureRationaleDocumentationGovernance | ArchitectureDecisionAsyncGovernance | ArchitectureChangeAnalysisComparisonQuality |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
