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
A paper-based illustration representing arc42 with its core stages and visible working result.
Architecture
arc42
Paper illustration of Request for Comments (RFC) with its method-specific working model.
Architecture
Request for Comments
Purposedifferent
arc42 structures architecture knowledge so teams can document system, decisions, and risks consistently. The template builds a living understanding of the architecture instead of scattered notes.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
LowMedium
Timedifferent
1-2 Tage1-3 Wochen vom Draft bis zur Entscheidung
Participantsdifferent
1-43-20 Reviewer
Formatdifferent
Workshop + asyncAsync
Outputdifferent
Architecture Document, Context View, Runtime View, Deployment ViewRFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets
Tags1 shared
ArchitectureDocumentationCommunication
ArchitectureDecisionAsyncGovernance
Add more methods

Often compared together

Methods with strong topical overlap with the current selection, not yet in the comparison.

Paper illustration of two considered options leading to a decision record with a marked status and visible consequences.
Architecture
Architecture Decision Record
Architecture Communication Canvas method illustration showing its working structure
Architecture
Architecture Communication Canvas
A paper-based illustration representing C4 Model with its core stages and visible working result.
Architecture
C4 Model