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)Constraint AnalysisPre-MortemLASR (Lightweight Approach for Software Reviews)
| Criterion |  Architecture SAAM (Software Architecture Analysis Method) |  Decision Making Constraint Analysis |  Decision Making Pre-Mortem |  Architecture LASR (Lightweight Approach for Software Reviews) |
|---|---|---|---|---|
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 an initiative stalls, the limit often lies not in the idea but in hard or soft boundary conditions. Constraint Analysis separates these limits and shows which of them can actually be shaped. | In early initiatives with many uncertainties, planning quickly turns too optimistic. A pre-mortem makes the expected failure visible in advance and sharpens the view of causes, gaps, and countermeasures. | 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 | High | Low | Low | Medium |
Timedifferent | Preparation, scenario analysis, and findings review; effort depends on scope | 30-90 min | 20–45 min | 3–4 h for initial assessment; preparation and deeper analysis additional |
Participantsdifferent | Architecture experts and stakeholders for scenarios and weighting | 2-8 | Small cross-functional group | 1 or a small team; particularly suitable for 3–4 people |
Formatdifferent | Workshop + async | Workshop + async | Workshop | 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 | Constraint List, Hard/Soft Classification, Option Impact Notes, Decision Boundaries | Risk list, Mitigation plan, Assumption log | 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 |
Tagsno overlap | ArchitectureChangeAnalysisComparisonQuality | ConstraintsDecisionPlanningOptions | RiskDecisionFailurePlanning | ArchitectureQualityRiskAssessmentLean |