ADR

• Architecture Decision Records (ADRs).

결론

컨셉자체는 괜찮은데 짜잘짜잘한거까지 하면 스트레스. 분쟁이 일어날시 팀장역활 중요.

시도

3명이서 해봤는데 adr 드라이븐을 강제해서 해봤다. 찬반으로 해서 결정하는건데 결정이 더 느리고 통과할때까지 문서만 바꾸느라 진도가 안나감.

Title: 제목
Decision: 결정
Issue:
Status: // proposed, accepted, rejected, deprecated, superseded
Expected Result: 예상결과 / Consequences 결과

버그노트
현상
추정
과정
원인
해결책

Ref:

• https://github.blog/2020-08-13-why-write-adrs/

• https://github.com/joelparkerhenderson/architecture-decision-record

• 템플릿

  • https://github.com/joelparkerhenderson/architecture-decision-record/blob/main/templates/decision-record-template-madr/index.md
  • https://github.com/joelparkerhenderson/architecture-decision-record/blob/main/templates/decision-record-template-by-michael-nygard/index.md
  • init / new / add

• 예제

  • https://github.com/joelparkerhenderson/architecture-decision-record/blob/main/examples/programming-languages/index.md

• Documenting Architecture Decisions - Michael Nygard

• https://en.wikipedia.org/wiki/Architectural_decision

• npryce/adr-tools - GPL

• https://github.com/phodal/adr - MIT

• https://bitbucket.org/tinkerer_/adr-tools-python/src/master/

• https://github.com/joelparkerhenderson/architecture-decision-record

• https://pypi.org/project/adr-tools-python/