View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:Wardley MappingATAM (Architecture Tradeoff Analysis Method)Behavior Over Time GraphLASR (Lightweight Approach for Software Reviews)
| Criterion |  Systems Thinking Wardley Mapping |  Architecture ATAM (Architecture Tradeoff Analysis Method) |  Systems Thinking Behavior Over Time Graph |  Architecture LASR (Lightweight Approach for Software Reviews) |
|---|---|---|---|---|
Purposedifferent | Wardley Mapping makes visible where an offering stands today and where it can evolve. The method connects user need, value chain, and evolution stages into a strategic basis for platform, build, or buy decisions. | ATAM helps teams weigh architecture decisions when quality goals compete. The team considers business goals, stakeholder expectations, and technical decisions together. The evaluation shows which risks need further investigation. | A Behavior Over Time Graph shows how a metric or observation develops over time. The method makes trends, breaks, and recurring patterns visible that get lost in snapshots. | 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. |
Complexitydifferent | Medium | High | Low | Medium |
Timedifferent | 1-3 h | Several meetings plus preparation and analysis; total effort depends on scope | 20-45 min | 3–4 h for initial assessment; preparation and deeper analysis additional |
Participantsdifferent | 2-10 | Evaluation team, architects, and relevant stakeholders | 1-10 | 1 or a small team; particularly suitable for 3–4 people |
Formatsame | Workshop + async | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Wardley Map, Strategic Options, Evolution Notes | Prioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigations | Behavior Over Time Graph, Trend Hypotheses, Key Events | 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 |
Tagsno overlap | StrategySystems thinkingDynamics | ArchitectureQualityRiskTradeoffsStakeholders | Systems thinkingPatternsDynamics | ArchitectureQualityRiskAssessmentLean |