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 ModelingSAAM (Software Architecture Analysis Method)Competency QuestionsATAM (Architecture Tradeoff Analysis Method)
| Criterion |  Knowledge Modeling Shape-First Modeling |  Architecture SAAM (Software Architecture Analysis Method) |  Knowledge Modeling Competency Questions |  Architecture ATAM (Architecture Tradeoff Analysis Method) |
|---|---|---|---|---|
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. | SAAM helps teams judge an architecture’s suitability for selected tasks and changes. It is particularly useful for examining modifiability and comparing architecture alternatives with clear reasoning. | 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. |
Complexitydifferent | Medium | High | Medium | High |
Timedifferent | Halber Tag pro Domain Slice | Preparation, scenario analysis, and findings review; effort depends on scope | 2-4 h | Several meetings plus preparation and analysis; total effort depends on scope |
Participantsdifferent | 1-4 | Architecture experts and stakeholders for scenarios and weighting | 2-8 | Evaluation team, architects, and relevant stakeholders |
Formatsame | Workshop + async | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | SHACL or ShEx Shapes, Validation Reports, Data Contracts, Shape Documentation | Domain functions mapped to components and connections, Quality attributes and evaluation criteria, Typical tasks and their effects on the architecture, Reasoned evaluation or comparison of alternatives | 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 |
Tagsno overlap | Knowledge graphValidationSemantic | ArchitectureChangeAnalysisComparisonQuality | OntologyKnowledge graphScopeRequirementsSemantic | ArchitectureQualityRiskTradeoffsStakeholders |