View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Architecture SAAM (Software Architecture Analysis Method) |  Decision Making Constraint Analysis |  Decision Making Pre-Mortem |
|---|---|---|---|
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. |
Complexitydifferent | High | Low | Low |
Timedifferent | Preparation, scenario analysis, and findings review; effort depends on scope | 30-90 min | 20–45 min |
Participantsdifferent | Architecture experts and stakeholders for scenarios and weighting | 2-8 | Small cross-functional group |
Formatdifferent | Workshop + async | Workshop + async | Workshop |
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 |
Tagsno overlap | ArchitectureChangeAnalysisComparisonQuality | ConstraintsDecisionPlanningOptions | RiskDecisionFailurePlanning |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
