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
A paper-based illustration representing arc42 with its core stages and visible working result.
Architecture
arc42
Paper illustration of Request for Comments (RFC) with its method-specific working model.
Architecture
Request for Comments
Design sheets and interface cards connect to jointly written pseudocode with highlighted unresolved questions.
Architecture
ARID (Active Reviews for Intermediate Designs)
A paper-based illustration representing C4 Model with its core stages and visible working result.
Architecture
C4 Model
Purposedifferent
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.An RFC clarifies architecture context, options, and consequences. It structures technical context, alternatives, tradeoffs, open questions, and review feedback, and captures the result as an RFC document, reviewer comments, and a decision rationale.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 C4 Model makes a system legible across several resolution levels, from context down to code. It suits situations where different audiences need to understand the same architecture from different altitudes.
Complexitydifferent
LowMediumMediumLow
Timedifferent
1-2 Tage1-3 Wochen vom Draft bis zur Entscheidung2–4 h review as a planning range; preparation and evaluation additional1-4 h
Participantsdifferent
1-43-20 ReviewerDesigners, developers as users, and facilitation1-5
Formatdifferent
Workshop + asyncAsyncWorkshop + asyncWorkshop + async
Outputdifferent
Architecture Document, Context View, Runtime View, Deployment ViewRFC document, Reviewer comments, Decision rationale, Follow-up ADR or ticketsPrioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisionsContext Diagram, Container Diagram, Component Diagram
Tags1 shared
ArchitectureDocumentationCommunication
ArchitectureDecisionAsyncGovernance
ArchitectureEngineeringFeedbackValidationTasks
ArchitectureCommunicationVisualization
Add more methods