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 QuestionsC4 ModelFailure Mode and Effects AnalysisATAM (Architecture Tradeoff Analysis Method)
| Criterion |  Knowledge Modeling Competency Questions |  Architecture C4 Model |  Operations Failure Mode and Effects Analysis |  Architecture ATAM (Architecture Tradeoff Analysis Method) |
|---|---|---|---|---|
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. | The C4 Model makes a system legible across several resolution levels, from context down to code. It suits situations where different audiences need to understand the same architecture from different altitudes. | For a process, product, or service with noticeable failure risks, the method assesses possible failure modes in advance. It directs attention to combinations of occurrence, effect, and detectability. | 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 | Low | High | High |
Timedifferent | 2-4 h | 1-4 h | 2-6 h | Several meetings plus preparation and analysis; total effort depends on scope |
Participantsdifferent | 2-8 | 1-5 | 3-10 | Evaluation team, architects, and relevant stakeholders |
Formatdifferent | Workshop + async | Workshop + async | Workshop | Workshop + async |
Outputdifferent | Competency Question Set, Required Concepts, Test Queries, Coverage Matrix | Context Diagram, Container Diagram, Component Diagram | FMEA Table, Risk Priority, Mitigation Actions | 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 | OntologyKnowledge graphScopeRequirementsSemantic | ArchitectureCommunicationVisualization | RiskQualityOperationsRoot cause | ArchitectureQualityRiskTradeoffsStakeholders |