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
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 Design Sprint with its core stages and visible working result.
Innovation
Design Sprint
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.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.When the product question is unclear and time pressure is high, the method takes a team from an open idea to a testable solution. It connects problem understanding, decision, and learning in one compact format, lowering the risk of spending a lot of energy on a mere guess.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
LowMediumHighLow
Timedifferent
1-4 h3–4 h for initial assessment; preparation and deeper analysis additional4-5 Tage1-2 Tage
Participantsdifferent
1-51 or a small team; particularly suitable for 3–4 people5-81-4
Formatdifferent
Workshop + asyncWorkshop + asyncWorkshopWorkshop + async
Outputdifferent
Context 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 checksPrototype, Test Findings, Decision RationaleArchitecture Document, Context View, Runtime View, Deployment View
Tagsno overlap
ArchitectureCommunicationVisualization
ArchitectureQualityRiskAssessmentLean
Design sprintPrototypeValidationInnovation
ArchitectureDocumentationCommunication
Add more methods