View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:SAAM (Software Architecture Analysis Method)Decision MatrixLASR (Lightweight Approach for Software Reviews)Trade-off Analysis
| Criterion |  Architecture SAAM (Software Architecture Analysis Method) |  Decision Making Decision Matrix |  Architecture LASR (Lightweight Approach for Software Reviews) |  Decision Making Trade-off Analysis |
|---|---|---|---|---|
Purposedifferent | 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. | When several options collide with several criteria, comparison quickly becomes subjective. A Decision Matrix makes the trade-off visible and brings weighting, criteria, and options into a shared logic. | 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. | With limited resources, quality, speed, cost, and risk almost always compete with each other. Trade-off Analysis makes these tensions explicit and prevents decisions from producing hidden side effects. |
Complexitydifferent | High | Medium | Medium | Medium |
Timedifferent | Preparation, scenario analysis, and findings review; effort depends on scope | 45-90 min | 3–4 h for initial assessment; preparation and deeper analysis additional | 45-120 min |
Participantsdifferent | Architecture experts and stakeholders for scenarios and weighting | 2-8 | 1 or a small team; particularly suitable for 3–4 people | 2-8 |
Formatsame | Workshop + async | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Domain functions mapped to components and connections, Quality attributes and evaluation criteria, Typical tasks and their effects on the architecture, Reasoned evaluation or comparison of alternatives | Decision Matrix, Scoring Rationale, Selected Option | 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 checks | Trade-off Matrix, Criteria List, Decision Rationale, Accepted Downsides |
Tagsno overlap | ArchitectureChangeAnalysisComparisonQuality | DecisionCriteriaScoringTradeoffs | ArchitectureQualityRiskAssessmentLean | TradeoffsDecisionCriteriaOptions |