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:Quality Attribute Workshop Eisenhower Matrix ARID (Active Reviews for Intermediate Designs)Pareto Analysis

Criterion	Architecture Quality Attribute Workshop	Decision Making Eisenhower Matrix	Architecture ARID (Active Reviews for Intermediate Designs)	Decision Making Pareto Analysis
Purposedifferent	A Quality Attribute Workshop translates quality requirements into concrete scenarios and architecture impulses. The method brings product, engineering, and operations to the same view of desired properties.	It separates true priorities from noise so it becomes clear what should be done now, scheduled, delegated, or dropped.	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.	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.
Complexitydifferent	Medium	Low	Medium	Low
Timedifferent	2-4 h	15-30 min	2–4 h review as a planning range; preparation and evaluation additional	30-60 min
Participantsdifferent	5-15	1-6	Designers, developers as users, and facilitation	1-6
Formatdifferent	Workshop	Workshop + async	Workshop + async	Workshop + async
Outputdifferent	Quality Scenarios, Priority List, Architecture Concerns	Eisenhower Matrix, Action List, Delegation Notes	Prioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisions	Pareto Chart, Top Causes, Focus List
Tagsno overlap	RequirementsArchitectureWorkshop	PrioritizationFocusTasks	ArchitectureEngineeringFeedbackValidationTasks	PrioritizationQualityFocusRoot cause

Add more methods