View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:Polarity MappingArchitecture Decision RecordChange AnalysisSAAM (Software Architecture Analysis Method)
| Criterion |  Systems Thinking Polarity Mapping |  Architecture Architecture Decision Record |  Operations Change Analysis |  Architecture SAAM (Software Architecture Analysis Method) |
|---|---|---|---|---|
Purposedifferent | Polarity Mapping makes tensions between two opposing poles tangible, such as standardization and adaptation or control and autonomy. The method guards against making apparent either-or decisions prematurely. | An ADR permanently records an architecture decision with context, trade-offs, and consequence. It creates continuity for later changes because the decision path stays traceable. | For a deviation after a change, the method isolates the influence of the altered condition. It narrows down which differences are relevant and which are just accompanying noise. | 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. |
Complexitydifferent | Medium | Low | Medium | High |
Timedifferent | 1-2 h | 15-45 min | 45-120 min | Preparation, scenario analysis, and findings review; effort depends on scope |
Participantsdifferent | 3-12 | 1-3 | 2-6 | Architecture experts and stakeholders for scenarios and weighting |
Formatdifferent | Workshop | Async | Workshop + async | Workshop + async |
Outputdifferent | Polarity Map, Warning Signs, Balance Actions | ADR File, Decision Log, Rationale | Change Matrix, Cause Hypotheses, Validation Questions, Action List | 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 |
Tagsno overlap | Systems thinkingTradeoffsLeadership | ArchitectureRationaleDocumentationGovernance | ChangeRoot causeTroubleshootingComparison | ArchitectureChangeAnalysisComparisonQuality |