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
Design sheets and interface cards connect to jointly written pseudocode with highlighted unresolved questions.
Architecture
ARID (Active Reviews for Intermediate Designs)
Paper illustration for Change Analysis.
Operations
Change Analysis
A paper-based illustration representing arc42 with its core stages and visible working result.
Architecture
arc42
Architecture Communication Canvas method illustration showing its working structure
Architecture
Architecture Communication Canvas
Purposedifferent
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.For a deviation after a change, the method isolates the influence of the altered condition. It narrows down which differences are relevant and which are just accompanying noise.arc42 structures architecture knowledge so teams can document system, decisions, and risks consistently. The template builds a living understanding of the architecture instead of scattered notes.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
MediumMediumLowMedium
Timedifferent
2–4 h review as a planning range; preparation and evaluation additional45-120 min1-2 Tage60-120 min
Participantsdifferent
Designers, developers as users, and facilitation2-61-42-8
Formatsame
Workshop + asyncWorkshop + asyncWorkshop + asyncWorkshop + async
Outputdifferent
Prioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisionsChange Matrix, Cause Hypotheses, Validation Questions, Action ListArchitecture Document, Context View, Runtime View, Deployment ViewCommunication Canvas, Stakeholder Messages, Architecture Communication Plan
Tagsno overlap
ArchitectureEngineeringFeedbackValidationTasks
ChangeRoot causeTroubleshootingComparison
ArchitectureDocumentationCommunication
ArchitectureCommunicationStakeholdersCanvas
Add more methods