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 of two considered options leading to a decision record with a marked status and visible consequences.
Architecture
Architecture Decision Record
Paper illustration: scenarios and architectural decisions are connected to identified risks.
Architecture
ATAM (Architecture Tradeoff Analysis Method)
A paper-based illustration representing arc42 with its core stages and visible working result.
Architecture
arc42
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.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.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.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.
Complexitydifferent
MediumLowHighLow
Timedifferent
2-4 h15-45 minSeveral meetings plus preparation and analysis; total effort depends on scope1-2 Tage
Participantsdifferent
2-81-3Evaluation team, architects, and relevant stakeholders1-4
Formatdifferent
Workshop + asyncAsyncWorkshop + asyncWorkshop + async
Outputdifferent
Competency Question Set, Required Concepts, Test Queries, Coverage MatrixADR File, Decision Log, RationalePrioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigationsArchitecture Document, Context View, Runtime View, Deployment View
Tagsno overlap
OntologyKnowledge graphScopeRequirementsSemantic
ArchitectureRationaleDocumentationGovernance
ArchitectureQualityRiskTradeoffsStakeholders
ArchitectureDocumentationCommunication
Add more methods