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 C4 Model with its core stages and visible working result.
Architecture
C4 Model
Paper illustration of Request for Comments (RFC) with its method-specific working model.
Architecture
Request for Comments
Paper illustration with architecture components and concrete change tasks for comparison.
Architecture
SAAM (Software Architecture Analysis Method)
Paper illustration of two considered options leading to a decision record with a marked status and visible consequences.
Architecture
Architecture Decision Record
Purposedifferent
The C4 Model makes a system legible across several resolution levels, from context down to code. It suits situations where different audiences need to understand the same architecture from different altitudes.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.SAAM helps teams judge an architecture’s suitability for selected tasks and changes. It is particularly useful for examining modifiability and comparing architecture alternatives with clear reasoning.An ADR permanently records an architecture decision with context, trade-offs, and consequence. It creates continuity for later changes because the decision path stays traceable.
Complexitydifferent
LowMediumHighLow
Timedifferent
1-4 h1-3 Wochen vom Draft bis zur EntscheidungPreparation, scenario analysis, and findings review; effort depends on scope15-45 min
Participantsdifferent
1-53-20 ReviewerArchitecture experts and stakeholders for scenarios and weighting1-3
Formatdifferent
Workshop + asyncAsyncWorkshop + asyncAsync
Outputdifferent
Context Diagram, Container Diagram, Component DiagramRFC document, Reviewer comments, Decision rationale, Follow-up ADR or ticketsDomain functions mapped to components and connections, Quality attributes and evaluation criteria, Typical tasks and their effects on the architecture, Reasoned evaluation or comparison of alternativesADR File, Decision Log, Rationale
Tags1 shared
ArchitectureCommunicationVisualization
ArchitectureDecisionAsyncGovernance
ArchitectureChangeAnalysisComparisonQuality
ArchitectureRationaleDocumentationGovernance
Add more methods