Compare

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 Comments Software Architecture Canvas Stakeholder Salience Model Alignment Mapping

Criterion	Architecture Request for Comments	Architecture Software Architecture Canvas	Facilitation Stakeholder Salience Model	Facilitation Alignment Mapping
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.	The Software Architecture Canvas reduces a system to the most important architecture decisions, constraints, and interfaces. It is useful when teams need a resilient overall picture quickly.	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.	When several people work toward one goal but hold different mental maps, Alignment Mapping makes the discrepancies visible. It arranges goals, assumptions, and priorities so shared direction becomes verifiable.
Complexitydifferent	Medium	Low	Medium	Medium
Timedifferent	1-3 Wochen vom Draft bis zur Entscheidung	1-2 h	60-90 min	1-2 h
Participantsdifferent	3-20 Reviewer	3-10	3-6	4-12
Formatdifferent	Async	Workshop	Workshop	Workshop
Outputdifferent	RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets	Architecture Canvas, Goals, Constraints, Quality Attributes	Salience Diagram, Strategy per Class	Alignment Map, Open Issues, Decision Questions
Tagsno overlap	ArchitectureDecisionAsyncGovernance	CanvasArchitectureAlignmentWorkshop	StakeholdersFacilitationAlignmentGovernance	AlignmentStakeholdersStrategyFacilitation

Add more methods