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 HEART Framework with its method-specific working model.
UX Research
HEART Framework
Four paper stations connect system purpose, quality goals, risk cards and focused investigation with a target and gap profile.
Architecture
LASR (Lightweight Approach for Software Reviews)
Paper illustration of Goal Question Metric with its method-specific working model.
Engineering
Goal Question Metric
Design sheets and interface cards connect to jointly written pseudocode with highlighted unresolved questions.
Architecture
ARID (Active Reviews for Intermediate Designs)
Purposedifferent
Helps clarify observations, needs, and patterns in concrete terms. It groups observations into patterns, questions, and decisions. The result is captured as a HEART-GSM table and dashboard.LASR helps development teams identify where their software falls short of important quality goals and which improvements to consider. A small group with existing system knowledge can make an initial assessment and investigate open questions in more detail.Helps clarify technical problems, hypotheses, and next steps in concrete terms. It breaks a technical problem into testable parts. The result is captured as a GQM table and metric briefs.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.
Complexitysame
MediumMediumMediumMedium
Timedifferent
120 min initial, dann laufend3–4 h for initial assessment; preparation and deeper analysis additional90-180 min2–4 h review as a planning range; preparation and evaluation additional
Participantsdifferent
3-61 or a small team; particularly suitable for 3–4 people3-6Designers, developers as users, and facilitation
Formatdifferent
Workshop + asyncWorkshop + asyncWorkshopWorkshop + async
Outputdifferent
HEART-GSM Table, DashboardLean Mission Statement describing the software’s purpose, Prioritized quality goals and evaluation criteria, Risks and estimated gaps against quality goals, More closely examined findings and open checksGQM Table, Metric ProfilesPrioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisions
Tagsno overlap
MetricsUX researchMeasurementSatisfaction
ArchitectureQualityRiskAssessmentLean
MetricsMeasurementEngineeringAlignment
ArchitectureEngineeringFeedbackValidationTasks
Add more methods