ISO 42010–inspired (architecture description record)
This is not “ISO 42010 as an ADR format.” It is a decision record that uses 42010 vocabulary: stakeholders, concerns, and views, so a decision is traceable to the architecture description.
Use it when a decision is inseparable from who is affected, which quality concerns drive it, and which view (e.g. deployment, security) must change. For background, read ISO / IEEE 42010 and decisions.
Switch format
Markdown template
# <short title>
> **Architecture description record (ISO/IEC/IEEE 42010–inspired).** Not a full conformity assessment—use to align *concerns* and *views* with a decision.
**Record ID / cross-ref:** <ADR-42010-0001 or your scheme>
## System / subject scope
<what system of interest is described>
## Stakeholders and roles
<who may be affected or who must read this description>
## Stakeholder concerns
<reliability, cost, lawfulness, modifiability, … as relevant to this view>
## View and viewpoint
<name the viewpoint, e.g. security / deployment, and the view, e.g. C4 L2, cluster map>
## Decision
<one clear architecture decision the description must reflect>
## Rationale
<reference alternatives or constraints, tied to the concerns above>
## Architectural impact
<what in the as-built or to-be design changes>
## Traceability
<links: requirements, policies, SLOs, other ADRs>
Open generator with this format preselected (also persisted in local storage on this site).