Architectural Decision Records
Version | Status | Authors | Decision Makers |
0.0.1 | Proposed | @Ali González | Architectural Committee |
From Architectural Decision Records (ADRs):
An Architectural Decision (AD) is a justified design choice that addresses a functional or non-functional requirement that is architecturally significant. An Architecturally Significant Requirement (ASR) is a requirement that has a measurable effect on the architecture and quality of a software and/or hardware system. An Architectural Decision Record (ADR) captures a single AD and its rationale; Put it simply, ADR can help you understand the reasons for a chosen architectural decision, along with its trade-offs and consequences.
The collection of ADRs created and maintained in a project constitute its decision log. All these are within the topic of Architectural Knowledge Management (AKM), but ADR usage can be extended to design and other decisions (“any decision record”).
This document will record and store any ADRs made by the Architecture Committee, or decisions refactoring or roadmap decisions taken by a Working Group and reviewed by the Architecture Committee on a Decision Log so that they can be consulted and referenced.
References
Decision Log
ADR Number | Date | Title | Status |
---|---|---|---|
2025-02-06 | eIDAS Compatibility for Wallet Building Block | DRAFT |