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
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)
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.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.
Complexitydifferent
MediumMediumHigh
Timedifferent
2-4 h2–4 h review as a planning range; preparation and evaluation additionalSeveral meetings plus preparation and analysis; total effort depends on scope
Participantsdifferent
2-8Designers, developers as users, and facilitationEvaluation team, architects, and relevant stakeholders
Formatsame
Workshop + asyncWorkshop + asyncWorkshop + async
Outputdifferent
Competency Question Set, Required Concepts, Test Queries, Coverage MatrixPrioritized 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 investigations
Tagsno overlap
OntologyKnowledge graphScopeRequirementsSemantic
ArchitectureEngineeringFeedbackValidationTasks
ArchitectureQualityRiskTradeoffsStakeholders
Add more methods

Often compared together

Methods with strong topical overlap with the current selection, not yet in the comparison.

Four paper stations connect system purpose, quality goals, risk cards and focused investigation with a target and gap profile.
Architecture
LASR (Lightweight Approach for Software Reviews)
Paper illustration of NeOn Methodology with its method-specific working model.
Knowledge Modeling
NeOn Methodology
Paper illustration for Risk Storming.
Architecture
Risk Storming
Paper illustration of Shape-first Modeling with its method-specific working model.
Knowledge Modeling
Shape-First Modeling