methodatlas
Architecture

arc42

Turns architecture context, options, and consequences into a tangible result by capturing goals and stakeholders, scoping context, and linking risks and decisions.

Core question
Which architecture decisions, structures, and quality attributes does the reader need in order to understand, operate, and evolve the system?
LowWorkshop + async1-2 Tage
Open runsheetPlan sessionStart comparison
Purpose

The method helps clarify architecture context, options, and consequences concretely. It organizes technical context, alternatives, and consequences. The result is captured as an architecture document, context view, and runtime view.

How it works

The team follows the steps: capture goals and stakeholders, scope context, document building blocks, describe runtime and deployment, and link risks and decisions. Each step is captured visibly. At the end, an architecture document, context view, and runtime view are available so decisions, tests, or actions can follow directly.

Visual orientation

Method sketch for a quick mental model.

arc42 · Architecture DocumentationDocument goals, context, views, quality, and decisions consistently
arc42 Architecture DocumentationThe sketch shows how architecture drivers connect through arc42 chapters into a living architecture document with decisions, reviews, and handover.Structure architecture knowledge as a living documentGoals, context, views, quality, and decisions are connected consistently.DriversWhy document?arc42 StructureFill views and chapters deliberatelyLiving DocsConnect rationaleGoalsQuality and scopeStakeholdersInformation needsConstraintsFrames and rulesContextSystem boundaryBuilding BlocksStructureRuntimeFlowsDeploymentInfrastructureQualityScenariosRisksDebtArchitecture Documentconsistent stateADRsDecisionsReviewkeep currentHandoverTeam memory

Flow

  1. 1Capture goals and stakeholders
  2. 2Scope context
  3. 3Document building blocks
  4. 4Describe runtime and deployment
  5. 5Link risks and decisions

The runsheet guides execution with 6 phases, timeboxes, 5 pitfalls, and clear stop criteria.

Open runsheet

Ideal for

  • Living architecture docs
  • Team handover
  • Complex systems

Not good for

  • Throwaway projects
  • Teams without documentation needs

Deep dive

In detail

arc42 follows a clear working logic: capture goals and stakeholders, scope context, document building blocks, describe runtime and deployment, and link risks and decisions. This turns the method into a visible thinking process rather than only a conversation. Participants move step by step from raw material, observations, or options toward a shared structure. The result is an architecture document, context view, and runtime view that make decisions, learning, or further planning actionable.

Facilitation

Prepare a clear guiding question, the right information, and a visible workspace. Plan about 1-2 days with 1-4 people and use the format either in a workshop or asynchronously. The facilitation stays lightweight; short timeboxes, visible intermediate results, and a parking lot for open questions help.

Output artifacts
Architecture DocumentContext ViewRuntime ViewDeployment View
Tags
architecturedocumentationtemplatecommunication

Sources

GitHub - arc42/arc42-template: arc42 - the template for software architecture documentation and communication · GitHubgithub.comarc42 Template Overview - arc42arc42.org
Artifact templates
arc42 Working TemplateCompact working template for arc42 with context, input, output artifacts, and next step.
markdown

arc42-working-template.md

Compact working template for arc42 with context, input, output artifacts, and next step.

arc42 Working Template

Goal

Pragmatic template for structured, living software architecture documentation.

Context

When and for what do we use this method?

Input

Which data, observations, decisions, or materials are available?

Execution

Short notes along the runsheet.

Output artifacts

  • Architecture Document:
  • Context View:
  • Runtime View:
  • Deployment View:

Assumptions and open questions

  • ...

Decision / Next step

Owner, date, and success signal.

When to choose differently

Short decision aid for existing alternatives.

Software Architecture Canvas

Statt arc42, wenn du eine Architektur auf einer kompakten, gemeinsamen Überblicksfolie rahmen willst.

Similar methods

All methods
Architecture
Views and Beyond

Turns architecture context, options, and outcomes into a tangible result by identifying stakeholders, selecting views, and validating completeness.

Architecture
Architecture Decision Record

Turns architecture context, options, and consequences into a tangible result by naming the decision, describing context, and capturing consequences.

Architecture
C4 Model

Turns architecture context, options, and consequences into a tangible result by drawing system context, identifying containers, and adding code-level detail only when needed.

Architecture
Quality Attribute Workshop

Turns architecture context, options, and consequences into a tangible result by collecting stakeholder goals, eliciting quality scenarios, and documenting architecture implications.

Architecture
Architecture Communication Canvas

Turns architecture context, options, and consequences into a tangible result by clarifying the communication goal, collecting stakeholders and audiences, and deriving a communication plan.

Architecture
Architecture Inception Canvas

Turns architecture context, options, and consequences into a tangible result by defining the problem, collecting goals and constraints, and determining next investigations.