View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:Shape-First ModelingATAM (Architecture Tradeoff Analysis Method)Assumption MappingLASR (Lightweight Approach for Software Reviews)
| Criterion |  Knowledge Modeling Shape-First Modeling |  Architecture ATAM (Architecture Tradeoff Analysis Method) |  Product Discovery Assumption Mapping |  Architecture LASR (Lightweight Approach for Software Reviews) |
|---|---|---|---|---|
Purposedifferent | Shape-First Modeling defines data quality through shapes before implementation or integration frays at the edges. The approach fits when validation and data contracts should be part of the design from the start. | 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. | When assumptions still sit unordered in the room, it weighs uncertainty against leverage. It makes visible which hypotheses should be checked 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. |
Complexitydifferent | Medium | High | Medium | Medium |
Timedifferent | Halber Tag pro Domain Slice | Several meetings plus preparation and analysis; total effort depends on scope | 45-60 min | 3–4 h for initial assessment; preparation and deeper analysis additional |
Participantsdifferent | 1-4 | Evaluation team, architects, and relevant stakeholders | 2-8 | 1 or a small team; particularly suitable for 3–4 people |
Formatsame | Workshop + async | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | SHACL or ShEx Shapes, Validation Reports, Data Contracts, Shape Documentation | Prioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigations | Assumption map, Test backlog, Risk ranking | 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 | Knowledge graphValidationSemantic | ArchitectureQualityRiskTradeoffsStakeholders | AssumptionsRiskExperimentsValidation | ArchitectureQualityRiskAssessmentLean |