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)
Architecture Communication Canvas method illustration showing its working structure
Architecture
Architecture Communication Canvas
Paper illustration of Power-Interest Grid with a method-specific labelled workspace.
Facilitation
Power Interest Grid
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)
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.The Architecture Communication Canvas plans architecture communication so the right people receive the right message. The method turns technical complexity into deliberate communication design.When many stakeholders compete for attention at once, the Power Interest Grid sorts them by influence and stake. It turns individual contributions into a visible selection. The result is captured as a Power Interest Grid and a stakeholder-specific strategy.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.
Complexitydifferent
HighMediumLowMedium
Timedifferent
Several meetings plus preparation and analysis; total effort depends on scope60-120 min30-60 min3–4 h for initial assessment; preparation and deeper analysis additional
Participantsdifferent
Evaluation team, architects, and relevant stakeholders2-82-81 or a small team; particularly suitable for 3–4 people
Formatdifferent
Workshop + asyncWorkshop + asyncWorkshopWorkshop + async
Outputdifferent
Prioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigationsCommunication Canvas, Stakeholder Messages, Architecture Communication PlanPower Interest Grid, Strategy per StakeholderLean 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 checks
Tagsno overlap
ArchitectureQualityRiskTradeoffsStakeholders
ArchitectureCommunicationStakeholdersCanvas
StakeholdersFacilitationAlignmentPlanning
ArchitectureQualityRiskAssessmentLean
Add more methods