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 RAID Log with a method-specific labelled workspace.
Delivery
RAID Log
Paper illustration of Competency Questions with its method-specific working model.
Knowledge Modeling
Competency Questions
A 5 Whys working surface connects an observable problem with evidenced causes, marked uncertainty and concrete countermeasures with ownership.
Operations
5 Whys
Paper illustration: scenarios and architectural decisions are connected to identified risks.
Architecture
ATAM (Architecture Tradeoff Analysis Method)
Purposedifferent
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.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 single, hard-to-explain deviation, the method exposes the causal chain behind the visible symptom. It keeps the cause open until a controllable condition emerges instead of a mere description.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
LowMediumLowHigh
Timedifferent
30 min Setup, dann laufend2-4 h15-30 minSeveral meetings plus preparation and analysis; total effort depends on scope
Participantsdifferent
1-3 maintaining, briefing for everyone2-82-6Evaluation team, architects, and relevant stakeholders
Formatdifferent
AsyncWorkshop + asyncWorkshopWorkshop + async
Outputdifferent
RAID Log, Status Report SourceCompetency Question Set, Required Concepts, Test Queries, Coverage MatrixRoot cause notes, CountermeasuresPrioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigations
Tagsno overlap
RiskTrackingStakeholdersGovernance
OntologyKnowledge graphScopeRequirementsSemantic
Root causeIncidentLeanProblem solving
ArchitectureQualityRiskTradeoffsStakeholders
Add more methods