View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:Expectation MappingLASR (Lightweight Approach for Software Reviews)Views and BeyondATAM (Architecture Tradeoff Analysis Method)
| Criterion |  Facilitation Expectation Mapping |  Architecture LASR (Lightweight Approach for Software Reviews) |  Architecture Views and Beyond |  Architecture ATAM (Architecture Tradeoff Analysis Method) |
|---|---|---|---|---|
Purposedifferent | When roles, interfaces, or projects fail because of differing expectations, Expectation Mapping surfaces these differences. It shows what each side takes for granted and where the pictures diverge. | 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. | Views and Beyond organizes architecture into several views so no single diagram has to do everything at once. This makes it possible to choose the representation that fits the stakeholder's question. | 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. |
Complexitydifferent | Low | Medium | Medium | High |
Timedifferent | 45-90 min | 3–4 h for initial assessment; preparation and deeper analysis additional | 1-3 Tage | Several meetings plus preparation and analysis; total effort depends on scope |
Participantsdifferent | 3-12 | 1 or a small team; particularly suitable for 3–4 people | 1-4 | Evaluation team, architects, and relevant stakeholders |
Formatdifferent | Workshop | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Expectation Map, Alignment Notes, Agreements | 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 | Architecture Views, Cross-view Notes, Rationale | Prioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigations |
Tagsno overlap | AlignmentStakeholdersTeam | ArchitectureQualityRiskAssessmentLean | DocumentationStakeholdersArchitecture | ArchitectureQualityRiskTradeoffsStakeholders |