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 Failure Mode and Effects Analysis
Operations
Failure Mode and Effects Analysis
Paper illustration for Change Analysis.
Operations
Change Analysis
Paper illustration with architecture components and concrete change tasks for comparison.
Architecture
SAAM (Software Architecture Analysis Method)
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 process, product, or service with noticeable failure risks, the method assesses possible failure modes in advance. It directs attention to combinations of occurrence, effect, and detectability.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.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.
Complexitydifferent
MediumHighMediumHigh
Timedifferent
1-3 Wochen vom Draft bis zur Entscheidung2-6 h45-120 minPreparation, scenario analysis, and findings review; effort depends on scope
Participantsdifferent
3-20 Reviewer3-102-6Architecture experts and stakeholders for scenarios and weighting
Formatdifferent
AsyncWorkshopWorkshop + asyncWorkshop + async
Outputdifferent
RFC document, Reviewer comments, Decision rationale, Follow-up ADR or ticketsFMEA Table, Risk Priority, Mitigation ActionsChange Matrix, Cause Hypotheses, Validation Questions, Action ListDomain functions mapped to components and connections, Quality attributes and evaluation criteria, Typical tasks and their effects on the architecture, Reasoned evaluation or comparison of alternatives
Tagsno overlap
ArchitectureDecisionAsyncGovernance
RiskQualityOperationsRoot cause
ChangeRoot causeTroubleshootingComparison
ArchitectureChangeAnalysisComparisonQuality
Add more methods