methodatlas
Compare

View methods side by side.

Choose up to four methods. Add them using the search and share the comparison by copying its link.

Criterion
Software Architecture Canvas method illustration showing its working structure
Architecture
Software Architecture Canvas
Paper illustration of Request for Comments (RFC) with its method-specific working model.
Architecture
Request for Comments
Architecture Communication Canvas method illustration showing its working structure
Architecture
Architecture Communication Canvas
Paper illustration of Stakeholder Salience Model with its method-specific working model.
Facilitation
Stakeholder Salience Model
Purposedifferent
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.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 Architecture Communication Canvas plans architecture communication so the right people receive the right message. The method turns technical complexity into deliberate communication design.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
LowMediumMediumMedium
Timedifferent
1-2 h1-3 Wochen vom Draft bis zur Entscheidung60-120 min60-90 min
Participantsdifferent
3-103-20 Reviewer2-83-6
Formatdifferent
WorkshopAsyncWorkshop + asyncWorkshop
Outputdifferent
Architecture Canvas, Goals, Constraints, Quality AttributesRFC document, Reviewer comments, Decision rationale, Follow-up ADR or ticketsCommunication Canvas, Stakeholder Messages, Architecture Communication PlanSalience Diagram, Strategy per Class
Tagsno overlap
CanvasArchitectureAlignmentWorkshop
ArchitectureDecisionAsyncGovernance
ArchitectureCommunicationStakeholdersCanvas
StakeholdersFacilitationAlignmentGovernance
Add more methods