methodatlas
Compare

View methods side by side.

Choose up to four methods. Add them using the search and share the comparison by copying its link.

Criterion
Paper illustration of Competency Questions with its method-specific working model.
Knowledge Modeling
Competency Questions
Paper illustration for Fault Tree Analysis.
Operations
Fault Tree Analysis
A paper-based illustration representing arc42 with its core stages and visible working result.
Architecture
arc42
Paper illustration of two considered options leading to a decision record with a marked status and visible consequences.
Architecture
Architecture Decision Record
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.For a critical top event with several possible triggers, the method logically models failure paths. It makes visible which combinations of conditions can lead to damage.arc42 structures architecture knowledge so teams can document system, decisions, and risks consistently. The template builds a living understanding of the architecture instead of scattered notes.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
MediumHighLowLow
Timedifferent
2-4 h2-6 h1-2 Tage15-45 min
Participantsdifferent
2-83-81-41-3
Formatdifferent
Workshop + asyncWorkshop + asyncWorkshop + asyncAsync
Outputdifferent
Competency Question Set, Required Concepts, Test Queries, Coverage MatrixFault Tree, Critical Paths, Cause Hypotheses, Control ActionsArchitecture Document, Context View, Runtime View, Deployment ViewADR File, Decision Log, Rationale
Tagsno overlap
OntologyKnowledge graphScopeRequirementsSemantic
RiskRoot causeSafety
ArchitectureDocumentationCommunication
ArchitectureRationaleDocumentationGovernance
Add more methods