View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:Risk StormingCompetency QuestionsATAM (Architecture Tradeoff Analysis Method)Shape-First Modeling
| Criterion |  Architecture Risk Storming |  Knowledge Modeling Competency Questions |  Architecture ATAM (Architecture Tradeoff Analysis Method) |  Knowledge Modeling Shape-First Modeling |
|---|---|---|---|---|
Purposedifferent | Helps clarify architecture context, options, and consequences in concrete terms. It organizes technical context, alternatives, and consequences. The result is captured as an Annotated Diagram, a Prioritized Risk List, and an Action Backlog. | 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. |
Complexitydifferent | Low | Medium | High | Medium |
Timedifferent | 60-90 min | 2-4 h | Several meetings plus preparation and analysis; total effort depends on scope | Halber Tag pro Domain Slice |
Participantsdifferent | 4-12 | 2-8 | Evaluation team, architects, and relevant stakeholders | 1-4 |
Formatdifferent | Workshop | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Annotated Diagram, Prioritized Risk List, Action Backlog | 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 |
Tagsno overlap | RiskArchitectureWorkshopValidation | OntologyKnowledge graphScopeRequirementsSemantic | ArchitectureQualityRiskTradeoffsStakeholders | Knowledge graphValidationSemantic |