The architecture decision record helps document informed decisions and promotes communication within the team. It allows for a transparent tracking of architectural decisions over time.
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.
An architecture decision record keeps an important architecture decision, its context, and its consequences traceable over time.
The approach became established in software architecture as short, versioned documentation of architecture decisions. Michael Nygard popularized the now common ADR format in 2011 with a template for context, decision, and consequences.
An ADR records the decision situation: context and options lead to a decision, while consequences expose later effects and open risks.
Application
Ein nachvollziehbarer Ablauf verbindet Anlass, Entscheidung und überprüfbares Ergebnis.
Die Methode braucht einen passenden Kontext und ersetzt keine fachliche Prüfung.
ADRs preserve decision knowledge and reduce later questions. They become stale when decisions are not updated or checked against the actual architecture.
Where this building block is located in the topic model.
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.