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 with architecture components and concrete change tasks for comparison.
Architecture
SAAM (Software Architecture Analysis Method)
Paper fishbone diagram with a measurable effect at the head and six labeled cause branches.
Operations
Fishbone Diagram
Paper illustration of the Force Field Analysis working structure.
Decision Making
Force Field Analysis
Paper illustration for Failure Mode and Effects Analysis
Operations
Failure Mode and Effects Analysis
Purposedifferent
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.When a problem has several possible contributing factors, the method sorts causes by cause areas. It prevents an initial hunch from blocking the view of other plausible drivers.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.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.
Complexitydifferent
HighLowLowHigh
Timedifferent
Preparation, scenario analysis, and findings review; effort depends on scope30-60 min45-90 min2-6 h
Participantsdifferent
Architecture experts and stakeholders for scenarios and weighting2-83-123-10
Formatdifferent
Workshop + asyncWorkshopWorkshopWorkshop
Outputdifferent
Domain functions mapped to components and connections, Quality attributes and evaluation criteria, Typical tasks and their effects on the architecture, Reasoned evaluation or comparison of alternativesFishbone Diagram, Cause Categories, Investigation BacklogForce Field Map, Change Levers, Risk NotesFMEA Table, Risk Priority, Mitigation Actions
Tagsno overlap
ArchitectureChangeAnalysisComparisonQuality
Root causeQualityOperations
ChangeDecisionStrategy
RiskQualityOperationsRoot cause
Add more methods