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
Paper illustration: scenarios and architectural decisions are connected to identified risks.
Architecture
ATAM (Architecture Tradeoff Analysis Method)
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)
Software Architecture Canvas method illustration showing its working structure
Architecture
Software Architecture Canvas
Architecture Inception Canvas method illustration showing its working structure
Architecture
Architecture Inception Canvas
Purposedifferent
ATAM helps teams weigh architecture decisions when quality goals compete. The team considers business goals, stakeholder expectations, and technical decisions together. The evaluation shows which risks need further investigation.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 Software Architecture Canvas reduces a system to the most important architecture decisions, constraints, and interfaces. It is useful when teams need a resilient overall picture quickly.The Architecture Inception Canvas bundles the first architecture questions into a compact decision picture. It fits when an initiative is still in motion but still needs clear guardrails.
Complexitydifferent
HighMediumLowLow
Timedifferent
Several meetings plus preparation and analysis; total effort depends on scope3–4 h for initial assessment; preparation and deeper analysis additional1-2 h1-2 h
Participantsdifferent
Evaluation team, architects, and relevant stakeholders1 or a small team; particularly suitable for 3–4 people3-103-8
Formatdifferent
Workshop + asyncWorkshop + asyncWorkshopWorkshop
Outputdifferent
Prioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigationsLean 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 Canvas, Goals, Constraints, Quality AttributesInception Canvas, Risks, Goal List, Open Questions
Tags1 shared
ArchitectureQualityRiskTradeoffsStakeholders
ArchitectureQualityRiskAssessmentLean
CanvasArchitectureAlignmentWorkshop
AlignmentArchitectureCanvas
Add more methods