View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Systems Thinking Systems Mapping |  Delivery RAID Log |  Architecture SAAM (Software Architecture Analysis Method) |
|---|---|---|---|
Purposedifferent | Systems Mapping arranges elements, relationships, and boundaries so a complex field becomes legible at a glance. The overview stabilizes the overall picture before detail work or steering begins. | Helps clarify scope, sequence, and delivery flow in concrete terms. It makes work, boundaries, and order steerable. The result is captured as a RAID Log and a source for status reporting. | 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 | High |
Timedifferent | 1-3 h | 30 min Setup, dann laufend | Preparation, scenario analysis, and findings review; effort depends on scope |
Participantsdifferent | 3-12 | 1-3 maintaining, briefing for everyone | Architecture experts and stakeholders for scenarios and weighting |
Formatdifferent | Workshop + async | Async | Workshop + async |
Outputdifferent | System Map, Dependencies, Leverage Points | RAID Log, Status Report Source | 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 thinkingMappingBoundariesChange | RiskTrackingStakeholdersGovernance | ArchitectureChangeAnalysisComparisonQuality |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
