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
A paper-based illustration representing Design Sprint with its core stages and visible working result.
Innovation
Design Sprint
A paper-based illustration representing C4 Model with its core stages and visible working result.
Architecture
C4 Model
Design sheets and interface cards connect to jointly written pseudocode with highlighted unresolved questions.
Architecture
ARID (Active Reviews for Intermediate Designs)
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.When the product question is unclear and time pressure is high, the method takes a team from an open idea to a testable solution. It connects problem understanding, decision, and learning in one compact format, lowering the risk of spending a lot of energy on a mere guess.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.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.
Complexitydifferent
LowHighLowMedium
Timedifferent
1-2 Tage4-5 Tage1-4 h2–4 h review as a planning range; preparation and evaluation additional
Participantsdifferent
1-45-81-5Designers, developers as users, and facilitation
Formatdifferent
Workshop + asyncWorkshopWorkshop + asyncWorkshop + async
Outputdifferent
Architecture Document, Context View, Runtime View, Deployment ViewPrototype, Test Findings, Decision RationaleContext Diagram, Container Diagram, Component DiagramPrioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisions
Tagsno overlap
ArchitectureDocumentationCommunication
Design sprintPrototypeValidationInnovation
ArchitectureCommunicationVisualization
ArchitectureEngineeringFeedbackValidationTasks
Add more methods