Architecture Decision Record
← dokument

How to start use ADR

To start use ADR, talk with your teammates about dis areas.

Decision identification:

  • How urgent and how important be di AD?

  • E must make now, or e fit wait until dem know more?

  • Both personal and collective experience, and also recognized design methods and practices, fit help with decision identification.

  • Ideally, maintain decision todo list wey go complement di product todo list.

Decision making:

  • Plenty decision making techniques dey, both general ones and software architecture specific ones, for instance, dialogue mapping.

  • Group decision making na active research topic.

Decision enactment and enforcement:

  • Dem dey use ADs for software design; so dem must communicate dem to di stakeholders of di system wey dey fund am, develop am, and operate am, and di stakeholders must accept dem.

  • Architecturally evident coding styles and code reviews wey focus on architectural concerns and decisions na two related practices.

  • Dem must also (re-)consider ADs wen dem dey modernize one software system for software evolution.

Decision sharing (optional):

  • Plenty ADs dey recur across projects.

  • So, experiences with past decisions, both good and bad, fit be valuable reusable assets wen you dey use explicit knowledge management strategy.

Decision documentation:

  • Plenty templates and tools dey for decision capturing.

  • Check agile communities, e.g. M. Nygard's ADRs.

  • Check traditional software engineering and architecture design processes, e.g. table layouts wey IBM UMF and Tyree and Akerman from CapitalOne suggest.

For more: