Architecture Decision Record

Active theme: Light

← dockiments

Suggestiouns for screivin guid ADRs

Characteristics o a guid ADR:

  • Rationale: Explain the reasons for daein the particular AD. This can include the context (see ablow), pros an cons o various potential chyces, feature comparisons, cost/benefit discussiouns, an mair.

  • Specific: Each ADR sud be aboot ae AD, no a wheen o ADs.

  • Timestamps: Identify whan each item in the ADR wis written. This is especially important for aspects that micht chynge ower time, sic as costs, schedules, scalin, an the like.

  • Immutable: Dinnae alter existin information in an ADR. Instead, amend the ADR bi addin new information, or supersede the ADR bi makin a new ADR.

Characteristics o a guid "Context" section in an ADR:

  • Explain yer organisation's situation an business priorities.

  • Include rationale an considerations based on social an skills makeups o yer teams.

  • Include pros an cons that are relevant, an describe them in terms that align wi yer needs an goals.

Characteristics o guid "Consequences" section in an ADR:

  • Explain whit follaes frae makin the decisioun. This can include the effects, outcomes, outputs, follae ups, an mair.

  • Include information aboot onie subsequent ADRs. It's relatively common for ae ADR tae trigger the need for mair ADRs, sic as whan ae ADR maks a muckle owerarchin chyce, which in turn creates needs for mair smaller decisiouns.

  • Include onie efter-action review processes. It's typical for teams tae review each ADR ae month efter, tae compare the ADR information wi whit's happent in actual practice, in order tae lairn an growe.

A new ADR can tak the place o a previous ADR:

  • Whan an AD is made that replaces or invalidates a previous ADR, than a new ADR sud be creatit