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
Paper illustration of Request for Comments (RFC) with its method-specific working model.
Architecture
Request for Comments
Paper illustration for Change Analysis.
Operations
Change Analysis
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.For a deviation after a change, the method isolates the influence of the altered condition. It narrows down which differences are relevant and which are just accompanying noise.
Complexitysame
MediumMedium
Timedifferent
1-3 Wochen vom Draft bis zur Entscheidung45-120 min
Participantsdifferent
3-20 Reviewer2-6
Formatdifferent
AsyncWorkshop + async
Outputdifferent
RFC document, Reviewer comments, Decision rationale, Follow-up ADR or ticketsChange Matrix, Cause Hypotheses, Validation Questions, Action List
Tagsno overlap
ArchitectureDecisionAsyncGovernance
ChangeRoot causeTroubleshootingComparison
Add more methods

Often compared together

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

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
Paper illustration of Decision Rights Mapping with its method-specific working model.
Decision Making
Decision Rights Mapping