Compare

View methods side by side.

Choose up to four methods. Add them using the search and share the comparison by copying its link.

Selected:Pareto Analysis Eisenhower Matrix SAAM (Software Architecture Analysis Method)Change Analysis

Criterion	Decision Making Pareto Analysis	Decision Making Eisenhower Matrix	Architecture SAAM (Software Architecture Analysis Method)	Operations Change Analysis
Purposedifferent	In many problem situations, effect is distributed unequally across many causes. A Pareto Analysis separates the few drivers with high leverage from the long remainder and focuses attention on what measurably moves the needle.	It separates true priorities from noise so it becomes clear what should be done now, scheduled, delegated, or dropped.	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.	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.
Complexitydifferent	Low	Low	High	Medium
Timedifferent	30-60 min	15-30 min	Preparation, scenario analysis, and findings review; effort depends on scope	45-120 min
Participantsdifferent	1-6	1-6	Architecture experts and stakeholders for scenarios and weighting	2-6
Formatsame	Workshop + async	Workshop + async	Workshop + async	Workshop + async
Outputdifferent	Pareto Chart, Top Causes, Focus List	Eisenhower Matrix, Action List, Delegation Notes	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 alternatives	Change Matrix, Cause Hypotheses, Validation Questions, Action List
Tagsno overlap	PrioritizationQualityFocusRoot cause	PrioritizationFocusTasks	ArchitectureChangeAnalysisComparisonQuality	ChangeRoot causeTroubleshootingComparison

Add more methods