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 a Concept Map with concepts and labelled links
Knowledge Modeling
Concept Mapping
Design sheets and interface cards connect to jointly written pseudocode with highlighted unresolved questions.
Architecture
ARID (Active Reviews for Intermediate Designs)
Paper illustration: scenarios and architectural decisions are connected to identified risks.
Architecture
ATAM (Architecture Tradeoff Analysis Method)
Paper illustration for Knowledge Mapping.
Knowledge Modeling
Knowledge Mapping
Purposedifferent
Concept Mapping arranges terms and relationships in a network that makes subject-matter connections tangible. It fits when a topic needs to be understood structurally rather than linearly.ARID examines how well developers can work with a technical design. It focuses on a part of the system that can still be revised, between the architecture overview and the detailed specification.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.Knowledge Mapping makes knowledge, gaps, and transfer paths visible across a field. It fits when expertise should not just exist but also be findable and transferable.
Complexitydifferent
MediumMediumHighMedium
Timedifferent
1-2 h2–4 h review as a planning range; preparation and evaluation additionalSeveral meetings plus preparation and analysis; total effort depends on scope1-3 h
Participantsdifferent
1-8Designers, developers as users, and facilitationEvaluation team, architects, and relevant stakeholders3-12
Formatdifferent
Workshop + asyncWorkshop + asyncWorkshop + asyncWorkshop
Outputdifferent
Concept Map, Relationship Labels, Knowledge GapsPrioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisionsPrioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigationsKnowledge Map, Critical Knowledge Areas, Transfer Plan
Tagsno overlap
KnowledgeConceptsMappingSensemaking
ArchitectureEngineeringFeedbackValidationTasks
ArchitectureQualityRiskTradeoffsStakeholders
KnowledgeMappingRisk
Add more methods