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 HEART Framework with its method-specific working model.
UX Research
HEART Framework
Paper illustration: scenarios and architectural decisions are connected to identified risks.
Architecture
ATAM (Architecture Tradeoff Analysis Method)
Design sheets and interface cards connect to jointly written pseudocode with highlighted unresolved questions.
Architecture
ARID (Active Reviews for Intermediate Designs)
Architecture Communication Canvas method illustration showing its working structure
Architecture
Architecture Communication Canvas
Purposedifferent
Helps clarify observations, needs, and patterns in concrete terms. It groups observations into patterns, questions, and decisions. The result is captured as a HEART-GSM table and dashboard.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.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.The Architecture Communication Canvas plans architecture communication so the right people receive the right message. The method turns technical complexity into deliberate communication design.
Complexitydifferent
MediumHighMediumMedium
Timedifferent
120 min initial, dann laufendSeveral meetings plus preparation and analysis; total effort depends on scope2–4 h review as a planning range; preparation and evaluation additional60-120 min
Participantsdifferent
3-6Evaluation team, architects, and relevant stakeholdersDesigners, developers as users, and facilitation2-8
Formatsame
Workshop + asyncWorkshop + asyncWorkshop + asyncWorkshop + async
Outputdifferent
HEART-GSM Table, DashboardPrioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigationsPrioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisionsCommunication Canvas, Stakeholder Messages, Architecture Communication Plan
Tagsno overlap
MetricsUX researchMeasurementSatisfaction
ArchitectureQualityRiskTradeoffsStakeholders
ArchitectureEngineeringFeedbackValidationTasks
ArchitectureCommunicationStakeholdersCanvas
Add more methods