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)
Paper illustration of RAID Log with a method-specific labelled workspace.
Delivery
RAID Log
Paper illustration with architecture components and concrete change tasks for comparison.
Architecture
SAAM (Software Architecture Analysis Method)
Architecture Communication Canvas method illustration showing its working structure
Architecture
Architecture Communication Canvas
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.Helps clarify scope, sequence, and delivery flow in concrete terms. It makes work, boundaries, and order steerable. The result is captured as a RAID Log and a source for status reporting.SAAM helps teams judge an architecture’s suitability for selected tasks and changes. It is particularly useful for examining modifiability and comparing architecture alternatives with clear reasoning.The Architecture Communication Canvas plans architecture communication so the right people receive the right message. The method turns technical complexity into deliberate communication design.
Complexitydifferent
MediumLowHighMedium
Timedifferent
3–4 h for initial assessment; preparation and deeper analysis additional30 min Setup, dann laufendPreparation, scenario analysis, and findings review; effort depends on scope60-120 min
Participantsdifferent
1 or a small team; particularly suitable for 3–4 people1-3 maintaining, briefing for everyoneArchitecture experts and stakeholders for scenarios and weighting2-8
Formatdifferent
Workshop + asyncAsyncWorkshop + 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 checksRAID Log, Status Report SourceDomain functions mapped to components and connections, Quality attributes and evaluation criteria, Typical tasks and their effects on the architecture, Reasoned evaluation or comparison of alternativesCommunication Canvas, Stakeholder Messages, Architecture Communication Plan
Tagsno overlap
ArchitectureQualityRiskAssessmentLean
RiskTrackingStakeholdersGovernance
ArchitectureChangeAnalysisComparisonQuality
ArchitectureCommunicationStakeholdersCanvas
Add more methods