# Architectural Decision Records (ADRs)
Resources:
# Template
context: functional requirement (user story or use case) or an architecture component, facing: non-functional requirement, for instance a desired quality, we decided for: decision outcome, arguably the most important part, and neglected: alternatives not chosen (not to be forgotten!), to achieve: benefits, the full or partial satisfaction of the requirement, accepting that: drawbacks, impact on other properties/context and effort/cost.
copy success