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 branching category tree with a highlighted search path and possible dead ends.
UX Research
Tree Testing
A paper-based illustration representing C4 Model with its core stages and visible working result.
Architecture
C4 Model
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)
A paper-based illustration representing arc42 with its core stages and visible working result.
Architecture
arc42
Purposedifferent
When a navigation exists but search paths still fail, tree testing checks findability without visual distraction. The method shows whether labels, levels, and paths really lead to the intended destination.The C4 Model makes a system legible across several resolution levels, from context down to code. It suits situations where different audiences need to understand the same architecture from different altitudes.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.arc42 structures architecture knowledge so teams can document system, decisions, and risks consistently. The template builds a living understanding of the architecture instead of scattered notes.
Complexitydifferent
MediumLowMediumLow
Timedifferent
1-2 Tage1-4 h3–4 h for initial assessment; preparation and deeper analysis additional1-2 Tage
Participantsdifferent
Based on research question1-51 or a small team; particularly suitable for 3–4 people1-4
Formatdifferent
AsyncWorkshop + asyncWorkshop + asyncWorkshop + async
Outputdifferent
Findability Metrics, Path Analysis, Revised IAContext Diagram, Container Diagram, Component DiagramLean 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 checksArchitecture Document, Context View, Runtime View, Deployment View
Tagsno overlap
Information architectureNavigationFindability
ArchitectureCommunicationVisualization
ArchitectureQualityRiskAssessmentLean
ArchitectureDocumentationCommunication
Add more methods