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)Stakeholder Salience ModelRAID Log
| Criterion |  Knowledge Modeling Competency Questions |  Architecture ATAM (Architecture Tradeoff Analysis Method) |  Facilitation Stakeholder Salience Model |  Delivery RAID Log |
|---|---|---|---|---|
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. | When stakeholders appear to matter very differently, the Stakeholder Salience Model rates their actual priority through power, legitimacy, and urgency. It turns individual contributions into a visible selection. The result is captured as a Salience diagram and a class-based strategy. | Helps clarify scope, sequence, and delivery flow in concrete terms. It makes work, boundaries, and order steerable. The result is captured as a RAID Log and a source for status reporting. |
Complexitydifferent | Medium | High | Medium | Low |
Timedifferent | 2-4 h | Several meetings plus preparation and analysis; total effort depends on scope | 60-90 min | 30 min Setup, dann laufend |
Participantsdifferent | 2-8 | Evaluation team, architects, and relevant stakeholders | 3-6 | 1-3 maintaining, briefing for everyone |
Formatdifferent | 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 | Salience Diagram, Strategy per Class | RAID Log, Status Report Source |
Tagsno overlap | OntologyKnowledge graphScopeRequirementsSemantic | ArchitectureQualityRiskTradeoffsStakeholders | StakeholdersFacilitationAlignmentGovernance | RiskTrackingStakeholdersGovernance |