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 with architecture components and concrete change tasks for comparison.
Architecture
SAAM (Software Architecture Analysis Method)
Design sheets and interface cards connect to jointly written pseudocode with highlighted unresolved questions.
Architecture
ARID (Active Reviews for Intermediate Designs)
Paper illustration of Shape-first Modeling with its method-specific working model.
Knowledge Modeling
Shape-First Modeling
Purposedifferent
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.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.Shape-First Modeling defines data quality through shapes before implementation or integration frays at the edges. The approach fits when validation and data contracts should be part of the design from the start.
Complexitydifferent
HighMediumMedium
Timedifferent
Preparation, scenario analysis, and findings review; effort depends on scope2–4 h review as a planning range; preparation and evaluation additionalHalber Tag pro Domain Slice
Participantsdifferent
Architecture experts and stakeholders for scenarios and weightingDesigners, developers as users, and facilitation1-4
Formatsame
Workshop + asyncWorkshop + asyncWorkshop + async
Outputdifferent
Domain functions mapped to components and connections, Quality attributes and evaluation criteria, Typical tasks and their effects on the architecture, Reasoned evaluation or comparison of alternativesPrioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisionsSHACL or ShEx Shapes, Validation Reports, Data Contracts, Shape Documentation
Tagsno overlap
ArchitectureChangeAnalysisComparisonQuality
ArchitectureEngineeringFeedbackValidationTasks
Knowledge graphValidationSemantic
Add more methods

Often compared together

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

Paper illustration: scenarios and architectural decisions are connected to identified risks.
Architecture
ATAM (Architecture Tradeoff Analysis Method)
Paper illustration for Change Analysis.
Operations
Change Analysis
Paper illustration of Competency Questions with its method-specific working model.
Knowledge Modeling
Competency Questions
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)