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
Gap Analysis method illustration showing its working structure
Business Strategy
GAP Analysis
Paper illustration of the Force Field Analysis working structure.
Decision Making
Force Field Analysis
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)
Purposedifferent
GAP Analysis compares the current state with a target picture and makes the distance manageable. It becomes useful when, ahead of new initiatives, it must become clear which capabilities, processes, or resources are missing.In change initiatives, supporting and restraining forces sit at the table at the same time. Force Field Analysis makes these tensions explicit and shows where change can be pushed forward by strengthening or relieving.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.
Complexitydifferent
MediumLowMediumHigh
Timedifferent
1-3 h45-90 min1-3 Wochen vom Draft bis zur EntscheidungPreparation, scenario analysis, and findings review; effort depends on scope
Participantsdifferent
2-83-123-20 ReviewerArchitecture experts and stakeholders for scenarios and weighting
Formatdifferent
Workshop + asyncWorkshopAsyncWorkshop + async
Outputdifferent
Gap Matrix, Action Plan, Risk NotesForce Field Map, Change Levers, Risk NotesRFC 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 alternatives
Tagsno overlap
StrategyAnalysisPlanning
ChangeDecisionStrategy
ArchitectureDecisionAsyncGovernance
ArchitectureChangeAnalysisComparisonQuality
Add more methods