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)RAID LogStakeholder MappingStakeholder Salience Model
| Criterion |  Architecture SAAM (Software Architecture Analysis Method) |  Delivery RAID Log |  Facilitation Stakeholder Mapping |  Facilitation Stakeholder Salience Model |
|---|---|---|---|---|
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. | 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. | When an initiative depends on many people, interests, and power dynamics, Stakeholder Mapping systematically orders the environment. It shows who influences, who is affected, and where relationship management or safeguarding matters first. | When stakeholders appear to matter very differently, the Stakeholder Salience Model rates their actual priority through power, legitimacy, and urgency. It turns individual contributions into a visible selection. The result is captured as a Salience diagram and a class-based strategy. |
Complexitydifferent | High | Low | Low | Medium |
Timedifferent | Preparation, scenario analysis, and findings review; effort depends on scope | 30 min Setup, dann laufend | 60–90 min | 60-90 min |
Participantsdifferent | Architecture experts and stakeholders for scenarios and weighting | 1-3 maintaining, briefing for everyone | 2-8 | 3-6 |
Formatdifferent | Workshop + async | 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 | RAID Log, Status Report Source | Stakeholder Map, Engagement Plan, Risk Notes | Salience Diagram, Strategy per Class |
Tagsno overlap | ArchitectureChangeAnalysisComparisonQuality | RiskTrackingStakeholdersGovernance | StakeholdersAlignmentFacilitationChange | StakeholdersFacilitationAlignmentGovernance |