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 Behavior Over Time Graph.
Systems Thinking
Behavior Over Time Graph
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)
Design sheets and interface cards connect to jointly written pseudocode with highlighted unresolved questions.
Architecture
ARID (Active Reviews for Intermediate Designs)
Purposedifferent
A Behavior Over Time Graph shows how a metric or observation develops over time. The method makes trends, breaks, and recurring patterns visible that get lost in snapshots.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.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
LowMediumMedium
Timedifferent
20-45 min3–4 h for initial assessment; preparation and deeper analysis additional2–4 h review as a planning range; preparation and evaluation additional
Participantsdifferent
1-101 or a small team; particularly suitable for 3–4 peopleDesigners, developers as users, and facilitation
Formatsame
Workshop + asyncWorkshop + asyncWorkshop + async
Outputdifferent
Behavior Over Time Graph, Trend Hypotheses, Key EventsLean 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 checksPrioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisions
Tagsno overlap
Systems thinkingPatternsDynamics
ArchitectureQualityRiskAssessmentLean
ArchitectureEngineeringFeedbackValidationTasks
Add more methods

Often compared together

Methods with strong topical overlap with the current selection, not yet in the comparison.

Paper illustration: scenarios and architectural decisions are connected to identified risks.
Architecture
ATAM (Architecture Tradeoff Analysis Method)
Causal Loop Diagram workspace showing the question, observations, and next decision.
Systems Thinking
Causal Loop Diagram
Paper illustration for Risk Storming.
Architecture
Risk Storming
Stock and Flow Diagram method illustration showing its working structure
Systems Thinking
Stock and Flow Diagram