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 radar with five axes, two current and target profiles, and evidence cards beside each dimension.
Decision Making
Radar
Decision Tree method illustration showing its working structure
Decision Making
Decision Tree
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)
Purposedifferent
When capabilities, maturity levels, or market positions need to be compared across several dimensions, overview is easily lost. Radar brings different characteristics into a shared picture and shows patterns faster than tables do.For decisions with follow-on paths and dependencies, a linear comparison is often not enough. A Decision Tree shows how options branch under conditions and which consequences hang on each branch.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.
Complexitydifferent
MediumMediumLowMedium
Timedifferent
1-2 h30-90 min1-4 h3–4 h for initial assessment; preparation and deeper analysis additional
Participantsdifferent
2-101-61-51 or a small team; particularly suitable for 3–4 people
Formatsame
Workshop + asyncWorkshop + asyncWorkshop + asyncWorkshop + async
Outputdifferent
Radar Map, Capability Scores, Action AreasDecision Tree, Option Map, Assumption ListContext 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 checks
Tagsno overlap
AssessmentPortfolioCapability
DecisionTreeOptions
ArchitectureCommunicationVisualization
ArchitectureQualityRiskAssessmentLean
Add more methods