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
A paper-based illustration representing C4 Model with its core stages and visible working result.
Architecture
C4 Model
Paper illustration of Shape-first Modeling with its method-specific working model.
Knowledge Modeling
Shape-First Modeling
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
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.Shape-First Modeling defines data quality through shapes before implementation or integration frays at the edges. The approach fits when validation and data contracts should be part of the design from the start.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
LowMediumMediumLow
Timedifferent
1-4 hHalber Tag pro Domain Slice3–4 h for initial assessment; preparation and deeper analysis additional1-2 Tage
Participantsdifferent
1-51-41 or a small team; particularly suitable for 3–4 people1-4
Formatsame
Workshop + asyncWorkshop + asyncWorkshop + asyncWorkshop + async
Outputdifferent
Context Diagram, Container Diagram, Component DiagramSHACL or ShEx Shapes, Validation Reports, Data Contracts, Shape DocumentationLean 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
ArchitectureCommunicationVisualization
Knowledge graphValidationSemantic
ArchitectureQualityRiskAssessmentLean
ArchitectureDocumentationCommunication
Add more methods