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)
Stock and Flow Diagram method illustration showing its working structure
Systems Thinking
Stock and Flow Diagram
A paper-based illustration representing arc42 with its core stages and visible working result.
Architecture
arc42
Paper illustration of System Dynamics Simulation with its method-specific working model.
Systems Thinking
System Dynamics Simulation
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.A Stock and Flow Diagram shows how stocks, inflows, and outflows shape a system over time. It is especially suited when growth, delays, or capacity limits determine the dynamics.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.System Dynamics Simulation makes assumptions about time, delay, and feedback testable through experiments. It draws relationships, patterns, and feedback loops. The result is captured as a simulation model and scenario reports.
Complexitydifferent
MediumHighLowHigh
Timedifferent
3–4 h for initial assessment; preparation and deeper analysis additional2-6 h1-2 TageMehrere Tage bis Wochen
Participantsdifferent
1 or a small team; particularly suitable for 3–4 people1-61-41-5 Modellierende, Stakeholder asynchron
Formatdifferent
Workshop + asyncWorkshop + asyncWorkshop + asyncAsync
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 checksStock and Flow Model, Dynamics Notes, Simulation HypothesesArchitecture Document, Context View, Runtime View, Deployment ViewSimulation Model, Scenario Reports
Tagsno overlap
ArchitectureQualityRiskAssessmentLean
DynamicsSimulationFeedbackSystems thinking
ArchitectureDocumentationCommunication
Systems thinkingDynamicsSimulationAnalysis
Add more methods