View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:Competency QuestionsATAM (Architecture Tradeoff Analysis Method)Shape-First ModelingLASR (Lightweight Approach for Software Reviews)
| Criterion |  Knowledge Modeling Competency Questions |  Architecture ATAM (Architecture Tradeoff Analysis Method) |  Knowledge Modeling Shape-First Modeling |  Architecture LASR (Lightweight Approach for Software Reviews) |
|---|---|---|---|---|
Purposedifferent | Competency Questions translate a domain model into concrete questions that it must be able to answer. The method keeps the model's scope clean and prevents pretty but useless structures. | 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. | 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. | 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 | 2-4 h | Several meetings plus preparation and analysis; total effort depends on scope | Halber Tag pro Domain Slice | 3–4 h for initial assessment; preparation and deeper analysis additional |
Participantsdifferent | 2-8 | Evaluation team, architects, and relevant stakeholders | 1-4 | 1 or a small team; particularly suitable for 3–4 people |
Formatsame | Workshop + async | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Competency Question Set, Required Concepts, Test Queries, Coverage Matrix | Prioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigations | SHACL or ShEx Shapes, Validation Reports, Data Contracts, Shape Documentation | 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 | OntologyKnowledge graphScopeRequirementsSemantic | ArchitectureQualityRiskTradeoffsStakeholders | Knowledge graphValidationSemantic | ArchitectureQualityRiskAssessmentLean |