adr   233

« earlier    

Architecture decision record (ADR)
Architecture decision record (ADR) examples for software planning, IT leadership, and template documenation.

Github repo for templates and examples for ADRs. See also
adr  architecture  design  documentation  examples  templates 
17 days ago by drmeme
Documenting Architecture Decisions
An architecture decision record is a short text file in a format similar to an Alexandrian pattern. (Though the decisions themselves are not necessarily patterns, they share the characteristic balancing of forces.) Each record describes a set of forces and a single decision in response to those forces. Note that the decision is the central piece here, so specific forces may appear in multiple ADRs.

ADRs consist of:

1. Title: These documents have names that are short noun phrases. For example, "ADR 1: Deployment on Ruby on Rails 3.0.10" or "ADR 9: LDAP for Multitenant Integration"

2. Context: This section describes the forces at play, including technological, political, social, and project local. These forces are probably in tension, and should be called out as such. The language in this section is value-neutral. It is simply describing facts.

3. Decision: This section describes our response to these forces. It is stated in full sentences, with active voice. "We will ..."

4. Status: A decision may be "proposed" if the project stakeholders haven't agreed with it yet, or "accepted" once it is agreed. If a later ADR changes or reverses a decision, it may be marked as "deprecated" or "superseded" with a reference to its replacement.

5. Consequences: This section describes the resulting context, after applying the decision. All consequences should be listed here, not just the "positive" ones. A particular decision may have positive, negative, and neutral consequences, but all of them affect the team and project in the future.
agile  architecture  design  decision  adr  documentation  documents 
17 days ago by drmeme
Architectural Decision Records
I really like Architecture Decision Records * Making a decision as a team * Choosing the best one for the system as it exists today * Recording not only WHY the decision was made but also trade offs that occur because of the decision.
adr  architecture 
october 2019 by cdwillie76
F53 | Streamers Documentation
streamer overlays - works with Pro Tools and other software
ADR  ProTools  Studio  Software  Video  Tools 
october 2019 by jeremiahmoore

« earlier    

related tags

adrs  agile  alternative-dispute-resolution  apple  applications  architect  architectural  architecture  architecturedocumentation  archive  asset  best_market_server  blog  business  cedear  christianity  cli  contracts  coreos  corporations  cusip  decision-making  decision  decisions  design  dev  development  disk  documentary  documentation  documents  engineering  envato  etcd  examples  fpi  games  git  github  hardware  herramientas  intel  inversion  invesrting  ios  ipo  isin  journal  kubernetes  law  learn  learning  linux  longreads  markdown  mediation  microservices  miso  muckreads  mvc  newyorktimes  nrc  nrg  online  osx  otc  paper  pattern  patterns  performance  persistence  php  planthealth  process  programming  protection  protools  radak  radio  raft  record  religion  remote  rfc  rkn  securities  server  slides  software-engineering  software  softwarearchitecture  softwareengineering  sound  spoilers  stock  storage  studio  sudoku  sumochallenge  tech-choice  tech-radar  technical-debt  templates  terminal  thoughtworks-tech-radar  thoughtworks  tools  transporte  trials  tutoriales  twitter  usd  video  virginia  web-development  webdev  xeon 

Copy this bookmark: