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 for DACI
Decision Making
DACI
Architecture Inception Canvas method illustration showing its working structure
Architecture
Architecture Inception Canvas
Paper illustration of Request for Comments (RFC) with its method-specific working model.
Architecture
Request for Comments
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.In cross-functional decisions, responsibilities quickly blur between approval, influence, and execution. DACI arranges these roles so decision pressure, contribution, and information stay cleanly separated.The Architecture Inception Canvas bundles the first architecture questions into a compact decision picture. It fits when an initiative is still in motion but still needs clear guardrails.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.
Complexitydifferent
LowLowLowMedium
Timedifferent
1-2 h30-60 min1-2 h1-3 Wochen vom Draft bis zur Entscheidung
Participantsdifferent
3-102-103-83-20 Reviewer
Formatdifferent
WorkshopWorkshop + asyncWorkshopAsync
Outputdifferent
Architecture Canvas, Goals, Constraints, Quality AttributesDACI Matrix, Decision Owner, Decision LogInception Canvas, Risks, Goal List, Open QuestionsRFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets
Tagsno overlap
CanvasArchitectureAlignmentWorkshop
DecisionRolesGovernanceAlignment
AlignmentArchitectureCanvas
ArchitectureDecisionAsyncGovernance
Add more methods