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 Architecture Communication Canvas Decision Rights Mapping

Criterion	Architecture Request for Comments	Architecture Software Architecture Canvas	Architecture Architecture Communication Canvas	Decision Making Decision Rights 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.	The Architecture Communication Canvas plans architecture communication so the right people receive the right message. The method turns technical complexity into deliberate communication design.	In organizations with many stakeholders, it often blurs who actually decides and who is merely consulted. It separates options, evaluation criteria, and open risks. The result is captured as a Decision Rights matrix and an agreement.
Complexitydifferent	Medium	Low	Medium	Medium
Timedifferent	1-3 Wochen vom Draft bis zur Entscheidung	1-2 h	60-120 min	90-180 min
Participantsdifferent	3-20 Reviewer	3-10	2-8	4-12
Formatdifferent	Async	Workshop	Workshop + async	Workshop
Outputdifferent	RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets	Architecture Canvas, Goals, Constraints, Quality Attributes	Communication Canvas, Stakeholder Messages, Architecture Communication Plan	Decision Rights Matrix, Agreement
Tagsno overlap	ArchitectureDecisionAsyncGovernance	CanvasArchitectureAlignmentWorkshop	ArchitectureCommunicationStakeholdersCanvas	DecisionGovernanceAlignmentResponsibility

Add more methods