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 Risk Storming Architecture Communication Canvas Software Architecture Canvas

Criterion	Architecture Request for Comments	Architecture Risk Storming	Architecture Architecture Communication Canvas	Architecture Software Architecture Canvas
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.	Helps clarify architecture context, options, and consequences in concrete terms. It organizes technical context, alternatives, and consequences. The result is captured as an Annotated Diagram, a Prioritized Risk List, and an Action Backlog.	The Architecture Communication Canvas plans architecture communication so the right people receive the right message. The method turns technical complexity into deliberate communication design.	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.
Complexitydifferent	Medium	Low	Medium	Low
Timedifferent	1-3 Wochen vom Draft bis zur Entscheidung	60-90 min	60-120 min	1-2 h
Participantsdifferent	3-20 Reviewer	4-12	2-8	3-10
Formatdifferent	Async	Workshop	Workshop + async	Workshop
Outputdifferent	RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets	Annotated Diagram, Prioritized Risk List, Action Backlog	Communication Canvas, Stakeholder Messages, Architecture Communication Plan	Architecture Canvas, Goals, Constraints, Quality Attributes
Tags1 shared	ArchitectureDecisionAsyncGovernance	RiskArchitectureWorkshopValidation	ArchitectureCommunicationStakeholdersCanvas	CanvasArchitectureAlignmentWorkshop

Add more methods