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 MORT Analysis with its method-specific working model.
Operations
MORT Analysis
Paper illustration: scenarios and architectural decisions are connected to identified risks.
Architecture
ATAM (Architecture Tradeoff Analysis Method)
Paper illustration of Family Tree Analysis with its method-specific working model.
Operations
Family Tree Analysis
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.For a safety-relevant event or a system with high protection requirements, the method examines where controls failed. It exposes both technical and organizational gaps.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.For a series of incidents with a similar pattern, the method arranges individual events as branches of a common origin. It makes visible which conditions keep recurring.
Complexitydifferent
MediumHighHighMedium
Timedifferent
3–4 h for initial assessment; preparation and deeper analysis additionalMehrere Tage bis WochenSeveral meetings plus preparation and analysis; total effort depends on scope2-4 h
Participantsdifferent
1 or a small team; particularly suitable for 3–4 people2-6Evaluation team, architects, and relevant stakeholders2-6
Formatsame
Workshop + asyncWorkshop + asyncWorkshop + 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 checksMORT Worksheets, Findings per Branch, Corrective Actions, Systemic RecommendationsPrioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigationsFamily Tree Diagram, Pattern Notes, Systemic Measures
Tagsno overlap
ArchitectureQualityRiskAssessmentLean
Root causeSafetySystemicIncident
ArchitectureQualityRiskTradeoffsStakeholders
Root causePatternsIncidentSystemic
Add more methods