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
Stakeholder Mapping
Facilitation
Stakeholder Mapping
Paper illustration with architecture components and concrete change tasks for comparison.
Architecture
SAAM (Software Architecture Analysis Method)
Paper illustration of Power-Interest Grid with a method-specific labelled workspace.
Facilitation
Power Interest Grid
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.When an initiative depends on many people, interests, and power dynamics, Stakeholder Mapping systematically orders the environment. It shows who influences, who is affected, and where relationship management or safeguarding matters first.SAAM helps teams judge an architecture’s suitability for selected tasks and changes. It is particularly useful for examining modifiability and comparing architecture alternatives with clear reasoning.When many stakeholders compete for attention at once, the Power Interest Grid sorts them by influence and stake. It turns individual contributions into a visible selection. The result is captured as a Power Interest Grid and a stakeholder-specific strategy.
Complexitydifferent
MediumLowHighLow
Timedifferent
2-4 h60–90 minPreparation, scenario analysis, and findings review; effort depends on scope30-60 min
Participantsdifferent
2-82-8Architecture experts and stakeholders for scenarios and weighting2-8
Formatdifferent
Workshop + asyncWorkshop + asyncWorkshop + asyncWorkshop
Outputdifferent
Competency Question Set, Required Concepts, Test Queries, Coverage MatrixStakeholder Map, Engagement Plan, Risk NotesDomain functions mapped to components and connections, Quality attributes and evaluation criteria, Typical tasks and their effects on the architecture, Reasoned evaluation or comparison of alternativesPower Interest Grid, Strategy per Stakeholder
Tagsno overlap
OntologyKnowledge graphScopeRequirementsSemantic
StakeholdersAlignmentFacilitationChange
ArchitectureChangeAnalysisComparisonQuality
StakeholdersFacilitationAlignmentPlanning
Add more methods