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 SAAM (Software Architecture Analysis Method) |  Decision Making Red Teaming |  Architecture Request for Comments |
|---|---|---|---|
Purposedifferent | 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. | For strategic decisions with high reach, agreement and gut feeling are often not enough. Red teaming brings deliberate opposition into the situation and tests where a plan breaks under real counterarguments. | 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. |
Complexitydifferent | High | High | Medium |
Timedifferent | Preparation, scenario analysis, and findings review; effort depends on scope | 1-4 h | 1-3 Wochen vom Draft bis zur Entscheidung |
Participantsdifferent | Architecture experts and stakeholders for scenarios and weighting | 3-8 | 3-20 Reviewer |
Formatdifferent | Workshop + async | Workshop | Async |
Outputdifferent | 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 | Challenge Findings, Risk Register, Mitigation Plan | RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets |
Tagsno overlap | ArchitectureChangeAnalysisComparisonQuality | RiskDecisionSensemaking | ArchitectureDecisionAsyncGovernance |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
