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 ModelingARID (Active Reviews for Intermediate Designs)
| Criterion |  Knowledge Modeling Competency Questions |  Architecture ATAM (Architecture Tradeoff Analysis Method) |  Knowledge Modeling Shape-First Modeling |  Architecture ARID (Active Reviews for Intermediate Designs) |
|---|---|---|---|---|
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. | ARID examines how well developers can work with a technical design. It focuses on a part of the system that can still be revised, between the architecture overview and the detailed specification. |
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 | 2–4 h review as a planning range; preparation and evaluation additional |
Participantsdifferent | 2-8 | Evaluation team, architects, and relevant stakeholders | 1-4 | Designers, developers as users, and facilitation |
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 | Prioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisions |
Tagsno overlap | OntologyKnowledge graphScopeRequirementsSemantic | ArchitectureQualityRiskTradeoffsStakeholders | Knowledge graphValidationSemantic | ArchitectureEngineeringFeedbackValidationTasks |