Loading content
ARC42 provides a clear framework for documenting and communicating software architectures. The method includes various components that allow for the systematic capture and presentation of architectural decisions, requirements, and solutions.
Use this profile to understand the building block briefly, place it in the model, and switch to the 360° assessment when needed.
Executable approach: can be applied and produces an outcome.
What organizes, connects, or makes decisions possible.
ARC42 is a structured method for documenting and communicating software architectures in a concise, traceable, and team-friendly way.
arc42 grew out of practical work across many systems and domains to make software architecture not only designable, but also documentable and communicable. Peter Hruschka and Gernot Starke published the method in 2005 as an open, pragmatic template approach; it is technology-agnostic, free to use, and intended for small as well as large teams.
Think of arc42 as a scaffold with dedicated compartments. Each compartment captures a different architectural view: context and goals, constraints and quality requirements, solution strategy, building blocks, runtime behavior, distribution, cross-cutting concerns, and decisions. Teams fill the template incrementally, which keeps the documentation comparable without prescribing a specific notation or tool.
The standard provides terms for views, viewpoints, and stakeholder concerns; arc42 aligns its documentation with them.
A complementary way to present context, containers, components, and relationships clearly.
A lightweight format for recording important architecture decisions, alternatives, and reasons.
Documentation should evolve with the system and make change, risk, and quality expectations visible early.
Text-based diagrams support versionable sketches and automated generation in build and documentation pipelines.
A tool for structured architecture models, useful for consistent views and a shared model basis.
ARC42 is useful when teams need to align on architecture across roles, ease onboarding, prepare reviews, or keep a system understandable over time. Its value increases with clear ownership and regular maintenance; the template does not replace architectural decisions, and too much formality can turn it into writing overhead.
Where this building block is located in the topic model.
No structure path available.
Explore how this building block connects to concepts, methods, technologies, and tools.
These sources establish the term and its professional meaning.
All direct connections of the current building block in a compact text view.
This classification shows where the building block typically matters, how demanding it is, and what kind of impact it has in the model.
The level within the organization (enterprise, domain, team) at which the AssetBlock is applied.