View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:Request for Comments3-Circle Venn DiagramSAAM (Software Architecture Analysis Method)Stakeholder Salience Model
| Criterion |  Architecture Request for Comments |  Facilitation 3-Circle Venn Diagram |  Architecture SAAM (Software Architecture Analysis Method) |  Facilitation Stakeholder Salience Model |
|---|---|---|---|---|
Purposedifferent | 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. | When three perspectives matter at the same time, a Three-Circle Venn Diagram shows the overlaps and remainders precisely. It makes visible where shared effect arises and where only a partial perspective applies. | 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. | When stakeholders appear to matter very differently, the Stakeholder Salience Model rates their actual priority through power, legitimacy, and urgency. It turns individual contributions into a visible selection. The result is captured as a Salience diagram and a class-based strategy. |
Complexitydifferent | Medium | Low | High | Medium |
Timedifferent | 1-3 Wochen vom Draft bis zur Entscheidung | 15-45 min | Preparation, scenario analysis, and findings review; effort depends on scope | 60-90 min |
Participantsdifferent | 3-20 Reviewer | 2-8 | Architecture experts and stakeholders for scenarios and weighting | 3-6 |
Formatdifferent | Async | Workshop + async | Workshop + async | Workshop |
Outputdifferent | RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets | Venn Diagram, Overlap Notes, Differentiators | 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 | Salience Diagram, Strategy per Class |
Tagsno overlap | ArchitectureDecisionAsyncGovernance | ComparisonFacilitationAlignment | ArchitectureChangeAnalysisComparisonQuality | StakeholdersFacilitationAlignmentGovernance |