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
A3 Problem-Solving workspace showing the question, observations, and next decision.
Operations
A3 Problem Solving
Architecture Communication Canvas method illustration showing its working structure
Architecture
Architecture Communication Canvas
Paper illustration: scenarios and architectural decisions are connected to identified risks.
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.For a complex deviation with several people involved, the method bundles problem, analysis, and decision onto one page. It creates a shared working space where causes, countermeasures, and follow-up fit together.The Architecture Communication Canvas plans architecture communication so the right people receive the right message. The method turns technical complexity into deliberate communication design.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
MediumMediumMediumHigh
Timedifferent
2-4 h45-90 min60-120 minSeveral meetings plus preparation and analysis; total effort depends on scope
Participantsdifferent
2-82-52-8Evaluation team, architects, and relevant stakeholders
Formatsame
Workshop + asyncWorkshop + asyncWorkshop + asyncWorkshop + async
Outputdifferent
Competency Question Set, Required Concepts, Test Queries, Coverage MatrixA3 Report, Action Plan, Root Cause AnalysisCommunication Canvas, Stakeholder Messages, Architecture Communication PlanPrioritized 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
LeanProblem solvingCoachingOperations
ArchitectureCommunicationStakeholdersCanvas
ArchitectureQualityRiskTradeoffsStakeholders
Add more methods