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 participant using a prototype while an observer takes notes beside a highlighted usability issue.
UX Research
Usability Testing
Views and Beyond method illustration showing its working structure
Architecture
Views and Beyond
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 product is built but people get stuck on tasks, usability testing shows the friction at concrete points. Observed use instead of self-report makes visible where orientation, understanding, or interaction breaks down.Views and Beyond organizes architecture into several views so no single diagram has to do everything at once. This makes it possible to choose the representation that fits the stakeholder's question.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
MediumMediumMediumLow
Timedifferent
1-2 h je Session1-3 Tage3–4 h for initial assessment; preparation and deeper analysis additional1-2 Tage
Participantsdifferent
Based on research question1-41 or a small team; particularly suitable for 3–4 people1-4
Formatsame
Workshop + asyncWorkshop + asyncWorkshop + asyncWorkshop + async
Outputdifferent
Usability Issues, Severity List, RecommendationsArchitecture Views, Cross-view Notes, RationaleLean 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
ValidationUXPrototype
DocumentationStakeholdersArchitecture
ArchitectureQualityRiskAssessmentLean
ArchitectureDocumentationCommunication
Add more methods