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
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 C4 Model with its core stages and visible working result.
Architecture
C4 Model
Paper illustration of Competency Questions with its method-specific working model.
Knowledge Modeling
Competency Questions
A paper-based illustration representing arc42 with its core stages and visible working result.
Architecture
arc42
Purposedifferent
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.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.Competency Questions translate a domain model into concrete questions that it must be able to answer. The method keeps the model's scope clean and prevents pretty but useless structures.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
3–4 h for initial assessment; preparation and deeper analysis additional1-4 h2-4 h1-2 Tage
Participantsdifferent
1 or a small team; particularly suitable for 3–4 people1-52-81-4
Formatsame
Workshop + asyncWorkshop + asyncWorkshop + asyncWorkshop + async
Outputdifferent
Lean 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 checksContext Diagram, Container Diagram, Component DiagramCompetency Question Set, Required Concepts, Test Queries, Coverage MatrixArchitecture Document, Context View, Runtime View, Deployment View
Tagsno overlap
ArchitectureQualityRiskAssessmentLean
ArchitectureCommunicationVisualization
OntologyKnowledge graphScopeRequirementsSemantic
ArchitectureDocumentationCommunication
Add more methods