View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:Problem Framing WorkshopStakeholder MappingLASR (Lightweight Approach for Software Reviews)SAAM (Software Architecture Analysis Method)
| Criterion |  Facilitation Problem Framing Workshop |  Facilitation Stakeholder Mapping |  Architecture LASR (Lightweight Approach for Software Reviews) |  Architecture SAAM (Software Architecture Analysis Method) |
|---|---|---|---|---|
Purposedifferent | When a team works on symptoms but the real question stays fuzzy, a Problem Framing Workshop sharpens the view of the right problem. It separates observation, interpretation, and target picture from each other. | 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. | 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. | 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 | Low | Low | Medium | High |
Timedifferent | 60-120 min | 60–90 min | 3–4 h for initial assessment; preparation and deeper analysis additional | Preparation, scenario analysis, and findings review; effort depends on scope |
Participantsdifferent | 4-10 | 2-8 | 1 or a small team; particularly suitable for 3–4 people | Architecture experts and stakeholders for scenarios and weighting |
Formatdifferent | Workshop | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Problem Statement, Scope Boundaries, Assumption List, Next Analysis Questions | Stakeholder Map, Engagement Plan, Risk Notes | 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 | 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 | FacilitationAlignmentDiscovery | StakeholdersAlignmentFacilitationChange | ArchitectureQualityRiskAssessmentLean | ArchitectureChangeAnalysisComparisonQuality |