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 for Pareto Analysis
Decision Making
Pareto Analysis
Design sheets and interface cards connect to jointly written pseudocode with highlighted unresolved questions.
Architecture
ARID (Active Reviews for Intermediate Designs)
Paper illustration with architecture components and concrete change tasks for comparison.
Architecture
SAAM (Software Architecture Analysis Method)
Paper illustration for 8D Problem Solving.
Operations
8D Problem Solving
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.ARID examines how well developers can work with a technical design. It focuses on a part of the system that can still be revised, between the architecture overview and the detailed specification.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 an acute quality or delivery problem, the method structures immediate protection and root cause work together. It keeps the situation stable while the actual cause is investigated cleanly.
Complexitydifferent
LowMediumHighHigh
Timedifferent
30-60 min2–4 h review as a planning range; preparation and evaluation additionalPreparation, scenario analysis, and findings review; effort depends on scope1-6 Wochen
Participantsdifferent
1-6Designers, developers as users, and facilitationArchitecture experts and stakeholders for scenarios and weighting4-10
Formatsame
Workshop + asyncWorkshop + asyncWorkshop + asyncWorkshop + async
Outputdifferent
Pareto Chart, Top Causes, Focus ListPrioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisionsDomain functions mapped to components and connections, Quality attributes and evaluation criteria, Typical tasks and their effects on the architecture, Reasoned evaluation or comparison of alternatives8D Report, Containment Plan, Root Cause Evidence, Corrective Action Plan
Tagsno overlap
PrioritizationQualityFocusRoot cause
ArchitectureEngineeringFeedbackValidationTasks
ArchitectureChangeAnalysisComparisonQuality
QualityProblem solvingRoot cause
Add more methods