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 a four-quadrant grid with tasks sorted by importance and urgency and translated into actions.
Decision Making
Eisenhower Matrix
Paper illustration for Pareto Analysis
Decision Making
Pareto Analysis
Paper illustration with architecture components and concrete change tasks for comparison.
Architecture
SAAM (Software Architecture Analysis Method)
Design sheets and interface cards connect to jointly written pseudocode with highlighted unresolved questions.
Architecture
ARID (Active Reviews for Intermediate Designs)
Purposedifferent
It separates true priorities from noise so it becomes clear what should be done now, scheduled, delegated, or dropped.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.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.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.
Complexitydifferent
LowLowHighMedium
Timedifferent
15-30 min30-60 minPreparation, scenario analysis, and findings review; effort depends on scope2–4 h review as a planning range; preparation and evaluation additional
Participantsdifferent
1-61-6Architecture experts and stakeholders for scenarios and weightingDesigners, developers as users, and facilitation
Formatsame
Workshop + asyncWorkshop + asyncWorkshop + asyncWorkshop + async
Outputdifferent
Eisenhower Matrix, Action List, Delegation NotesPareto Chart, Top Causes, Focus 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 alternativesPrioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisions
Tagsno overlap
PrioritizationFocusTasks
PrioritizationQualityFocusRoot cause
ArchitectureChangeAnalysisComparisonQuality
ArchitectureEngineeringFeedbackValidationTasks
Add more methods