View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:ATAM (Architecture Tradeoff Analysis Method)Competency QuestionsViews and BeyondArchitecture Decision Record
| Criterion |  Architecture ATAM (Architecture Tradeoff Analysis Method) |  Knowledge Modeling Competency Questions |  Architecture Views and Beyond |  Architecture Architecture Decision Record |
|---|---|---|---|---|
Purposedifferent | 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. | 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. | Views and Beyond organizes architecture into several views so no single diagram has to do everything at once. This makes it possible to choose the representation that fits the stakeholder's question. | An ADR permanently records an architecture decision with context, trade-offs, and consequence. It creates continuity for later changes because the decision path stays traceable. |
Complexitydifferent | High | Medium | Medium | Low |
Timedifferent | Several meetings plus preparation and analysis; total effort depends on scope | 2-4 h | 1-3 Tage | 15-45 min |
Participantsdifferent | Evaluation team, architects, and relevant stakeholders | 2-8 | 1-4 | 1-3 |
Formatdifferent | Workshop + async | Workshop + async | Workshop + async | Async |
Outputdifferent | Prioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigations | Competency Question Set, Required Concepts, Test Queries, Coverage Matrix | Architecture Views, Cross-view Notes, Rationale | ADR File, Decision Log, Rationale |
Tagsno overlap | ArchitectureQualityRiskTradeoffsStakeholders | OntologyKnowledge graphScopeRequirementsSemantic | DocumentationStakeholdersArchitecture | ArchitectureRationaleDocumentationGovernance |