├── locales ├── README.md ├── zh │ ├── 文档 │ │ ├── .empty │ │ ├── README.md │ │ ├── how-to-start-using-adrs │ │ │ ├── README.md │ │ │ └── index.md │ │ ├── how-to-start-using-adrs-with-tools │ │ │ ├── README.md │ │ │ └── index.md │ │ ├── what-is-an-architecture-decision-record │ │ │ ├── README.md │ │ │ └── index.md │ │ └── how-to-start-using-adrs-with-git │ │ │ └── index.md │ ├── 案例 │ │ └── .empty │ └── 模板 │ │ └── .empty ├── ko │ ├── 템플릿 │ │ ├── README.md │ │ ├── madr 프로젝트의 결정 기록 템플릿 │ │ │ ├── README.md │ │ │ ├── .locale-peer-id │ │ │ └── index.md │ │ ├── 결정 기록 템플릿별 edgex │ │ │ ├── README.md │ │ │ ├── .locale-peer-id │ │ │ └── index.md │ │ ├── 의사결정 기록 템플릿 사용 p언어 │ │ │ ├── README.md │ │ │ ├── .locale-peer-id │ │ │ └── index.md │ │ ├── 비즈니스 사례에 대한 의사결정 기록 템플릿 │ │ │ ├── README.md │ │ │ ├── .locale-peer-id │ │ │ └── index.md │ │ ├── 알렉산드리아 패턴에 대한 결정 기록 템플릿 │ │ │ ├── README.md │ │ │ ├── .locale-peer-id │ │ │ └── index.md │ │ ├── 의사 결정 기록 템플릿-by-michael-nygard │ │ │ ├── README.md │ │ │ ├── .locale-peer-id │ │ │ └── index.md │ │ ├── .locale-peer-id │ │ ├── 의사결정 기록 템플릿-by-jeff-tyree-and-art-akerman │ │ │ ├── README.md │ │ │ ├── .locale-peer-id │ │ │ └── index.md │ │ └── index.md │ ├── 서류 │ │ ├── 파일-이름-규칙 │ │ │ ├── README.md │ │ │ ├── .locale-peer-id │ │ │ └── index.md │ │ ├── adr-사용을-시작하는-방법 │ │ │ ├── README.md │ │ │ ├── .locale-peer-id │ │ │ └── index.md │ │ ├── adr을-위한-팀워크-조언 │ │ │ ├── README.md │ │ │ ├── .locale-peer-id │ │ │ └── index.md │ │ ├── 의사결정-지속가능성-기준 │ │ │ ├── README.md │ │ │ ├── .locale-peer-id │ │ │ └── index.md │ │ ├── 좋은-adr-작성을-위한-제안 │ │ │ ├── README.md │ │ │ ├── .locale-peer-id │ │ │ └── index.md │ │ ├── aws-아키텍처-결정-기록-프로세스 │ │ │ ├── README.md │ │ │ └── .locale-peer-id │ │ ├── git에서-adr-사용을-시작하는-방법 │ │ │ ├── README.md │ │ │ ├── .locale-peer-id │ │ │ └── index.md │ │ ├── 아키텍처-결정-기록이란-무엇입니까 │ │ │ ├── README.md │ │ │ ├── .locale-peer-id │ │ │ └── index.md │ │ ├── 지속-가능한-결정을-달성하기-위한-지침 │ │ │ ├── README.md │ │ │ ├── .locale-peer-id │ │ │ └── index.md │ │ ├── 도구를-사용하여-adr-사용을-시작하는-방법 │ │ │ ├── README.md │ │ │ ├── .locale-peer-id │ │ │ └── index.md │ │ └── .locale-peer-id │ └── .locale-peer-id ├── cy │ ├── templedi │ │ ├── README.md │ │ ├── .locale-peer-id │ │ ├── templed-cofnod-penderfyniad-gan-edgex │ │ │ ├── README.md │ │ │ └── .locale-peer-id │ │ ├── templed-cofnod-penderfyniad-gan-planguage │ │ │ ├── README.md │ │ │ ├── .locale-peer-id │ │ │ └── index.md │ │ ├── templed-cofnod-penderfyniad-y-prosiect-madr │ │ │ ├── README.md │ │ │ └── .locale-peer-id │ │ ├── templed-cofnod-penderfyniad-ar-gyfer-achos-busnes │ │ │ ├── README.md │ │ │ └── .locale-peer-id │ │ ├── templed-cofnod-penderfyniad-gan-michael-nygard │ │ │ ├── README.md │ │ │ ├── .locale-peer-id │ │ │ └── index.md │ │ ├── templed-cofnod-penderfyniad-ar-gyfer-patrwm-alecsandraidd │ │ │ ├── README.md │ │ │ ├── .locale-peer-id │ │ │ └── index.md │ │ ├── templed-cofnod-penderfyniad-gan-jeff-tyree-and-art-akerman │ │ │ ├── README.md │ │ │ └── .locale-peer-id │ │ └── index.md │ ├── .locale-peer-id │ └── nogfennau │ │ ├── confensiynau-enw-ffeil │ │ ├── README.md │ │ ├── .locale-peer-id │ │ └── index.md │ │ ├── sut-i-ddechrau-defnyddio-adrs │ │ ├── README.md │ │ ├── .locale-peer-id │ │ └── index.md │ │ ├── .locale-peer-id │ │ ├── cyngor-gwaith-tîm-ar-gyfer-adrs │ │ ├── README.md │ │ ├── .locale-peer-id │ │ └── index.md │ │ ├── awgrymiadau-ar-gyfer-ysgrifennu-adrs-da │ │ ├── README.md │ │ ├── .locale-peer-id │ │ └── index.md │ │ ├── cwestiynau-gwaith-tîm-ar-gyfer-adrau │ │ ├── README.md │ │ └── .locale-peer-id │ │ ├── meini-prawf-cynaliadwyedd-penderfynu │ │ ├── README.md │ │ ├── .locale-peer-id │ │ └── index.md │ │ ├── sut-i-ddechrau-defnyddio-adrs-gyda-git │ │ ├── README.md │ │ ├── .locale-peer-id │ │ └── index.md │ │ ├── beth-yw-cofnod-penderfyniad-pensaernïaeth │ │ ├── README.md │ │ ├── .locale-peer-id │ │ └── index.md │ │ ├── proses-cofnodion-penderfynol-pensaernïol-aws │ │ ├── README.md │ │ └── .locale-peer-id │ │ ├── sut-i-ddechrau-defnyddio-adrs-gydag-offer │ │ ├── README.md │ │ ├── .locale-peer-id │ │ └── index.md │ │ └── canllawiau-i-gyflawni-penderfyniadau-cynaliadwy │ │ ├── README.md │ │ ├── .locale-peer-id │ │ └── index.md ├── en │ ├── examples │ │ ├── README.md │ │ ├── .locale-peer-id │ │ ├── 4-day-work-week │ │ │ ├── README.md │ │ │ └── .locale-peer-id │ │ ├── css-framework │ │ │ ├── README.md │ │ │ └── .locale-peer-id │ │ ├── mysql-database │ │ │ ├── README.md │ │ │ └── .locale-peer-id │ │ ├── secrets-storage │ │ │ ├── README.md │ │ │ └── .locale-peer-id │ │ ├── tailwind-css │ │ │ ├── README.md │ │ │ └── .locale-peer-id │ │ ├── work-from-home │ │ │ ├── README.md │ │ │ └── .locale-peer-id │ │ ├── amazon-web-services │ │ │ ├── README.md │ │ │ ├── .locale-peer-id │ │ │ └── index.md │ │ ├── high-trust-teamwork │ │ │ ├── README.md │ │ │ ├── .locale-peer-id │ │ │ └── index.md │ │ ├── postgresql-database │ │ │ ├── README.md │ │ │ ├── .locale-peer-id │ │ │ └── index.md │ │ ├── svelte-components │ │ │ └── README.md │ │ ├── sveltekit-framework │ │ │ ├── README.md │ │ │ ├── .locale-peer-id │ │ │ └── index.md │ │ ├── timestamp-format │ │ │ ├── README.md │ │ │ └── .locale-peer-id │ │ ├── api-using-json-v-grpc │ │ │ ├── README.md │ │ │ ├── .locale-peer-id │ │ │ └── index.md │ │ ├── continuous-integration │ │ │ ├── README.md │ │ │ ├── .locale-peer-id │ │ │ └── index.md │ │ ├── go-programming-language │ │ │ ├── README.md │ │ │ └── .locale-peer-id │ │ ├── google-cloud-platform │ │ │ ├── README.md │ │ │ ├── .locale-peer-id │ │ │ └── index.md │ │ ├── java-programming-language │ │ │ ├── README.md │ │ │ ├── .locale-peer-id │ │ │ └── index.md │ │ ├── metrics-monitors-alerts │ │ │ ├── README.md │ │ │ └── .locale-peer-id │ │ ├── microsoft-azure-devops │ │ │ ├── README.md │ │ │ └── .locale-peer-id │ │ ├── monorepo-vs-multirepo │ │ │ ├── README.md │ │ │ └── .locale-peer-id │ │ ├── programming-code-editors │ │ │ ├── README.md │ │ │ └── .locale-peer-id │ │ ├── programming-languages │ │ │ ├── README.md │ │ │ └── .locale-peer-id │ │ ├── python-django-framework │ │ │ ├── README.md │ │ │ └── .locale-peer-id │ │ ├── ruby-on-rails-framework │ │ │ ├── README.md │ │ │ ├── .locale-peer-id │ │ │ └── index.md │ │ ├── rust-programming-language │ │ │ ├── README.md │ │ │ └── .locale-peer-id │ │ ├── agile-software-development │ │ │ ├── README.md │ │ │ ├── .locale-peer-id │ │ │ └── index.md │ │ ├── choosing-a-database-technology │ │ │ ├── README.md │ │ │ └── .locale-peer-id │ │ ├── python-programming-language │ │ │ ├── README.md │ │ │ └── .locale-peer-id │ │ ├── environment-variable-configuration │ │ │ ├── README.md │ │ │ └── .locale-peer-id │ │ ├── kubernetes-container-orchestration │ │ │ ├── README.md │ │ │ ├── .locale-peer-id │ │ │ └── index.md │ │ ├── react-front-end-javascript-library │ │ │ ├── README.md │ │ │ └── .locale-peer-id │ │ ├── svelte-front-end-javascript-library │ │ │ ├── README.md │ │ │ └── .locale-peer-id │ │ ├── vue-front-end-javascript-library │ │ │ ├── README.md │ │ │ ├── .locale-peer-id │ │ │ └── index.md │ │ ├── authentication-authorization-options │ │ │ └── README.md │ │ ├── docker-swarm-container-orchestration │ │ │ ├── README.md │ │ │ └── .locale-peer-id │ │ ├── microsoft-azure-cloud-infrastructure │ │ │ ├── README.md │ │ │ └── .locale-peer-id │ │ ├── snake-case-v-camelcase-for-a-rest-api │ │ │ ├── README.md │ │ │ └── .locale-peer-id │ │ ├── browser-automation-framework-for-e2e-testing-playwright-vs-selenium │ │ │ └── README.md │ │ ├── chart-library-toolkit-for-data-visualization-using-typescript-and-json │ │ │ └── README.md │ │ ├── web-application-framework-batteries-included-full-stack-for-a-startup-product │ │ │ └── README.md │ │ └── index.md │ ├── templates │ │ ├── README.md │ │ ├── .locale-peer-id │ │ ├── decision-record-template-by-arc42 │ │ │ └── README.md │ │ ├── decision-record-template-by-edgex │ │ │ ├── README.md │ │ │ └── .locale-peer-id │ │ ├── decision-record-template-by-gareth-morgan │ │ │ └── README.md │ │ ├── decision-record-template-by-michael-nygard │ │ │ ├── README.md │ │ │ ├── .locale-peer-id │ │ │ └── index.md │ │ ├── decision-record-template-for-business-case │ │ │ ├── README.md │ │ │ └── .locale-peer-id │ │ ├── decision-record-template-of-the-madr-project │ │ │ ├── README.md │ │ │ ├── .locale-peer-id │ │ │ └── index.md │ │ ├── decision-record-template-using-planguage │ │ │ ├── README.md │ │ │ ├── .locale-peer-id │ │ │ └── index.md │ │ ├── decision-record-template-by-gig-cymru-nhs-wales │ │ │ └── README.md │ │ ├── decision-record-template-for-alexandrian-pattern │ │ │ ├── README.md │ │ │ ├── .locale-peer-id │ │ │ └── index.md │ │ ├── decision-record-template-by-jeff-tyree-and-art-akerman │ │ │ ├── README.md │ │ │ └── .locale-peer-id │ │ └── index.md │ ├── documents │ │ ├── aws-adr-process │ │ │ ├── README.md │ │ │ └── .locale-peer-id │ │ ├── how-to-start-using-adrs │ │ │ ├── README.md │ │ │ ├── .locale-peer-id │ │ │ └── index.md │ │ ├── teamwork-advice-for-adrs │ │ │ ├── README.md │ │ │ ├── .locale-peer-id │ │ │ └── index.md │ │ ├── teamwork-questions-for-adrs │ │ │ ├── README.md │ │ │ └── .locale-peer-id │ │ ├── .locale-peer-id │ │ ├── decision-sustainability-criteria │ │ │ ├── README.md │ │ │ ├── .locale-peer-id │ │ │ └── index.md │ │ ├── file-name-conventions-for-adrs │ │ │ ├── README.md │ │ │ ├── .locale-peer-id │ │ │ └── index.md │ │ ├── how-to-start-using-adrs-with-git │ │ │ ├── README.md │ │ │ ├── .locale-peer-id │ │ │ └── index.md │ │ ├── how-to-start-using-adrs-with-tools │ │ │ ├── README.md │ │ │ ├── .locale-peer-id │ │ │ └── index.md │ │ ├── suggestions-for-writing-good-adrs │ │ │ ├── README.md │ │ │ ├── .locale-peer-id │ │ │ └── index.md │ │ ├── what-is-an-architecture-decision-record │ │ │ ├── README.md │ │ │ ├── .locale-peer-id │ │ │ └── index.md │ │ └── guidelines-to-achieve-sustainable-decisions │ │ │ ├── README.md │ │ │ ├── .locale-peer-id │ │ │ └── index.md │ └── .locale-peer-id ├── fr │ ├── modèles │ │ ├── README.md │ │ ├── .locale-peer-id │ │ ├── modèle-denregistrement-de-décision-par-edgex │ │ │ ├── README.md │ │ │ └── .locale-peer-id │ │ ├── modèle-denregistrement-de-décision-du-projet-madr │ │ │ ├── README.md │ │ │ └── .locale-peer-id │ │ ├── modèle-denregistrement-de-décision utilisant-plangage │ │ │ ├── README.md │ │ │ ├── .locale-peer-id │ │ │ └── index.md │ │ ├── modèle-denregistrement-de-décision-par michael-nygard │ │ │ ├── README.md │ │ │ ├── .locale-peer-id │ │ │ └── index.md │ │ ├── modèle-denregistrement-de-décision-pour-le modèle-alexandrin │ │ │ ├── README.md │ │ │ ├── .locale-peer-id │ │ │ └── index.md │ │ ├── modèle-denregistrement-de-décision par jeff-tyree-et-art-akerman │ │ │ ├── README.md │ │ │ └── .locale-peer-id │ │ ├── modèle-denregistrement-de-décision pour-lanalyse-de-rentabilisation │ │ │ ├── README.md │ │ │ └── .locale-peer-id │ │ └── index.md │ ├── .locale-peer-id │ └── documents │ │ ├── .locale-peer-id │ │ ├── conventions-de-noms-de-fichiers │ │ ├── README.md │ │ ├── .locale-peer-id │ │ └── index.md │ │ ├── critères-de-durabilité-de-décision │ │ ├── README.md │ │ ├── .locale-peer-id │ │ └── index.md │ │ ├── comment-commencer-à-utiliser-les-adr │ │ ├── README.md │ │ ├── .locale-peer-id │ │ └── index.md │ │ ├── suggestions-pour-écrire-de-bonnes-adr │ │ ├── README.md │ │ ├── .locale-peer-id │ │ └── index.md │ │ ├── conseils-de-travail-déquipe-pour-les-adr │ │ ├── README.md │ │ ├── .locale-peer-id │ │ └── index.md │ │ ├── comment-commencer-à-utiliser-les-adr-avec-git │ │ ├── README.md │ │ ├── .locale-peer-id │ │ └── index.md │ │ ├── quest-ce-quun-dossier-de-décision-darchitecture │ │ ├── README.md │ │ ├── .locale-peer-id │ │ └── index.md │ │ ├── comment-commencer-à-utiliser-les-adr-avec-des-outils │ │ ├── README.md │ │ ├── .locale-peer-id │ │ └── index.md │ │ ├── processus-des-dossiers-de-décision-architecturale-aws │ │ ├── README.md │ │ └── .locale-peer-id │ │ └── lignes-directrices-pour-atteindre-des-décisions-durables │ │ ├── README.md │ │ ├── .locale-peer-id │ │ └── index.md ├── ja │ ├── テンプレート │ │ ├── README.md │ │ ├── ビジネスケース用意思決定記録テンプレート │ │ │ ├── README.md │ │ │ ├── .locale-peer-id │ │ │ └── index.md │ │ ├── Planguageを使用した意思決定記録テンプレート │ │ │ ├── README.md │ │ │ ├── .locale-peer-id │ │ │ └── index.md │ │ ├── madrプロジェクトの意思決定記録テンプレート │ │ │ ├── README.md │ │ │ ├── .locale-peer-id │ │ │ └── index.md │ │ ├── アレクサンドリアパターンの意思決定記録テンプレート │ │ │ ├── README.md │ │ │ ├── .locale-peer-id │ │ │ └── index.md │ │ ├── EdgeX Foundryによる意思決定記録テンプレート │ │ │ ├── README.md │ │ │ ├── .locale-peer-id │ │ │ └── index.md │ │ ├── Michael Nygard による意思決定記録テンプレート │ │ │ ├── README.md │ │ │ ├── .locale-peer-id │ │ │ └── index.md │ │ ├── .locale-peer-id │ │ ├── Jeff TyreeとArt Akermanによる意思決定記録テンプレート │ │ │ ├── README.md │ │ │ ├── .locale-peer-id │ │ │ └── index.md │ │ └── index.md │ ├── ドキュメント │ │ ├── aws-adr-process │ │ │ ├── README.md │ │ │ └── .locale-peer-id │ │ ├── how-to-start-using-adrs │ │ │ ├── README.md │ │ │ ├── .locale-peer-id │ │ │ └── index.md │ │ ├── teamwork-advice-for-adrs │ │ │ ├── README.md │ │ │ ├── .locale-peer-id │ │ │ └── index.md │ │ ├── decision-sustainability-criteria │ │ │ ├── README.md │ │ │ ├── .locale-peer-id │ │ │ └── index.md │ │ ├── file-name-conventions-for-adrs │ │ │ ├── README.md │ │ │ ├── .locale-peer-id │ │ │ └── index.md │ │ ├── how-to-start-using-adrs-with-git │ │ │ ├── README.md │ │ │ ├── .locale-peer-id │ │ │ └── index.md │ │ ├── .locale-peer-id │ │ ├── how-to-start-using-adrs-with-tools │ │ │ ├── README.md │ │ │ ├── .locale-peer-id │ │ │ └── index.md │ │ ├── suggestions-for-writing-good-adrs │ │ │ ├── README.md │ │ │ ├── .locale-peer-id │ │ │ └── index.md │ │ ├── what-is-an-architecture-decision-record │ │ │ ├── README.md │ │ │ ├── .locale-peer-id │ │ │ └── index.md │ │ └── guidelines-to-achieve-sustainable-decisions │ │ │ ├── README.md │ │ │ ├── .locale-peer-id │ │ │ └── index.md │ ├── .locale-peer-id │ └── 翻訳注.txt ├── es │ ├── plantillas │ │ ├── README.md │ │ ├── .locale-peer-id │ │ ├── plantilla-de-registro-de-decisión-de-edgex │ │ │ ├── README.md │ │ │ └── .locale-peer-id │ │ ├── plantilla-de-registro-de-decisión-de-michael-nygard │ │ │ ├── README.md │ │ │ ├── .locale-peer-id │ │ │ └── index.md │ │ ├── plantilla-de-registro-de-decisión-del-proyecto-madr │ │ │ ├── README.md │ │ │ └── .locale-peer-id │ │ ├── plantilla-de-registro-de-decisión-usando-planguage │ │ │ ├── README.md │ │ │ ├── .locale-peer-id │ │ │ └── .locale-directory-name-en.txt │ │ ├── plantilla-de-registro-de-decisión-para-caso-de-negocio │ │ │ ├── README.md │ │ │ └── .locale-peer-id │ │ ├── plantilla-de-registro-de-decisión-de-jeff-tyree-y-art-akerman │ │ │ ├── README.md │ │ │ └── .locale-peer-id │ │ ├── plantilla-de-registro-de-decisión-para-el-patrón-alejandrino │ │ │ ├── README.md │ │ │ ├── .locale-peer-id │ │ │ └── index.md │ │ └── index.md │ ├── .locale-peer-id │ └── documentos │ │ ├── cómo-comenzar-a-usar-adrs │ │ ├── README.md │ │ ├── .locale-peer-id │ │ └── index.md │ │ ├── convenciones-de-nombre-de-archivo │ │ ├── README.md │ │ ├── .locale-peer-id │ │ └── index.md │ │ ├── cómo-comenzar-a-usar-adr-con-git │ │ ├── README.md │ │ ├── .locale-peer-id │ │ └── index.md │ │ ├── .locale-peer-id │ │ ├── consejo-de-trabajo-en-equipo-para-adrs │ │ ├── README.md │ │ ├── .locale-peer-id │ │ └── index.md │ │ ├── sugerencias-para-escribir-buenos-adr │ │ ├── README.md │ │ ├── .locale-peer-id │ │ └── index.md │ │ ├── criterios-de-sostenibilidad-de-decisión │ │ ├── README.md │ │ ├── .locale-peer-id │ │ └── index.md │ │ ├── cómo-comenzar-a-usar-adr-con-herramientas │ │ ├── README.md │ │ ├── .locale-peer-id │ │ └── index.md │ │ ├── directrices-para-lograr-decisiones-sostenibles │ │ ├── README.md │ │ ├── .locale-peer-id │ │ └── index.md │ │ ├── qué-es-un-registro-de-decisión-de-arquitectura │ │ ├── README.md │ │ ├── .locale-peer-id │ │ └── index.md │ │ └── proceso-de-registros-de-decisiones-arquitectónicas-de-aws │ │ ├── README.md │ │ └── .locale-peer-id └── index.md ├── LICENSE.md └── CITATION.cff /locales/README.md: -------------------------------------------------------------------------------- 1 | index.md -------------------------------------------------------------------------------- /locales/zh/文档/.empty: -------------------------------------------------------------------------------- 1 | 2 | -------------------------------------------------------------------------------- /locales/zh/案例/.empty: -------------------------------------------------------------------------------- 1 | 2 | -------------------------------------------------------------------------------- /locales/zh/模板/.empty: -------------------------------------------------------------------------------- 1 | 2 | -------------------------------------------------------------------------------- /locales/ko/템플릿/README.md: -------------------------------------------------------------------------------- 1 | index.md -------------------------------------------------------------------------------- /locales/zh/文档/README.md: -------------------------------------------------------------------------------- 1 | 文档 2 | -------------------------------------------------------------------------------- /locales/cy/templedi/README.md: -------------------------------------------------------------------------------- 1 | index.md -------------------------------------------------------------------------------- /locales/en/examples/README.md: -------------------------------------------------------------------------------- 1 | index.md -------------------------------------------------------------------------------- /locales/en/templates/README.md: -------------------------------------------------------------------------------- 1 | index.md -------------------------------------------------------------------------------- /locales/fr/modèles/README.md: -------------------------------------------------------------------------------- 1 | index.md -------------------------------------------------------------------------------- /locales/ja/テンプレート/README.md: -------------------------------------------------------------------------------- 1 | index.md -------------------------------------------------------------------------------- /locales/en/examples/.locale-peer-id: -------------------------------------------------------------------------------- 1 | 2 | -------------------------------------------------------------------------------- /locales/es/plantillas/README.md: -------------------------------------------------------------------------------- 1 | index.md -------------------------------------------------------------------------------- /locales/ko/서류/파일-이름-규칙/README.md: -------------------------------------------------------------------------------- 1 | index.md -------------------------------------------------------------------------------- /locales/ko/서류/adr-사용을-시작하는-방법/README.md: -------------------------------------------------------------------------------- 1 | index.md -------------------------------------------------------------------------------- /locales/ko/서류/adr을-위한-팀워크-조언/README.md: -------------------------------------------------------------------------------- 1 | index.md -------------------------------------------------------------------------------- /locales/ko/서류/의사결정-지속가능성-기준/README.md: -------------------------------------------------------------------------------- 1 | index.md -------------------------------------------------------------------------------- /locales/ko/서류/좋은-adr-작성을-위한-제안/README.md: -------------------------------------------------------------------------------- 1 | index.md -------------------------------------------------------------------------------- /locales/en/examples/4-day-work-week/README.md: -------------------------------------------------------------------------------- 1 | index.md -------------------------------------------------------------------------------- /locales/en/examples/css-framework/README.md: -------------------------------------------------------------------------------- 1 | index.md -------------------------------------------------------------------------------- /locales/en/examples/mysql-database/README.md: -------------------------------------------------------------------------------- 1 | index.md -------------------------------------------------------------------------------- /locales/en/examples/secrets-storage/README.md: -------------------------------------------------------------------------------- 1 | index.md -------------------------------------------------------------------------------- /locales/en/examples/tailwind-css/README.md: -------------------------------------------------------------------------------- 1 | index.md -------------------------------------------------------------------------------- /locales/en/examples/work-from-home/README.md: -------------------------------------------------------------------------------- 1 | index.md -------------------------------------------------------------------------------- /locales/ja/ドキュメント/aws-adr-process/README.md: -------------------------------------------------------------------------------- 1 | index.md -------------------------------------------------------------------------------- /locales/ko/서류/aws-아키텍처-결정-기록-프로세스/README.md: -------------------------------------------------------------------------------- 1 | index.md -------------------------------------------------------------------------------- /locales/ko/서류/git에서-adr-사용을-시작하는-방법/README.md: -------------------------------------------------------------------------------- 1 | index.md -------------------------------------------------------------------------------- /locales/ko/서류/아키텍처-결정-기록이란-무엇입니까/README.md: -------------------------------------------------------------------------------- 1 | index.md -------------------------------------------------------------------------------- /locales/ko/서류/지속-가능한-결정을-달성하기-위한-지침/README.md: -------------------------------------------------------------------------------- 1 | index.md -------------------------------------------------------------------------------- /locales/ko/템플릿/madr 프로젝트의 결정 기록 템플릿/README.md: -------------------------------------------------------------------------------- 1 | index.md -------------------------------------------------------------------------------- /locales/ko/템플릿/결정 기록 템플릿별 edgex/README.md: -------------------------------------------------------------------------------- 1 | index.md -------------------------------------------------------------------------------- /locales/ko/템플릿/의사결정 기록 템플릿 사용 p언어/README.md: -------------------------------------------------------------------------------- 1 | index.md -------------------------------------------------------------------------------- /locales/en/documents/aws-adr-process/README.md: -------------------------------------------------------------------------------- 1 | index.md -------------------------------------------------------------------------------- /locales/en/examples/amazon-web-services/README.md: -------------------------------------------------------------------------------- 1 | index.md -------------------------------------------------------------------------------- /locales/en/examples/high-trust-teamwork/README.md: -------------------------------------------------------------------------------- 1 | index.md -------------------------------------------------------------------------------- /locales/en/examples/postgresql-database/README.md: -------------------------------------------------------------------------------- 1 | index.md -------------------------------------------------------------------------------- /locales/en/examples/svelte-components/README.md: -------------------------------------------------------------------------------- 1 | index.md -------------------------------------------------------------------------------- /locales/en/examples/sveltekit-framework/README.md: -------------------------------------------------------------------------------- 1 | index.md -------------------------------------------------------------------------------- /locales/en/examples/timestamp-format/README.md: -------------------------------------------------------------------------------- 1 | index.md -------------------------------------------------------------------------------- /locales/ja/テンプレート/ビジネスケース用意思決定記録テンプレート/README.md: -------------------------------------------------------------------------------- 1 | index.md -------------------------------------------------------------------------------- /locales/ko/서류/도구를-사용하여-adr-사용을-시작하는-방법/README.md: -------------------------------------------------------------------------------- 1 | index.md -------------------------------------------------------------------------------- /locales/ko/템플릿/비즈니스 사례에 대한 의사결정 기록 템플릿/README.md: -------------------------------------------------------------------------------- 1 | index.md -------------------------------------------------------------------------------- /locales/ko/템플릿/알렉산드리아 패턴에 대한 결정 기록 템플릿/README.md: -------------------------------------------------------------------------------- 1 | index.md -------------------------------------------------------------------------------- /locales/cy/.locale-peer-id: -------------------------------------------------------------------------------- 1 | 0b59cb46e5817b414866ebe33f4d7bcf 2 | -------------------------------------------------------------------------------- /locales/cy/nogfennau/confensiynau-enw-ffeil/README.md: -------------------------------------------------------------------------------- 1 | index.md -------------------------------------------------------------------------------- /locales/en/.locale-peer-id: -------------------------------------------------------------------------------- 1 | 0b59cb46e5817b414866ebe33f4d7bcf 2 | -------------------------------------------------------------------------------- /locales/en/documents/how-to-start-using-adrs/README.md: -------------------------------------------------------------------------------- 1 | index.md -------------------------------------------------------------------------------- /locales/en/documents/teamwork-advice-for-adrs/README.md: -------------------------------------------------------------------------------- 1 | index.md -------------------------------------------------------------------------------- /locales/en/examples/api-using-json-v-grpc/README.md: -------------------------------------------------------------------------------- 1 | index.md -------------------------------------------------------------------------------- /locales/en/examples/continuous-integration/README.md: -------------------------------------------------------------------------------- 1 | index.md -------------------------------------------------------------------------------- /locales/en/examples/go-programming-language/README.md: -------------------------------------------------------------------------------- 1 | index.md -------------------------------------------------------------------------------- /locales/en/examples/google-cloud-platform/README.md: -------------------------------------------------------------------------------- 1 | index.md -------------------------------------------------------------------------------- /locales/en/examples/java-programming-language/README.md: -------------------------------------------------------------------------------- 1 | index.md -------------------------------------------------------------------------------- /locales/en/examples/metrics-monitors-alerts/README.md: -------------------------------------------------------------------------------- 1 | index.md -------------------------------------------------------------------------------- /locales/en/examples/microsoft-azure-devops/README.md: -------------------------------------------------------------------------------- 1 | index.md -------------------------------------------------------------------------------- /locales/en/examples/monorepo-vs-multirepo/README.md: -------------------------------------------------------------------------------- 1 | index.md -------------------------------------------------------------------------------- /locales/en/examples/programming-code-editors/README.md: -------------------------------------------------------------------------------- 1 | index.md -------------------------------------------------------------------------------- /locales/en/examples/programming-languages/README.md: -------------------------------------------------------------------------------- 1 | index.md -------------------------------------------------------------------------------- /locales/en/examples/python-django-framework/README.md: -------------------------------------------------------------------------------- 1 | index.md -------------------------------------------------------------------------------- /locales/en/examples/ruby-on-rails-framework/README.md: -------------------------------------------------------------------------------- 1 | index.md -------------------------------------------------------------------------------- /locales/en/examples/rust-programming-language/README.md: -------------------------------------------------------------------------------- 1 | index.md -------------------------------------------------------------------------------- /locales/es/.locale-peer-id: -------------------------------------------------------------------------------- 1 | 0b59cb46e5817b414866ebe33f4d7bcf 2 | -------------------------------------------------------------------------------- /locales/fr/.locale-peer-id: -------------------------------------------------------------------------------- 1 | 0b59cb46e5817b414866ebe33f4d7bcf 2 | -------------------------------------------------------------------------------- /locales/ja/.locale-peer-id: -------------------------------------------------------------------------------- 1 | 0b59cb46e5817b414866ebe33f4d7bcf 2 | -------------------------------------------------------------------------------- /locales/ja/テンプレート/Planguageを使用した意思決定記録テンプレート/README.md: -------------------------------------------------------------------------------- 1 | index.md -------------------------------------------------------------------------------- /locales/ja/テンプレート/madrプロジェクトの意思決定記録テンプレート/README.md: -------------------------------------------------------------------------------- 1 | index.md -------------------------------------------------------------------------------- /locales/ja/テンプレート/アレクサンドリアパターンの意思決定記録テンプレート/README.md: -------------------------------------------------------------------------------- 1 | index.md -------------------------------------------------------------------------------- /locales/ja/ドキュメント/how-to-start-using-adrs/README.md: -------------------------------------------------------------------------------- 1 | index.md -------------------------------------------------------------------------------- /locales/ja/ドキュメント/teamwork-advice-for-adrs/README.md: -------------------------------------------------------------------------------- 1 | index.md -------------------------------------------------------------------------------- /locales/ko/.locale-peer-id: -------------------------------------------------------------------------------- 1 | 0b59cb46e5817b414866ebe33f4d7bcf 2 | -------------------------------------------------------------------------------- /locales/ko/템플릿/의사 결정 기록 템플릿-by-michael-nygard/README.md: -------------------------------------------------------------------------------- 1 | index.md -------------------------------------------------------------------------------- /locales/zh/文档/how-to-start-using-adrs/README.md: -------------------------------------------------------------------------------- 1 | index.md 2 | -------------------------------------------------------------------------------- /locales/cy/nogfennau/sut-i-ddechrau-defnyddio-adrs/README.md: -------------------------------------------------------------------------------- 1 | index.md -------------------------------------------------------------------------------- /locales/en/documents/teamwork-questions-for-adrs/README.md: -------------------------------------------------------------------------------- 1 | index.md -------------------------------------------------------------------------------- /locales/en/examples/agile-software-development/README.md: -------------------------------------------------------------------------------- 1 | index.md -------------------------------------------------------------------------------- /locales/en/examples/choosing-a-database-technology/README.md: -------------------------------------------------------------------------------- 1 | index.md -------------------------------------------------------------------------------- /locales/en/examples/python-programming-language/README.md: -------------------------------------------------------------------------------- 1 | index.md -------------------------------------------------------------------------------- /locales/es/documentos/cómo-comenzar-a-usar-adrs/README.md: -------------------------------------------------------------------------------- 1 | index.md -------------------------------------------------------------------------------- /locales/ja/テンプレート/EdgeX Foundryによる意思決定記録テンプレート/README.md: -------------------------------------------------------------------------------- 1 | index.md -------------------------------------------------------------------------------- /locales/ja/テンプレート/Michael Nygard による意思決定記録テンプレート/README.md: -------------------------------------------------------------------------------- 1 | index.md -------------------------------------------------------------------------------- /locales/ja/ドキュメント/decision-sustainability-criteria/README.md: -------------------------------------------------------------------------------- 1 | index.md -------------------------------------------------------------------------------- /locales/ja/ドキュメント/file-name-conventions-for-adrs/README.md: -------------------------------------------------------------------------------- 1 | index.md -------------------------------------------------------------------------------- /locales/ja/ドキュメント/how-to-start-using-adrs-with-git/README.md: -------------------------------------------------------------------------------- 1 | index.md -------------------------------------------------------------------------------- /locales/ko/서류/.locale-peer-id: -------------------------------------------------------------------------------- 1 | abc7c72d426bc75e40b25a44ae37ce73 2 | -------------------------------------------------------------------------------- /locales/ko/템플릿/.locale-peer-id: -------------------------------------------------------------------------------- 1 | 70f1f9b3530831bc891a6e9b9b0d27de 2 | -------------------------------------------------------------------------------- /locales/cy/nogfennau/.locale-peer-id: -------------------------------------------------------------------------------- 1 | abc7c72d426bc75e40b25a44ae37ce73 2 | -------------------------------------------------------------------------------- /locales/cy/nogfennau/cyngor-gwaith-tîm-ar-gyfer-adrs/README.md: -------------------------------------------------------------------------------- 1 | index.md -------------------------------------------------------------------------------- /locales/cy/templedi/.locale-peer-id: -------------------------------------------------------------------------------- 1 | 70f1f9b3530831bc891a6e9b9b0d27de 2 | -------------------------------------------------------------------------------- /locales/en/documents/.locale-peer-id: -------------------------------------------------------------------------------- 1 | abc7c72d426bc75e40b25a44ae37ce73 2 | -------------------------------------------------------------------------------- /locales/en/documents/decision-sustainability-criteria/README.md: -------------------------------------------------------------------------------- 1 | index.md -------------------------------------------------------------------------------- /locales/en/documents/file-name-conventions-for-adrs/README.md: -------------------------------------------------------------------------------- 1 | index.md -------------------------------------------------------------------------------- /locales/en/documents/how-to-start-using-adrs-with-git/README.md: -------------------------------------------------------------------------------- 1 | index.md -------------------------------------------------------------------------------- /locales/en/documents/how-to-start-using-adrs-with-tools/README.md: -------------------------------------------------------------------------------- 1 | index.md -------------------------------------------------------------------------------- /locales/en/documents/suggestions-for-writing-good-adrs/README.md: -------------------------------------------------------------------------------- 1 | index.md -------------------------------------------------------------------------------- /locales/en/examples/environment-variable-configuration/README.md: -------------------------------------------------------------------------------- 1 | index.md -------------------------------------------------------------------------------- /locales/en/examples/kubernetes-container-orchestration/README.md: -------------------------------------------------------------------------------- 1 | index.md -------------------------------------------------------------------------------- /locales/en/examples/react-front-end-javascript-library/README.md: -------------------------------------------------------------------------------- 1 | index.md -------------------------------------------------------------------------------- /locales/en/examples/svelte-front-end-javascript-library/README.md: -------------------------------------------------------------------------------- 1 | index.md -------------------------------------------------------------------------------- /locales/en/examples/vue-front-end-javascript-library/README.md: -------------------------------------------------------------------------------- 1 | index.md -------------------------------------------------------------------------------- /locales/en/templates/.locale-peer-id: -------------------------------------------------------------------------------- 1 | 70f1f9b3530831bc891a6e9b9b0d27de 2 | -------------------------------------------------------------------------------- /locales/en/templates/decision-record-template-by-arc42/README.md: -------------------------------------------------------------------------------- 1 | index.md -------------------------------------------------------------------------------- /locales/en/templates/decision-record-template-by-edgex/README.md: -------------------------------------------------------------------------------- 1 | index.md -------------------------------------------------------------------------------- /locales/es/documentos/convenciones-de-nombre-de-archivo/README.md: -------------------------------------------------------------------------------- 1 | index.md -------------------------------------------------------------------------------- /locales/es/documentos/cómo-comenzar-a-usar-adr-con-git/README.md: -------------------------------------------------------------------------------- 1 | index.md -------------------------------------------------------------------------------- /locales/fr/documents/.locale-peer-id: -------------------------------------------------------------------------------- 1 | abc7c72d426bc75e40b25a44ae37ce73 2 | -------------------------------------------------------------------------------- /locales/fr/documents/conventions-de-noms-de-fichiers/README.md: -------------------------------------------------------------------------------- 1 | index.md -------------------------------------------------------------------------------- /locales/fr/documents/critères-de-durabilité-de-décision/README.md: -------------------------------------------------------------------------------- 1 | index.md -------------------------------------------------------------------------------- /locales/fr/modèles/.locale-peer-id: -------------------------------------------------------------------------------- 1 | 70f1f9b3530831bc891a6e9b9b0d27de 2 | -------------------------------------------------------------------------------- /locales/ja/テンプレート/.locale-peer-id: -------------------------------------------------------------------------------- 1 | 70f1f9b3530831bc891a6e9b9b0d27de 2 | -------------------------------------------------------------------------------- /locales/ja/テンプレート/Jeff TyreeとArt Akermanによる意思決定記録テンプレート/README.md: -------------------------------------------------------------------------------- 1 | index.md -------------------------------------------------------------------------------- /locales/ja/ドキュメント/.locale-peer-id: -------------------------------------------------------------------------------- 1 | abc7c72d426bc75e40b25a44ae37ce73 2 | -------------------------------------------------------------------------------- /locales/ja/ドキュメント/how-to-start-using-adrs-with-tools/README.md: -------------------------------------------------------------------------------- 1 | index.md -------------------------------------------------------------------------------- /locales/ja/ドキュメント/suggestions-for-writing-good-adrs/README.md: -------------------------------------------------------------------------------- 1 | index.md -------------------------------------------------------------------------------- /locales/zh/文档/how-to-start-using-adrs-with-tools/README.md: -------------------------------------------------------------------------------- 1 | index.md 2 | -------------------------------------------------------------------------------- /locales/cy/nogfennau/awgrymiadau-ar-gyfer-ysgrifennu-adrs-da/README.md: -------------------------------------------------------------------------------- 1 | index.md -------------------------------------------------------------------------------- /locales/cy/nogfennau/cwestiynau-gwaith-tîm-ar-gyfer-adrau/README.md: -------------------------------------------------------------------------------- 1 | index.md -------------------------------------------------------------------------------- /locales/cy/nogfennau/meini-prawf-cynaliadwyedd-penderfynu/README.md: -------------------------------------------------------------------------------- 1 | index.md -------------------------------------------------------------------------------- /locales/cy/nogfennau/sut-i-ddechrau-defnyddio-adrs-gyda-git/README.md: -------------------------------------------------------------------------------- 1 | index.md -------------------------------------------------------------------------------- /locales/cy/templedi/templed-cofnod-penderfyniad-gan-edgex/README.md: -------------------------------------------------------------------------------- 1 | index.md -------------------------------------------------------------------------------- /locales/en/documents/what-is-an-architecture-decision-record/README.md: -------------------------------------------------------------------------------- 1 | index.md -------------------------------------------------------------------------------- /locales/en/examples/authentication-authorization-options/README.md: -------------------------------------------------------------------------------- 1 | index.md -------------------------------------------------------------------------------- /locales/en/examples/docker-swarm-container-orchestration/README.md: -------------------------------------------------------------------------------- 1 | index.md -------------------------------------------------------------------------------- /locales/en/examples/microsoft-azure-cloud-infrastructure/README.md: -------------------------------------------------------------------------------- 1 | index.md -------------------------------------------------------------------------------- /locales/en/examples/snake-case-v-camelcase-for-a-rest-api/README.md: -------------------------------------------------------------------------------- 1 | index.md -------------------------------------------------------------------------------- /locales/es/documentos/.locale-peer-id: -------------------------------------------------------------------------------- 1 | abc7c72d426bc75e40b25a44ae37ce73 2 | -------------------------------------------------------------------------------- /locales/es/documentos/consejo-de-trabajo-en-equipo-para-adrs/README.md: -------------------------------------------------------------------------------- 1 | index.md -------------------------------------------------------------------------------- /locales/es/documentos/sugerencias-para-escribir-buenos-adr/README.md: -------------------------------------------------------------------------------- 1 | index.md -------------------------------------------------------------------------------- /locales/es/plantillas/.locale-peer-id: -------------------------------------------------------------------------------- 1 | 70f1f9b3530831bc891a6e9b9b0d27de 2 | -------------------------------------------------------------------------------- /locales/fr/documents/comment-commencer-à-utiliser-les-adr/README.md: -------------------------------------------------------------------------------- 1 | index.md -------------------------------------------------------------------------------- /locales/fr/documents/suggestions-pour-écrire-de-bonnes-adr/README.md: -------------------------------------------------------------------------------- 1 | index.md -------------------------------------------------------------------------------- /locales/ja/ドキュメント/what-is-an-architecture-decision-record/README.md: -------------------------------------------------------------------------------- 1 | index.md -------------------------------------------------------------------------------- /locales/ko/서류/파일-이름-규칙/.locale-peer-id: -------------------------------------------------------------------------------- 1 | 89116b5647aa1e53186f3c44b5a284a0 2 | -------------------------------------------------------------------------------- /locales/ko/템플릿/의사결정 기록 템플릿-by-jeff-tyree-and-art-akerman/README.md: -------------------------------------------------------------------------------- 1 | index.md -------------------------------------------------------------------------------- /locales/zh/文档/what-is-an-architecture-decision-record /README.md: -------------------------------------------------------------------------------- 1 | index.md 2 | -------------------------------------------------------------------------------- /locales/cy/nogfennau/beth-yw-cofnod-penderfyniad-pensaernïaeth/README.md: -------------------------------------------------------------------------------- 1 | index.md -------------------------------------------------------------------------------- /locales/cy/nogfennau/proses-cofnodion-penderfynol-pensaernïol-aws/README.md: -------------------------------------------------------------------------------- 1 | index.md -------------------------------------------------------------------------------- /locales/cy/nogfennau/sut-i-ddechrau-defnyddio-adrs-gydag-offer/README.md: -------------------------------------------------------------------------------- 1 | index.md -------------------------------------------------------------------------------- /locales/cy/templedi/templed-cofnod-penderfyniad-gan-planguage/README.md: -------------------------------------------------------------------------------- 1 | index.md -------------------------------------------------------------------------------- /locales/cy/templedi/templed-cofnod-penderfyniad-y-prosiect-madr/README.md: -------------------------------------------------------------------------------- 1 | index.md -------------------------------------------------------------------------------- /locales/en/documents/guidelines-to-achieve-sustainable-decisions/README.md: -------------------------------------------------------------------------------- 1 | index.md -------------------------------------------------------------------------------- /locales/en/templates/decision-record-template-by-gareth-morgan/README.md: -------------------------------------------------------------------------------- 1 | index.md -------------------------------------------------------------------------------- /locales/en/templates/decision-record-template-by-michael-nygard/README.md: -------------------------------------------------------------------------------- 1 | index.md -------------------------------------------------------------------------------- /locales/en/templates/decision-record-template-for-business-case/README.md: -------------------------------------------------------------------------------- 1 | index.md -------------------------------------------------------------------------------- /locales/en/templates/decision-record-template-of-the-madr-project/README.md: -------------------------------------------------------------------------------- 1 | index.md -------------------------------------------------------------------------------- /locales/en/templates/decision-record-template-using-planguage/README.md: -------------------------------------------------------------------------------- 1 | index.md -------------------------------------------------------------------------------- /locales/es/documentos/criterios-de-sostenibilidad-de-decisión/README.md: -------------------------------------------------------------------------------- 1 | index.md -------------------------------------------------------------------------------- /locales/es/documentos/cómo-comenzar-a-usar-adr-con-herramientas/README.md: -------------------------------------------------------------------------------- 1 | index.md -------------------------------------------------------------------------------- /locales/es/plantillas/plantilla-de-registro-de-decisión-de-edgex/README.md: -------------------------------------------------------------------------------- 1 | index.md -------------------------------------------------------------------------------- /locales/fr/documents/conseils-de-travail-déquipe-pour-les-adr/README.md: -------------------------------------------------------------------------------- 1 | index.md -------------------------------------------------------------------------------- /locales/fr/modèles/modèle-denregistrement-de-décision-par-edgex/README.md: -------------------------------------------------------------------------------- 1 | index.md -------------------------------------------------------------------------------- /locales/ja/ドキュメント/guidelines-to-achieve-sustainable-decisions/README.md: -------------------------------------------------------------------------------- 1 | index.md -------------------------------------------------------------------------------- /locales/ko/서류/adr-사용을-시작하는-방법/.locale-peer-id: -------------------------------------------------------------------------------- 1 | 8196518140224596af99a46d512feba3 2 | -------------------------------------------------------------------------------- /locales/ko/서류/adr을-위한-팀워크-조언/.locale-peer-id: -------------------------------------------------------------------------------- 1 | 875a7715e592ceb45eac5e155ee16318 2 | -------------------------------------------------------------------------------- /locales/ko/서류/의사결정-지속가능성-기준/.locale-peer-id: -------------------------------------------------------------------------------- 1 | 71d59ed566ae148b8bf42331a84754ac 2 | -------------------------------------------------------------------------------- /locales/ko/서류/좋은-adr-작성을-위한-제안/.locale-peer-id: -------------------------------------------------------------------------------- 1 | dc1a294e76821d6d3b086a2b17988427 2 | -------------------------------------------------------------------------------- /locales/cy/nogfennau/canllawiau-i-gyflawni-penderfyniadau-cynaliadwy/README.md: -------------------------------------------------------------------------------- 1 | index.md -------------------------------------------------------------------------------- /locales/cy/templedi/templed-cofnod-penderfyniad-ar-gyfer-achos-busnes/README.md: -------------------------------------------------------------------------------- 1 | index.md -------------------------------------------------------------------------------- /locales/cy/templedi/templed-cofnod-penderfyniad-gan-michael-nygard/README.md: -------------------------------------------------------------------------------- 1 | index.md -------------------------------------------------------------------------------- /locales/en/examples/4-day-work-week/.locale-peer-id: -------------------------------------------------------------------------------- 1 | fb15d0e84550135e2e7a280693ba5848 2 | -------------------------------------------------------------------------------- /locales/en/examples/css-framework/.locale-peer-id: -------------------------------------------------------------------------------- 1 | 694d2d4235299f058990c1cc470af15e 2 | -------------------------------------------------------------------------------- /locales/en/examples/mysql-database/.locale-peer-id: -------------------------------------------------------------------------------- 1 | 4f4246ee263e7d47d7533ed048c2c7ef 2 | -------------------------------------------------------------------------------- /locales/en/examples/secrets-storage/.locale-peer-id: -------------------------------------------------------------------------------- 1 | 8123c8089cda027baecab9c034e947c6 2 | -------------------------------------------------------------------------------- /locales/en/examples/tailwind-css/.locale-peer-id: -------------------------------------------------------------------------------- 1 | 496e7846025a0701822dc65ca71180a5 2 | -------------------------------------------------------------------------------- /locales/en/examples/work-from-home/.locale-peer-id: -------------------------------------------------------------------------------- 1 | 0a53cbdf9f479da77ad7e0a6128275a9 2 | -------------------------------------------------------------------------------- /locales/en/templates/decision-record-template-by-gig-cymru-nhs-wales/README.md: -------------------------------------------------------------------------------- 1 | index.md -------------------------------------------------------------------------------- /locales/en/templates/decision-record-template-for-alexandrian-pattern/README.md: -------------------------------------------------------------------------------- 1 | index.md -------------------------------------------------------------------------------- /locales/es/documentos/directrices-para-lograr-decisiones-sostenibles/README.md: -------------------------------------------------------------------------------- 1 | index.md -------------------------------------------------------------------------------- /locales/es/documentos/qué-es-un-registro-de-decisión-de-arquitectura/README.md: -------------------------------------------------------------------------------- 1 | index.md -------------------------------------------------------------------------------- /locales/fr/documents/comment-commencer-à-utiliser-les-adr-avec-git/README.md: -------------------------------------------------------------------------------- 1 | index.md -------------------------------------------------------------------------------- /locales/fr/documents/quest-ce-quun-dossier-de-décision-darchitecture/README.md: -------------------------------------------------------------------------------- 1 | index.md -------------------------------------------------------------------------------- /locales/fr/modèles/modèle-denregistrement-de-décision-du-projet-madr/README.md: -------------------------------------------------------------------------------- 1 | index.md -------------------------------------------------------------------------------- /locales/ja/ドキュメント/aws-adr-process/.locale-peer-id: -------------------------------------------------------------------------------- 1 | 7d4adf16004ca42546dee49922ae4ccf 2 | -------------------------------------------------------------------------------- /locales/ko/서류/aws-아키텍처-결정-기록-프로세스/.locale-peer-id: -------------------------------------------------------------------------------- 1 | 7d4adf16004ca42546dee49922ae4ccf 2 | -------------------------------------------------------------------------------- /locales/ko/서류/git에서-adr-사용을-시작하는-방법/.locale-peer-id: -------------------------------------------------------------------------------- 1 | d6fb3c7d91f95003163e694e74058e9d 2 | -------------------------------------------------------------------------------- /locales/ko/서류/아키텍처-결정-기록이란-무엇입니까/.locale-peer-id: -------------------------------------------------------------------------------- 1 | 020ff535ed1a3347a265209291e756b6 2 | -------------------------------------------------------------------------------- /locales/ko/서류/지속-가능한-결정을-달성하기-위한-지침/.locale-peer-id: -------------------------------------------------------------------------------- 1 | 934d1c42a693fe004cd8bf8f5ecb97e6 2 | -------------------------------------------------------------------------------- /locales/ko/템플릿/madr 프로젝트의 결정 기록 템플릿/.locale-peer-id: -------------------------------------------------------------------------------- 1 | 0a9f88e5cda952db0a82d071f585d090 2 | -------------------------------------------------------------------------------- /locales/ko/템플릿/결정 기록 템플릿별 edgex/.locale-peer-id: -------------------------------------------------------------------------------- 1 | 01939db0c341e9092c344d904065da12 2 | -------------------------------------------------------------------------------- /locales/ko/템플릿/의사결정 기록 템플릿 사용 p언어/.locale-peer-id: -------------------------------------------------------------------------------- 1 | bb37e19df57d398b0704d6bd30ee6e6d 2 | -------------------------------------------------------------------------------- /locales/en/documents/aws-adr-process/.locale-peer-id: -------------------------------------------------------------------------------- 1 | 7d4adf16004ca42546dee49922ae4ccf 2 | -------------------------------------------------------------------------------- /locales/en/examples/amazon-web-services/.locale-peer-id: -------------------------------------------------------------------------------- 1 | c4beaa505311198b2b00341fe42c948f 2 | -------------------------------------------------------------------------------- /locales/en/examples/high-trust-teamwork/.locale-peer-id: -------------------------------------------------------------------------------- 1 | 912115918de8642859827f500f4aca23 2 | -------------------------------------------------------------------------------- /locales/en/examples/postgresql-database/.locale-peer-id: -------------------------------------------------------------------------------- 1 | 4ea514a9c996ef7af8eca37ec2b96d69 2 | -------------------------------------------------------------------------------- /locales/en/examples/sveltekit-framework/.locale-peer-id: -------------------------------------------------------------------------------- 1 | 0bc6820a0b59edb03d91948dcfcd6cd0 2 | -------------------------------------------------------------------------------- /locales/en/examples/timestamp-format/.locale-peer-id: -------------------------------------------------------------------------------- 1 | 9374af360cb954bffd75c8518a93b25d 2 | -------------------------------------------------------------------------------- /locales/en/templates/decision-record-template-by-jeff-tyree-and-art-akerman/README.md: -------------------------------------------------------------------------------- 1 | index.md -------------------------------------------------------------------------------- /locales/es/plantillas/plantilla-de-registro-de-decisión-de-michael-nygard/README.md: -------------------------------------------------------------------------------- 1 | index.md -------------------------------------------------------------------------------- /locales/es/plantillas/plantilla-de-registro-de-decisión-del-proyecto-madr/README.md: -------------------------------------------------------------------------------- 1 | index.md -------------------------------------------------------------------------------- /locales/es/plantillas/plantilla-de-registro-de-decisión-usando-planguage/README.md: -------------------------------------------------------------------------------- 1 | index.md -------------------------------------------------------------------------------- /locales/fr/documents/comment-commencer-à-utiliser-les-adr-avec-des-outils/README.md: -------------------------------------------------------------------------------- 1 | index.md -------------------------------------------------------------------------------- /locales/fr/documents/processus-des-dossiers-de-décision-architecturale-aws/README.md: -------------------------------------------------------------------------------- 1 | index.md -------------------------------------------------------------------------------- /locales/fr/modèles/modèle-denregistrement-de-décision utilisant-plangage/README.md: -------------------------------------------------------------------------------- 1 | index.md -------------------------------------------------------------------------------- /locales/fr/modèles/modèle-denregistrement-de-décision-par michael-nygard/README.md: -------------------------------------------------------------------------------- 1 | index.md -------------------------------------------------------------------------------- /locales/ja/テンプレート/ビジネスケース用意思決定記録テンプレート/.locale-peer-id: -------------------------------------------------------------------------------- 1 | f6d1fb662640a00f4c66c586233dead9 2 | -------------------------------------------------------------------------------- /locales/ko/서류/도구를-사용하여-adr-사용을-시작하는-방법/.locale-peer-id: -------------------------------------------------------------------------------- 1 | 1a5a03dd6f20cea9f78fb4655a9a7f87 2 | -------------------------------------------------------------------------------- /locales/ko/템플릿/비즈니스 사례에 대한 의사결정 기록 템플릿/.locale-peer-id: -------------------------------------------------------------------------------- 1 | f6d1fb662640a00f4c66c586233dead9 2 | -------------------------------------------------------------------------------- /locales/ko/템플릿/알렉산드리아 패턴에 대한 결정 기록 템플릿/.locale-peer-id: -------------------------------------------------------------------------------- 1 | f33e4eb0409f956de201b791749dc9aa 2 | -------------------------------------------------------------------------------- /locales/cy/nogfennau/confensiynau-enw-ffeil/.locale-peer-id: -------------------------------------------------------------------------------- 1 | 89116b5647aa1e53186f3c44b5a284a0 2 | -------------------------------------------------------------------------------- /locales/cy/templedi/templed-cofnod-penderfyniad-ar-gyfer-patrwm-alecsandraidd/README.md: -------------------------------------------------------------------------------- 1 | index.md -------------------------------------------------------------------------------- /locales/cy/templedi/templed-cofnod-penderfyniad-gan-jeff-tyree-and-art-akerman/README.md: -------------------------------------------------------------------------------- 1 | index.md -------------------------------------------------------------------------------- /locales/en/documents/how-to-start-using-adrs/.locale-peer-id: -------------------------------------------------------------------------------- 1 | 8196518140224596af99a46d512feba3 2 | -------------------------------------------------------------------------------- /locales/en/documents/teamwork-advice-for-adrs/.locale-peer-id: -------------------------------------------------------------------------------- 1 | 875a7715e592ceb45eac5e155ee16318 2 | -------------------------------------------------------------------------------- /locales/en/examples/api-using-json-v-grpc/.locale-peer-id: -------------------------------------------------------------------------------- 1 | 7c91a4cc326aecb7f1a62a6d41b8b4fd 2 | -------------------------------------------------------------------------------- /locales/en/examples/continuous-integration/.locale-peer-id: -------------------------------------------------------------------------------- 1 | 45cdbd2e37d773b7e0592a142fd5de30 2 | -------------------------------------------------------------------------------- /locales/en/examples/go-programming-language/.locale-peer-id: -------------------------------------------------------------------------------- 1 | 77c69ad4fd10a2dc47f3f7a6dcbbef68 2 | -------------------------------------------------------------------------------- /locales/en/examples/google-cloud-platform/.locale-peer-id: -------------------------------------------------------------------------------- 1 | 819cd06503cb318caf8f90fcff244b84 2 | -------------------------------------------------------------------------------- /locales/en/examples/java-programming-language/.locale-peer-id: -------------------------------------------------------------------------------- 1 | 984e1e50927d81ec862d5899cd3cb077 2 | -------------------------------------------------------------------------------- /locales/en/examples/metrics-monitors-alerts/.locale-peer-id: -------------------------------------------------------------------------------- 1 | d97e71af7770a8cfefb718b2ffd28062 2 | -------------------------------------------------------------------------------- /locales/en/examples/microsoft-azure-devops/.locale-peer-id: -------------------------------------------------------------------------------- 1 | e1e84e31e7b1463322b083fd2983fe1a 2 | -------------------------------------------------------------------------------- /locales/en/examples/monorepo-vs-multirepo/.locale-peer-id: -------------------------------------------------------------------------------- 1 | b52cc745a00570dede6cd309dd35d7ac 2 | -------------------------------------------------------------------------------- /locales/en/examples/programming-code-editors/.locale-peer-id: -------------------------------------------------------------------------------- 1 | 8aec4ce83bd164e7b2945f37c052a6d1 2 | -------------------------------------------------------------------------------- /locales/en/examples/programming-languages/.locale-peer-id: -------------------------------------------------------------------------------- 1 | 1984c4f82b0b1364c6a3fae147697337 2 | -------------------------------------------------------------------------------- /locales/en/examples/python-django-framework/.locale-peer-id: -------------------------------------------------------------------------------- 1 | b8f60539494aed8b17e1b8969ae2f10b 2 | -------------------------------------------------------------------------------- /locales/en/examples/ruby-on-rails-framework/.locale-peer-id: -------------------------------------------------------------------------------- 1 | b107a749a966e10cc337420370e34063 2 | -------------------------------------------------------------------------------- /locales/en/examples/rust-programming-language/.locale-peer-id: -------------------------------------------------------------------------------- 1 | d21b58847a2e92716ef2f68b44156564 2 | -------------------------------------------------------------------------------- /locales/es/documentos/proceso-de-registros-de-decisiones-arquitectónicas-de-aws/README.md: -------------------------------------------------------------------------------- 1 | index.md -------------------------------------------------------------------------------- /locales/es/plantillas/plantilla-de-registro-de-decisión-para-caso-de-negocio/README.md: -------------------------------------------------------------------------------- 1 | index.md -------------------------------------------------------------------------------- /locales/fr/documents/lignes-directrices-pour-atteindre-des-décisions-durables/README.md: -------------------------------------------------------------------------------- 1 | index.md -------------------------------------------------------------------------------- /locales/fr/modèles/modèle-denregistrement-de-décision-pour-le modèle-alexandrin/README.md: -------------------------------------------------------------------------------- 1 | index.md -------------------------------------------------------------------------------- /locales/ja/テンプレート/Planguageを使用した意思決定記録テンプレート/.locale-peer-id: -------------------------------------------------------------------------------- 1 | bb37e19df57d398b0704d6bd30ee6e6d 2 | -------------------------------------------------------------------------------- /locales/ja/テンプレート/madrプロジェクトの意思決定記録テンプレート/.locale-peer-id: -------------------------------------------------------------------------------- 1 | 0a9f88e5cda952db0a82d071f585d090 2 | -------------------------------------------------------------------------------- /locales/ja/テンプレート/アレクサンドリアパターンの意思決定記録テンプレート/.locale-peer-id: -------------------------------------------------------------------------------- 1 | f33e4eb0409f956de201b791749dc9aa 2 | -------------------------------------------------------------------------------- /locales/ja/ドキュメント/how-to-start-using-adrs/.locale-peer-id: -------------------------------------------------------------------------------- 1 | 8196518140224596af99a46d512feba3 2 | -------------------------------------------------------------------------------- /locales/ja/ドキュメント/teamwork-advice-for-adrs/.locale-peer-id: -------------------------------------------------------------------------------- 1 | 875a7715e592ceb45eac5e155ee16318 2 | -------------------------------------------------------------------------------- /locales/ko/템플릿/의사 결정 기록 템플릿-by-michael-nygard/.locale-peer-id: -------------------------------------------------------------------------------- 1 | b1e90e6556c1c8f1e2eb3ac22c8c5077 2 | -------------------------------------------------------------------------------- /locales/cy/nogfennau/sut-i-ddechrau-defnyddio-adrs/.locale-peer-id: -------------------------------------------------------------------------------- 1 | 8196518140224596af99a46d512feba3 2 | -------------------------------------------------------------------------------- /locales/en/documents/teamwork-questions-for-adrs/.locale-peer-id: -------------------------------------------------------------------------------- 1 | 60057747e4547af35fd888021e41f332 2 | -------------------------------------------------------------------------------- /locales/en/examples/agile-software-development/.locale-peer-id: -------------------------------------------------------------------------------- 1 | a4bc089ce8e95a6dce0fb0845081674a 2 | -------------------------------------------------------------------------------- /locales/en/examples/choosing-a-database-technology/.locale-peer-id: -------------------------------------------------------------------------------- 1 | ee24129d8750e5ceebb9b4ff7b3cfb1a 2 | -------------------------------------------------------------------------------- /locales/en/examples/python-programming-language/.locale-peer-id: -------------------------------------------------------------------------------- 1 | 42fd8a00f5f37e2f2a9c4a3f2fd61356 2 | -------------------------------------------------------------------------------- /locales/es/documentos/cómo-comenzar-a-usar-adrs/.locale-peer-id: -------------------------------------------------------------------------------- 1 | 8196518140224596af99a46d512feba3 2 | -------------------------------------------------------------------------------- /locales/es/plantillas/plantilla-de-registro-de-decisión-de-jeff-tyree-y-art-akerman/README.md: -------------------------------------------------------------------------------- 1 | index.md -------------------------------------------------------------------------------- /locales/es/plantillas/plantilla-de-registro-de-decisión-para-el-patrón-alejandrino/README.md: -------------------------------------------------------------------------------- 1 | index.md -------------------------------------------------------------------------------- /locales/fr/modèles/modèle-denregistrement-de-décision par jeff-tyree-et-art-akerman/README.md: -------------------------------------------------------------------------------- 1 | index.md -------------------------------------------------------------------------------- /locales/ja/テンプレート/EdgeX Foundryによる意思決定記録テンプレート/.locale-peer-id: -------------------------------------------------------------------------------- 1 | 01939db0c341e9092c344d904065da12 2 | -------------------------------------------------------------------------------- /locales/ja/テンプレート/Michael Nygard による意思決定記録テンプレート/.locale-peer-id: -------------------------------------------------------------------------------- 1 | b1e90e6556c1c8f1e2eb3ac22c8c5077 2 | -------------------------------------------------------------------------------- /locales/ja/ドキュメント/decision-sustainability-criteria/.locale-peer-id: -------------------------------------------------------------------------------- 1 | 71d59ed566ae148b8bf42331a84754ac 2 | -------------------------------------------------------------------------------- /locales/ja/ドキュメント/file-name-conventions-for-adrs/.locale-peer-id: -------------------------------------------------------------------------------- 1 | 89116b5647aa1e53186f3c44b5a284a0 2 | -------------------------------------------------------------------------------- /locales/ja/ドキュメント/how-to-start-using-adrs-with-git/.locale-peer-id: -------------------------------------------------------------------------------- 1 | d6fb3c7d91f95003163e694e74058e9d 2 | -------------------------------------------------------------------------------- /locales/cy/nogfennau/cyngor-gwaith-tîm-ar-gyfer-adrs/.locale-peer-id: -------------------------------------------------------------------------------- 1 | 875a7715e592ceb45eac5e155ee16318 2 | -------------------------------------------------------------------------------- /locales/en/documents/decision-sustainability-criteria/.locale-peer-id: -------------------------------------------------------------------------------- 1 | 71d59ed566ae148b8bf42331a84754ac 2 | -------------------------------------------------------------------------------- /locales/en/documents/file-name-conventions-for-adrs/.locale-peer-id: -------------------------------------------------------------------------------- 1 | 89116b5647aa1e53186f3c44b5a284a0 2 | -------------------------------------------------------------------------------- /locales/en/documents/how-to-start-using-adrs-with-git/.locale-peer-id: -------------------------------------------------------------------------------- 1 | d6fb3c7d91f95003163e694e74058e9d 2 | -------------------------------------------------------------------------------- /locales/en/documents/how-to-start-using-adrs-with-tools/.locale-peer-id: -------------------------------------------------------------------------------- 1 | 1a5a03dd6f20cea9f78fb4655a9a7f87 2 | -------------------------------------------------------------------------------- /locales/en/documents/suggestions-for-writing-good-adrs/.locale-peer-id: -------------------------------------------------------------------------------- 1 | dc1a294e76821d6d3b086a2b17988427 2 | -------------------------------------------------------------------------------- /locales/en/examples/browser-automation-framework-for-e2e-testing-playwright-vs-selenium/README.md: -------------------------------------------------------------------------------- 1 | index.md -------------------------------------------------------------------------------- /locales/en/examples/chart-library-toolkit-for-data-visualization-using-typescript-and-json/README.md: -------------------------------------------------------------------------------- 1 | index.md -------------------------------------------------------------------------------- /locales/en/examples/environment-variable-configuration/.locale-peer-id: -------------------------------------------------------------------------------- 1 | 46b0910941ab1812cda52b34baca5798 2 | -------------------------------------------------------------------------------- /locales/en/examples/kubernetes-container-orchestration/.locale-peer-id: -------------------------------------------------------------------------------- 1 | cb3edecf9181c9c28bbbbc5d323ec733 2 | -------------------------------------------------------------------------------- /locales/en/examples/react-front-end-javascript-library/.locale-peer-id: -------------------------------------------------------------------------------- 1 | 9eadfd943b9e3d2404a28e8ad14d3076 2 | -------------------------------------------------------------------------------- /locales/en/examples/svelte-front-end-javascript-library/.locale-peer-id: -------------------------------------------------------------------------------- 1 | bdca98499db7dd51eeb5add1ca5ec974 2 | -------------------------------------------------------------------------------- /locales/en/examples/vue-front-end-javascript-library/.locale-peer-id: -------------------------------------------------------------------------------- 1 | b43f7e984abc2ba89f2738c3e63203aa 2 | -------------------------------------------------------------------------------- /locales/en/templates/decision-record-template-by-edgex/.locale-peer-id: -------------------------------------------------------------------------------- 1 | 01939db0c341e9092c344d904065da12 2 | -------------------------------------------------------------------------------- /locales/es/documentos/convenciones-de-nombre-de-archivo/.locale-peer-id: -------------------------------------------------------------------------------- 1 | 89116b5647aa1e53186f3c44b5a284a0 2 | -------------------------------------------------------------------------------- /locales/es/documentos/cómo-comenzar-a-usar-adr-con-git/.locale-peer-id: -------------------------------------------------------------------------------- 1 | d6fb3c7d91f95003163e694e74058e9d 2 | -------------------------------------------------------------------------------- /locales/fr/documents/conventions-de-noms-de-fichiers/.locale-peer-id: -------------------------------------------------------------------------------- 1 | 89116b5647aa1e53186f3c44b5a284a0 2 | -------------------------------------------------------------------------------- /locales/fr/documents/critères-de-durabilité-de-décision/.locale-peer-id: -------------------------------------------------------------------------------- 1 | 71d59ed566ae148b8bf42331a84754ac 2 | -------------------------------------------------------------------------------- /locales/fr/modèles/modèle-denregistrement-de-décision pour-lanalyse-de-rentabilisation/README.md: -------------------------------------------------------------------------------- 1 | index.md -------------------------------------------------------------------------------- /locales/ja/テンプレート/Jeff TyreeとArt Akermanによる意思決定記録テンプレート/.locale-peer-id: -------------------------------------------------------------------------------- 1 | f4ca0a94124a91279e1929ea23ab864d 2 | -------------------------------------------------------------------------------- /locales/ja/ドキュメント/how-to-start-using-adrs-with-tools/.locale-peer-id: -------------------------------------------------------------------------------- 1 | 1a5a03dd6f20cea9f78fb4655a9a7f87 2 | -------------------------------------------------------------------------------- /locales/ja/ドキュメント/suggestions-for-writing-good-adrs/.locale-peer-id: -------------------------------------------------------------------------------- 1 | dc1a294e76821d6d3b086a2b17988427 2 | -------------------------------------------------------------------------------- /LICENSE.md: -------------------------------------------------------------------------------- 1 | # License 2 | 3 | CC BY-NC-SA 4 | 5 | https://creativecommons.org/licenses/by-nc-sa/4.0/ 6 | 7 | -------------------------------------------------------------------------------- /locales/cy/nogfennau/awgrymiadau-ar-gyfer-ysgrifennu-adrs-da/.locale-peer-id: -------------------------------------------------------------------------------- 1 | dc1a294e76821d6d3b086a2b17988427 2 | -------------------------------------------------------------------------------- /locales/cy/nogfennau/cwestiynau-gwaith-tîm-ar-gyfer-adrau/.locale-peer-id: -------------------------------------------------------------------------------- 1 | 60057747e4547af35fd888021e41f332 2 | -------------------------------------------------------------------------------- /locales/cy/nogfennau/meini-prawf-cynaliadwyedd-penderfynu/.locale-peer-id: -------------------------------------------------------------------------------- 1 | 71d59ed566ae148b8bf42331a84754ac 2 | -------------------------------------------------------------------------------- /locales/cy/nogfennau/sut-i-ddechrau-defnyddio-adrs-gyda-git/.locale-peer-id: -------------------------------------------------------------------------------- 1 | d6fb3c7d91f95003163e694e74058e9d 2 | -------------------------------------------------------------------------------- /locales/cy/templedi/templed-cofnod-penderfyniad-gan-edgex/.locale-peer-id: -------------------------------------------------------------------------------- 1 | 01939db0c341e9092c344d904065da12 2 | -------------------------------------------------------------------------------- /locales/en/documents/what-is-an-architecture-decision-record/.locale-peer-id: -------------------------------------------------------------------------------- 1 | 020ff535ed1a3347a265209291e756b6 2 | -------------------------------------------------------------------------------- /locales/en/examples/docker-swarm-container-orchestration/.locale-peer-id: -------------------------------------------------------------------------------- 1 | 3d27355877340537b28efb2bae3a6907 2 | -------------------------------------------------------------------------------- /locales/en/examples/microsoft-azure-cloud-infrastructure/.locale-peer-id: -------------------------------------------------------------------------------- 1 | 4dce71df0db78d050f86e1a2cc4cb9d1 2 | -------------------------------------------------------------------------------- /locales/en/examples/snake-case-v-camelcase-for-a-rest-api/.locale-peer-id: -------------------------------------------------------------------------------- 1 | 56bcc02899f133bd74208e58e020ad3a 2 | -------------------------------------------------------------------------------- /locales/es/documentos/consejo-de-trabajo-en-equipo-para-adrs/.locale-peer-id: -------------------------------------------------------------------------------- 1 | 875a7715e592ceb45eac5e155ee16318 2 | -------------------------------------------------------------------------------- /locales/es/documentos/sugerencias-para-escribir-buenos-adr/.locale-peer-id: -------------------------------------------------------------------------------- 1 | dc1a294e76821d6d3b086a2b17988427 2 | -------------------------------------------------------------------------------- /locales/fr/documents/comment-commencer-à-utiliser-les-adr/.locale-peer-id: -------------------------------------------------------------------------------- 1 | 8196518140224596af99a46d512feba3 2 | -------------------------------------------------------------------------------- /locales/fr/documents/suggestions-pour-écrire-de-bonnes-adr/.locale-peer-id: -------------------------------------------------------------------------------- 1 | dc1a294e76821d6d3b086a2b17988427 2 | -------------------------------------------------------------------------------- /locales/ja/ドキュメント/what-is-an-architecture-decision-record/.locale-peer-id: -------------------------------------------------------------------------------- 1 | 020ff535ed1a3347a265209291e756b6 2 | -------------------------------------------------------------------------------- /locales/ko/템플릿/의사결정 기록 템플릿-by-jeff-tyree-and-art-akerman/.locale-peer-id: -------------------------------------------------------------------------------- 1 | f4ca0a94124a91279e1929ea23ab864d 2 | -------------------------------------------------------------------------------- /locales/cy/nogfennau/beth-yw-cofnod-penderfyniad-pensaernïaeth/.locale-peer-id: -------------------------------------------------------------------------------- 1 | 020ff535ed1a3347a265209291e756b6 2 | -------------------------------------------------------------------------------- /locales/cy/nogfennau/proses-cofnodion-penderfynol-pensaernïol-aws/.locale-peer-id: -------------------------------------------------------------------------------- 1 | 7d4adf16004ca42546dee49922ae4ccf 2 | -------------------------------------------------------------------------------- /locales/cy/nogfennau/sut-i-ddechrau-defnyddio-adrs-gydag-offer/.locale-peer-id: -------------------------------------------------------------------------------- 1 | 1a5a03dd6f20cea9f78fb4655a9a7f87 2 | -------------------------------------------------------------------------------- /locales/cy/templedi/templed-cofnod-penderfyniad-gan-planguage/.locale-peer-id: -------------------------------------------------------------------------------- 1 | bb37e19df57d398b0704d6bd30ee6e6d 2 | -------------------------------------------------------------------------------- /locales/cy/templedi/templed-cofnod-penderfyniad-y-prosiect-madr/.locale-peer-id: -------------------------------------------------------------------------------- 1 | 0a9f88e5cda952db0a82d071f585d090 2 | -------------------------------------------------------------------------------- /locales/en/documents/guidelines-to-achieve-sustainable-decisions/.locale-peer-id: -------------------------------------------------------------------------------- 1 | 934d1c42a693fe004cd8bf8f5ecb97e6 2 | -------------------------------------------------------------------------------- /locales/en/examples/web-application-framework-batteries-included-full-stack-for-a-startup-product/README.md: -------------------------------------------------------------------------------- 1 | index.md -------------------------------------------------------------------------------- /locales/en/templates/decision-record-template-by-michael-nygard/.locale-peer-id: -------------------------------------------------------------------------------- 1 | b1e90e6556c1c8f1e2eb3ac22c8c5077 2 | -------------------------------------------------------------------------------- /locales/en/templates/decision-record-template-for-business-case/.locale-peer-id: -------------------------------------------------------------------------------- 1 | f6d1fb662640a00f4c66c586233dead9 2 | -------------------------------------------------------------------------------- /locales/en/templates/decision-record-template-of-the-madr-project/.locale-peer-id: -------------------------------------------------------------------------------- 1 | 0a9f88e5cda952db0a82d071f585d090 2 | -------------------------------------------------------------------------------- /locales/en/templates/decision-record-template-using-planguage/.locale-peer-id: -------------------------------------------------------------------------------- 1 | bb37e19df57d398b0704d6bd30ee6e6d 2 | -------------------------------------------------------------------------------- /locales/es/documentos/criterios-de-sostenibilidad-de-decisión/.locale-peer-id: -------------------------------------------------------------------------------- 1 | 71d59ed566ae148b8bf42331a84754ac 2 | -------------------------------------------------------------------------------- /locales/es/documentos/cómo-comenzar-a-usar-adr-con-herramientas/.locale-peer-id: -------------------------------------------------------------------------------- 1 | 1a5a03dd6f20cea9f78fb4655a9a7f87 2 | -------------------------------------------------------------------------------- /locales/es/plantillas/plantilla-de-registro-de-decisión-de-edgex/.locale-peer-id: -------------------------------------------------------------------------------- 1 | 01939db0c341e9092c344d904065da12 2 | -------------------------------------------------------------------------------- /locales/fr/documents/conseils-de-travail-déquipe-pour-les-adr/.locale-peer-id: -------------------------------------------------------------------------------- 1 | 875a7715e592ceb45eac5e155ee16318 2 | -------------------------------------------------------------------------------- /locales/fr/modèles/modèle-denregistrement-de-décision-par-edgex/.locale-peer-id: -------------------------------------------------------------------------------- 1 | 01939db0c341e9092c344d904065da12 2 | -------------------------------------------------------------------------------- /locales/ja/ドキュメント/guidelines-to-achieve-sustainable-decisions/.locale-peer-id: -------------------------------------------------------------------------------- 1 | 934d1c42a693fe004cd8bf8f5ecb97e6 2 | -------------------------------------------------------------------------------- /locales/cy/nogfennau/canllawiau-i-gyflawni-penderfyniadau-cynaliadwy/.locale-peer-id: -------------------------------------------------------------------------------- 1 | 934d1c42a693fe004cd8bf8f5ecb97e6 2 | -------------------------------------------------------------------------------- /locales/cy/templedi/templed-cofnod-penderfyniad-ar-gyfer-achos-busnes/.locale-peer-id: -------------------------------------------------------------------------------- 1 | f6d1fb662640a00f4c66c586233dead9 2 | -------------------------------------------------------------------------------- /locales/cy/templedi/templed-cofnod-penderfyniad-gan-michael-nygard/.locale-peer-id: -------------------------------------------------------------------------------- 1 | b1e90e6556c1c8f1e2eb3ac22c8c5077 2 | -------------------------------------------------------------------------------- /locales/en/templates/decision-record-template-for-alexandrian-pattern/.locale-peer-id: -------------------------------------------------------------------------------- 1 | f33e4eb0409f956de201b791749dc9aa 2 | -------------------------------------------------------------------------------- /locales/es/documentos/directrices-para-lograr-decisiones-sostenibles/.locale-peer-id: -------------------------------------------------------------------------------- 1 | 934d1c42a693fe004cd8bf8f5ecb97e6 2 | -------------------------------------------------------------------------------- /locales/es/documentos/qué-es-un-registro-de-decisión-de-arquitectura/.locale-peer-id: -------------------------------------------------------------------------------- 1 | 020ff535ed1a3347a265209291e756b6 2 | -------------------------------------------------------------------------------- /locales/fr/documents/comment-commencer-à-utiliser-les-adr-avec-git/.locale-peer-id: -------------------------------------------------------------------------------- 1 | d6fb3c7d91f95003163e694e74058e9d 2 | -------------------------------------------------------------------------------- /locales/fr/documents/quest-ce-quun-dossier-de-décision-darchitecture/.locale-peer-id: -------------------------------------------------------------------------------- 1 | 020ff535ed1a3347a265209291e756b6 2 | -------------------------------------------------------------------------------- /locales/fr/modèles/modèle-denregistrement-de-décision-du-projet-madr/.locale-peer-id: -------------------------------------------------------------------------------- 1 | 0a9f88e5cda952db0a82d071f585d090 2 | -------------------------------------------------------------------------------- /locales/en/templates/decision-record-template-by-jeff-tyree-and-art-akerman/.locale-peer-id: -------------------------------------------------------------------------------- 1 | f4ca0a94124a91279e1929ea23ab864d 2 | -------------------------------------------------------------------------------- /locales/es/plantillas/plantilla-de-registro-de-decisión-de-michael-nygard/.locale-peer-id: -------------------------------------------------------------------------------- 1 | b1e90e6556c1c8f1e2eb3ac22c8c5077 2 | -------------------------------------------------------------------------------- /locales/es/plantillas/plantilla-de-registro-de-decisión-del-proyecto-madr/.locale-peer-id: -------------------------------------------------------------------------------- 1 | 0a9f88e5cda952db0a82d071f585d090 2 | -------------------------------------------------------------------------------- /locales/es/plantillas/plantilla-de-registro-de-decisión-usando-planguage/.locale-peer-id: -------------------------------------------------------------------------------- 1 | bb37e19df57d398b0704d6bd30ee6e6d 2 | -------------------------------------------------------------------------------- /locales/fr/documents/comment-commencer-à-utiliser-les-adr-avec-des-outils/.locale-peer-id: -------------------------------------------------------------------------------- 1 | 1a5a03dd6f20cea9f78fb4655a9a7f87 2 | -------------------------------------------------------------------------------- /locales/fr/documents/processus-des-dossiers-de-décision-architecturale-aws/.locale-peer-id: -------------------------------------------------------------------------------- 1 | 7d4adf16004ca42546dee49922ae4ccf 2 | -------------------------------------------------------------------------------- /locales/fr/modèles/modèle-denregistrement-de-décision utilisant-plangage/.locale-peer-id: -------------------------------------------------------------------------------- 1 | bb37e19df57d398b0704d6bd30ee6e6d 2 | -------------------------------------------------------------------------------- /locales/fr/modèles/modèle-denregistrement-de-décision-par michael-nygard/.locale-peer-id: -------------------------------------------------------------------------------- 1 | b1e90e6556c1c8f1e2eb3ac22c8c5077 2 | -------------------------------------------------------------------------------- /locales/cy/templedi/templed-cofnod-penderfyniad-ar-gyfer-patrwm-alecsandraidd/.locale-peer-id: -------------------------------------------------------------------------------- 1 | f33e4eb0409f956de201b791749dc9aa 2 | -------------------------------------------------------------------------------- /locales/cy/templedi/templed-cofnod-penderfyniad-gan-jeff-tyree-and-art-akerman/.locale-peer-id: -------------------------------------------------------------------------------- 1 | f4ca0a94124a91279e1929ea23ab864d 2 | -------------------------------------------------------------------------------- /locales/es/documentos/proceso-de-registros-de-decisiones-arquitectónicas-de-aws/.locale-peer-id: -------------------------------------------------------------------------------- 1 | 7d4adf16004ca42546dee49922ae4ccf 2 | -------------------------------------------------------------------------------- /locales/es/plantillas/plantilla-de-registro-de-decisión-para-caso-de-negocio/.locale-peer-id: -------------------------------------------------------------------------------- 1 | f6d1fb662640a00f4c66c586233dead9 2 | -------------------------------------------------------------------------------- /locales/fr/documents/lignes-directrices-pour-atteindre-des-décisions-durables/.locale-peer-id: -------------------------------------------------------------------------------- 1 | 934d1c42a693fe004cd8bf8f5ecb97e6 2 | -------------------------------------------------------------------------------- /locales/fr/modèles/modèle-denregistrement-de-décision-pour-le modèle-alexandrin/.locale-peer-id: -------------------------------------------------------------------------------- 1 | f33e4eb0409f956de201b791749dc9aa 2 | -------------------------------------------------------------------------------- /locales/es/plantillas/plantilla-de-registro-de-decisión-de-jeff-tyree-y-art-akerman/.locale-peer-id: -------------------------------------------------------------------------------- 1 | f4ca0a94124a91279e1929ea23ab864d 2 | -------------------------------------------------------------------------------- /locales/es/plantillas/plantilla-de-registro-de-decisión-para-el-patrón-alejandrino/.locale-peer-id: -------------------------------------------------------------------------------- 1 | f33e4eb0409f956de201b791749dc9aa 2 | -------------------------------------------------------------------------------- /locales/fr/modèles/modèle-denregistrement-de-décision par jeff-tyree-et-art-akerman/.locale-peer-id: -------------------------------------------------------------------------------- 1 | f4ca0a94124a91279e1929ea23ab864d 2 | -------------------------------------------------------------------------------- /locales/index.md: -------------------------------------------------------------------------------- 1 | * [Cymraeg](cy/) 2 | * [English](en/) 3 | * [Española](es/) 4 | * [Français](fr/) 5 | * [한국인](ko/) 6 | * [中文](zh/) 7 | -------------------------------------------------------------------------------- /locales/fr/modèles/modèle-denregistrement-de-décision pour-lanalyse-de-rentabilisation/.locale-peer-id: -------------------------------------------------------------------------------- 1 | f6d1fb662640a00f4c66c586233dead9 2 | -------------------------------------------------------------------------------- /locales/es/plantillas/plantilla-de-registro-de-decisión-usando-planguage/.locale-directory-name-en.txt: -------------------------------------------------------------------------------- 1 | decision-record-template-using-planguage 2 | -------------------------------------------------------------------------------- /locales/ja/翻訳注.txt: -------------------------------------------------------------------------------- 1 | 「ADR」の訳語はAWSやAzureに従って「アーキテクチャ決定レコード」とする。 2 | 3 | AWS： https://docs.aws.amazon.com/ja_jp/prescriptive-guidance/latest/architectural-decision-records/adr-process.html 4 | Azure： https://learn.microsoft.com/ja-jp/azure/well-architected/architect-role/architecture-decision-record -------------------------------------------------------------------------------- /locales/zh/文档/how-to-start-using-adrs-with-tools/index.md: -------------------------------------------------------------------------------- 1 | ## 如何开始使用 ADR 工具 2 | 3 | 您可以以任何方式开始使用 ADR 工具。 4 | 5 | 比如： 6 | 7 | * 如果你喜欢使用 Google Drive 和在线编辑，那么你可以创建一个 Google Doc 或 Google Sheet。 8 | 9 | * 如果你喜欢使用源代码版本控制工具比如 Git，那么你可以为每个 ADR 创建一个文件。 10 | 11 | * 如果你喜欢使用项目规划工具如 Atlassian Jira，那么你可以使用该工具的规划跟踪器。 12 | 13 | * 如果您喜欢使用 wiki 如 MediaWiki，那么你可以创建 ADR wiki 页面。 14 | -------------------------------------------------------------------------------- /locales/zh/文档/how-to-start-using-adrs-with-git/index.md: -------------------------------------------------------------------------------- 1 | # 如何开始使用 Git 进行 ADR 2 | 3 | 如果你倾向于使用 Git 做版本控制，这里将为你介绍如何在一个典型的软件源代码项目中，开始使用 Git 来进行 ADR。 4 | 5 | 新建一个目录来存放 ADR 文件： 6 | 7 | ```sh 8 | $ mkdir adr 9 | ``` 10 | 11 | 为每一个 ADR 创建一个文本文件，例如 `database.txt`: 12 | 13 | ```sh 14 | $ vi database.txt 15 | ``` 16 | 17 | 在该 ADR 中记录任何你期望的内容，更多细节可参考本仓库中的模板。 18 | 19 | 提交该 ADR 文件到你的 Git 仓库。 -------------------------------------------------------------------------------- /locales/ja/ドキュメント/how-to-start-using-adrs-with-tools/index.md: -------------------------------------------------------------------------------- 1 | ## ツールを使ってADRを使い始める方法 2 | 3 | ツールを使ってADRを使い始める方法は自由です。 4 | 5 | 例: 6 | 7 | * Googleドライブとオンライン編集を使いたい場合は、GoogleドキュメントまたはGoogleスプレッドシートを作成できます。 8 | 9 | * Gitなどのソースコードバージョン管理を使いたい場合は、ADRごとにファイルを作成できます。 10 | 11 | * Atlassian Jiraなどのプロジェクト計画ツールを使いたい場合は、ツールの計画トラッカーを使用できます。 12 | 13 | * MediaWikiなどのWikiを使いたい場合は、ADR Wikiを作成できます。 14 | -------------------------------------------------------------------------------- /locales/ko/서류/git에서-adr-사용을-시작하는-방법/index.md: -------------------------------------------------------------------------------- 1 | # git에서 ADR 사용을 시작하는 방법 2 | 3 | git 버전 제어를 사용하고 싶다면 소스 코드가 포함된 일반적인 소프트웨어 프로젝트에 대해 git에서 ADR을 사용하는 방법을 소개합니다. 4 | 5 | ADR 파일용 디렉터리를 만듭니다. 6 | 7 | ``쉬 8 | $ mkdir 주소 9 | ```` 10 | 11 | 각 ADR에 대해 `database.txt`와 같은 텍스트 파일을 만듭니다. 12 | 13 | ``쉬 14 | $ vi 데이터베이스.txt 15 | ```` 16 | 17 | ADR에 원하는 내용을 작성하세요. 아이디어를 얻으려면 이 저장소의 템플릿을 참조하세요. 18 | 19 | ADR을 git repo에 커밋합니다. -------------------------------------------------------------------------------- /locales/ko/서류/도구를-사용하여-adr-사용을-시작하는-방법/index.md: -------------------------------------------------------------------------------- 1 | # 도구를 사용하여 ADR 사용을 시작하는 방법 2 | 3 | 원하는 방식으로 도구를 사용하여 ADR을 사용할 수 있습니다. 4 | 5 | 예를 들어: 6 | 7 | * Google 드라이브와 온라인 편집을 좋아한다면 Google 문서나 Google 시트를 만들 수 있습니다. 8 | 9 | * git과 같은 소스 코드 버전 제어를 사용하려는 경우 각 ADR에 대한 파일을 생성할 수 있습니다. 10 | 11 | * Atlassian Jira와 같은 프로젝트 계획 도구를 사용하고 싶다면 도구의 계획 추적기를 사용할 수 있습니다. 12 | 13 | * MediaWiki와 같은 위키를 사용하고 싶다면 ADR 위키를 생성할 수 있습니다. -------------------------------------------------------------------------------- /locales/ja/ドキュメント/how-to-start-using-adrs-with-git/index.md: -------------------------------------------------------------------------------- 1 | # Git で ADR を使い始める方法 2 | 3 | Git によるバージョン管理をしている場合、ソースコードを含む一般的なソフトウェアプロジェクトで Git で ADR を使い始める手順は以下のとおりです。 4 | 5 | ADR ファイル用のディレクトリを作成します。 6 | 7 | ```sh 8 | $ mkdir adr 9 | ``` 10 | 11 | 各 ADR に対して、`database.txt` などのテキスト ファイルを作成します。 12 | 13 | ```sh 14 | $ vi database.txt 15 | ``` 16 | 17 | ADRには何でも書き込んでください。このリポジトリのテンプレートを参考に、アイデアを得てください。 18 | 19 | ADRをGitリポジトリにコミットしてください。 20 | -------------------------------------------------------------------------------- /locales/ko/서류/파일-이름-규칙/index.md: -------------------------------------------------------------------------------- 1 | # 파일 이름 규칙 2 | 3 | 일반적인 텍스트 파일을 사용하여 ADR을 생성하기로 선택한 경우 고유한 ADR 파일 이름 규칙을 생각해 볼 수 있습니다. 4 | 5 | 우리는 특정 형식의 파일 이름 규칙을 사용하는 것을 선호합니다. 6 | 7 | 예: 8 | 9 | * 선택-database.md 10 | 11 | * 형식-타임스탬프.md 12 | 13 | * 관리-passwords.md 14 | 15 | * 핸들 예외.md 16 | 17 | 파일 이름 규칙: 18 | 19 | * 이름에는 현재형 명령형 동사구가 있습니다. 이는 가독성을 높이고 커밋 메시지 형식과 일치합니다. 20 | 21 | * 이름은 소문자와 대시를 사용합니다(이 저장소와 동일). 이는 가독성과 시스템 유용성의 균형입니다. 22 | 23 | * 확장자는 마크다운입니다. 이는 쉬운 포맷에 유용할 수 있습니다. -------------------------------------------------------------------------------- /locales/ja/ドキュメント/file-name-conventions-for-adrs/index.md: -------------------------------------------------------------------------------- 1 | # ファイル名の命名規則 2 | 3 | 一般的なテキストファイルを使用してADRを作成する場合は、独自のADRファイル名の命名規則を設定することをお勧めします。 4 | 5 | 特定の形式のファイル名の命名規則を使用することをお勧めします。 6 | 7 | 例： 8 | 9 | * データベース選定.md 10 | 11 | * タイムスタンプフォーマット.md 12 | 13 | * パスワード管理.md 14 | 15 | * 例外処理.md 16 | 17 | ファイル名の命名規則： 18 | 19 | * ファイル名は名詞で終わらせます。これは読みやすさを向上させます。 20 | 21 | * ファイル名には日本語と必要に応じてダッシュを使用します（このリポジトリと同じです）。これは読みやすさとシステムの使いやすさのバランスです。 22 | 23 | * 拡張子はmarkdownです。これは書式設定を容易にするのに役立ちます。 -------------------------------------------------------------------------------- /locales/zh/文档/what-is-an-architecture-decision-record /index.md: -------------------------------------------------------------------------------- 1 | **架构决策记录**（ADR）是一份记录重要架构决策及其背景和后果的文件。 2 | 3 | **架构决策** (AD) 是满足重要需求的软件设计选择。 4 | 5 | **架构决策日志** (ADL) 是为某个项目（或组织）创建和维护的所有 ADR 的集合。 6 | 7 | **具体架构意义的重大需求**（ASR）是指对软件系统架构有可衡量的影响的需求。 8 | 9 | 所有这些都属于**架构知识管理**（AKM）的范畴。 10 | 11 | 本文件旨在快速介绍 ADR、如何创建 ADR 以及从何处获取更多信息。 12 | 13 | 缩略语： 14 | 15 | * **AD**: 架构决策 16 | 17 | * **ADL**: 架构决策日志 18 | 19 | * **ADR**: 架构决策记录 20 | 21 | * **AKM**: 架构知识管理 22 | 23 | * **ASR**: 具有架构意义的重大需求 24 | -------------------------------------------------------------------------------- /locales/ja/テンプレート/Michael Nygard による意思決定記録テンプレート/index.md: -------------------------------------------------------------------------------- 1 | # Michael Nygardによる意思決定記録テンプレート 2 | 3 | これは、[アーキテクチャに関する意思決定の文書化 - Michael Nygard](http://thinkrelevance.com/blog/2011/11/15/documenting-architecture-decisions) に掲載されているテンプレートです。 4 | ADR ファイルの管理には [adr-tools](https://github.com/npryce/adr-tools) を使用できます。 5 | 各 ADR ファイルに次のセクションを記述します。 6 | 7 | # タイトル 8 | 9 | ## ステータス 10 | 11 | 提案済み、承認済み、却下済み、非推奨、置き換え済みなど、どんなステータスか？ 12 | 13 | ## 背景 14 | 15 | この決定または変更の動機となっている問題は何か？ 16 | 17 | ## 決定 18 | 19 | 提案または実施する変更は何か？ 20 | 21 | ## 影響 22 | 23 | この変更によって、何が簡単になり、何が難しくなるか？ 24 | -------------------------------------------------------------------------------- /locales/ko/템플릿/index.md: -------------------------------------------------------------------------------- 1 | # 의사결정 기록 템플릿 2 | 3 | * [Jeff Tyree 및 Art Akerman의 의사결정 기록 템플릿](decision-record-template-by-jeff-tyree-and-art-akerman) 4 | * [Michael Nygard의 결정 기록 템플릿](decision-record-template-by-michael-nygard) 5 | * [EdgeX의 의사결정 기록 템플릿](decision-record-template-by-edgex) 6 | * [알렉산드리아 패턴에 대한 결정 기록 템플릿](decision-record-template-for-alexandrian-pattern) 7 | * [비즈니스 사례에 대한 의사결정 기록 템플릿](decision-record-template-for-business-case) 8 | * [MADR 프로젝트의 결정 기록 템플릿](decision-record-template-of-the-madr-project) 9 | * [P언어를 이용한 의사결정 기록 템플릿](decision-record-template-using-p언어) 10 | -------------------------------------------------------------------------------- /locales/en/documents/how-to-start-using-adrs-with-git/index.md: -------------------------------------------------------------------------------- 1 | # How to start using ADRs with git 2 | 3 | If you like using git version control, then here is how we like to start using ADRs with git for a typical software project with source code. 4 | 5 | Create a directory for ADR files: 6 | 7 | ```sh 8 | $ mkdir adr 9 | ``` 10 | 11 | For each ADR, create a text file, such as `database.txt`: 12 | 13 | ```sh 14 | $ vi database.txt 15 | ``` 16 | 17 | Write anything you want in the ADR. See the templates in this repository for ideas. 18 | 19 | Commit the ADR to your git repo. 20 | -------------------------------------------------------------------------------- /locales/ko/템플릿/의사 결정 기록 템플릿-by-michael-nygard/index.md: -------------------------------------------------------------------------------- 1 | # Michael Nygard의 결정 기록 템플릿 2 | 3 | 이는 [아키텍처 결정 문서화 - Michael Nygard](http://thinkrelevance.com/blog/2011/11/15/documenting-architecture-decisions)의 템플릿입니다. 4 | ADR 파일을 관리하려면 [adr-tools](https://github.com/npryce/adr-tools)를 사용할 수 있습니다. 5 | 6 | 각 ADR 파일에서 다음 섹션을 작성합니다. 7 | 8 | # 제목 9 | 10 | ## 상태 11 | 12 | 제안됨, 승인됨, 거부됨, 더 이상 사용되지 않음, 대체됨 등의 상태는 무엇입니까? 13 | 14 | ## 문맥 15 | 16 | 이러한 결정이나 변화에 동기를 부여하는 문제는 무엇입니까? 17 | 18 | ## 결정 19 | 20 | 우리가 제안하거나 수행하는 변화는 무엇입니까? 21 | 22 | ## 결과 23 | 24 | 이번 변화로 인해 어떤 일이 더 쉬워지거나 더 어려워졌나요? 25 | -------------------------------------------------------------------------------- /locales/ja/テンプレート/アレクサンドリアパターンの意思決定記録テンプレート/index.md: -------------------------------------------------------------------------------- 1 | # アレクサンドリアパターンの意思決定記録テンプレート 2 | 3 | ## はじめに 4 | 5 | * プロローグ（要約） 6 | * 議論（背景） 7 | * 解決策（意思決定） 8 | * 結果（結果） 9 | 10 | ## 詳細 ## 11 | 12 | * プロローグ（概要） 13 | * 宣言の要約： 14 | * （ユースケース）の状況において、
15 | （懸念事項）に直面し、
16 | （品質）を達成するために、
17 | （欠点）を受け入れ、
18 | （オプション）を決定しました。 19 | * 議論（背景） 20 | * 影響する力（技術的、政治的、社会的、プロジェクト的）についての説明をする。 21 | * 解決しようとしている問題を説明するストーリーを書く。 22 | * 解決策 23 | * この決定がどのように問題を解決するかを説明する。 24 | * 結果 25 | * 決定の長期的な結果について説明する。 26 | * うまくいったか、うまくいかなかったか、変更されたか、アップグレードされたかなどについて説明する。 27 | -------------------------------------------------------------------------------- /locales/en/documents/how-to-start-using-adrs-with-tools/index.md: -------------------------------------------------------------------------------- 1 | ## How to start using ADRs with tools 2 | 3 | You can start using ADRs with tools any way you want. 4 | 5 | For example: 6 | 7 | * If you like using Google Drive and online editing, then you can create a Google Doc, or Google Sheet. 8 | 9 | * If you like use source code version control, such as git, then you can create a file for each ADR. 10 | 11 | * If you like using project planning tools, such as Atlassian Jira, then you can use the tool's planning tracker. 12 | 13 | * If you like using wikis, such as MediaWiki, then you can create an ADR wiki. 14 | -------------------------------------------------------------------------------- /locales/es/documentos/cómo-comenzar-a-usar-adr-con-git/index.md: -------------------------------------------------------------------------------- 1 | # Cómo comenzar a usar ADR con Git 2 | 3 | Si le gusta usar el control de versiones Git, entonces así es cómo nos gusta comenzar a usar ADR con Git para un proyecto de software típico con el código fuente. 4 | 5 | Cree un directorio para archivos ADR: 6 | 7 | `` `SH 8 | $ mkdir adr 9 | `` `` `` 10 | 11 | Para cada ADR, cree un archivo de texto, como `database.txt`: 12 | 13 | `` `SH 14 | $ vi database.txt 15 | `` `` `` 16 | 17 | Escribe lo que quieras en el ADR. Vea las plantillas en este repositorio de ideas. 18 | 19 | Comprometa el ADR a tu repositorio git. 20 | -------------------------------------------------------------------------------- /locales/fr/documents/comment-commencer-à-utiliser-les-adr-avec-git/index.md: -------------------------------------------------------------------------------- 1 | # Comment commencer à utiliser les ADR avec Git 2 | 3 | Si vous aimez utiliser Git Version Control, alors voici comment nous aimons commencer à utiliser ADRS avec GIT pour un projet logiciel typique avec le code source. 4 | 5 | Créez un répertoire pour les fichiers ADR: 6 | 7 | `` `sh 8 | $ mkdir adr 9 | `` ' 10 | 11 | Pour chaque ADR, créez un fichier texte, tel que `database.txt`: 12 | 13 | `` `sh 14 | $ vi database.txt 15 | `` ' 16 | 17 | Écrivez tout ce que vous voulez dans l'ADR. Voir les modèles de ce référentiel pour les idées. 18 | 19 | Engagez l'ADR dans votre dépôt Git. -------------------------------------------------------------------------------- /locales/ja/ドキュメント/what-is-an-architecture-decision-record/index.md: -------------------------------------------------------------------------------- 1 | ## アーキテクチャ決定記録とは？ 2 | 3 | **アーキテクチャ決定記録** (ADR) は、重要なアーキテクチャ上の決定とその背景および結果を記録した文書です。 4 | 5 | **アーキテクチャ決定** (AD) は、重要な要件に対応するソフトウェア設計上の選択です。 6 | 7 | **アーキテクチャ決定ログ** (ADL) は、特定のプロジェクト (または組織) のために作成および維持されるすべての ADR の集合です。 8 | 9 | **アーキテクチャ上重要な要件** (ASR) は、ソフトウェアシステムのアーキテクチャに測定可能な影響を与える要件です。 10 | 11 | これらはすべて、**アーキテクチャ知識管理** (AKM) のトピックに含まれます。 12 | 13 | このドキュメントの目的は、ADR の概要、作成方法、および詳細情報の参照先を簡単に説明することです。 14 | 15 | 略語： 16 | 17 | * **AD**: アーキテクチャ決定 18 | 19 | * **ADL**: アーキテクチャ決定ログ 20 | 21 | * **ADR**: アーキテクチャ決定記録 22 | 23 | * **AKM**: アーキテクチャ知識管理 24 | 25 | * **ASR**: アーキテクチャ上重要な要件 26 | -------------------------------------------------------------------------------- /locales/ko/서류/아키텍처-결정-기록이란-무엇입니까/index.md: -------------------------------------------------------------------------------- 1 | # 아키텍처 결정 기록이란 무엇입니까? 2 | 3 | **아키텍처 결정 기록**(ADR)은 컨텍스트 및 결과와 함께 내려진 중요한 아키텍처 결정을 포착하는 문서입니다. 4 | 5 | **아키텍처 결정**(AD)은 중요한 요구 사항을 해결하는 소프트웨어 설계 선택입니다. 6 | 7 | **아키텍처 결정 로그**(ADL)는 특정 프로젝트(또는 조직)를 위해 생성 및 유지 관리되는 모든 ADR의 모음입니다. 8 | 9 | **아키텍처적으로 중요한 요구사항**(ASR)은 소프트웨어 시스템의 아키텍처에 측정 가능한 영향을 미치는 요구사항입니다. 10 | 11 | 이 모든 것이 **아키텍처 지식 관리**(AKM) 주제 내에 있습니다. 12 | 13 | 이 문서의 목표는 ADR에 대한 빠른 개요, 생성 방법, 추가 정보를 찾을 수 있는 위치를 제공하는 것입니다. 14 | 15 | 약어: 16 | 17 | * **AD**: 아키텍처 결정 18 | 19 | * **ADL**: 아키텍처 결정 로그 20 | 21 | * **ADR**: 아키텍처 결정 기록 22 | 23 | * **AKM**: 아키텍처 지식 관리 24 | 25 | * **ASR**: 구조적으로 중요한 요구 사항 -------------------------------------------------------------------------------- /locales/cy/nogfennau/sut-i-ddechrau-defnyddio-adrs-gyda-git/index.md: -------------------------------------------------------------------------------- 1 | # Sut i ddechrau defnyddio ADRs gyda git 2 | 3 | Os ydych chi'n hoffi defnyddio rheolaeth fersiwn GIT, yna dyma sut rydyn ni'n hoffi dechrau defnyddio ADRs gyda GIT ar gyfer prosiect meddalwedd nodweddiadol gyda'r cod ffynhonnell. 4 | 5 | Creu cyfeiriadur ar gyfer ffeiliau ADR: 6 | 7 | `` `sh 8 | $ mkdir adr 9 | `` ` 10 | 11 | Ar gyfer pob ADR, crëwch ffeil testun, fel `database.txt`: 12 | 13 | `` `sh 14 | $ vi database.txt 15 | `` ` 16 | 17 | Ysgrifennwch unrhyw beth rydych chi ei eisiau yn yr ADR. Gweler y templedi yn yr ystorfa hon am syniadau. 18 | 19 | Ymrwymwch yr ADR i'ch repo git. -------------------------------------------------------------------------------- /locales/es/documentos/cómo-comenzar-a-usar-adr-con-herramientas/index.md: -------------------------------------------------------------------------------- 1 | ## Cómo comenzar a usar ADR con herramientas 2 | 3 | Puede comenzar a usar ADR con herramientas de la manera que desee. 4 | 5 | Por ejemplo: 6 | 7 | * Si le gusta usar Google Drive y la edición en línea, puede crear un Doc Google o Google Sohad. 8 | 9 | * Si desea usar el control de versiones del código fuente, como GIT, puede crear un archivo para cada ADR. 10 | 11 | * Si le gusta usar herramientas de planificación de proyectos, como Atlassian JIRA, puede usar el rastreador de planificación de la herramienta. 12 | 13 | * Si te gusta usar wikis, como MediaWiki, entonces puedes crear un wiki ADR. 14 | * -------------------------------------------------------------------------------- /locales/ja/テンプレート/Planguageを使用した意思決定記録テンプレート/index.md: -------------------------------------------------------------------------------- 1 | # Planguageを使用した意思決定記録テンプレート 2 | 3 | https://www.iaria.org/conferences2012/filesICCGI12/Tutorial%20Specifying%20Effective%20Non-func.pdf も参照 4 | 5 | ## Planguageとは? 6 | 7 | Planguage は、以下のキーワードを使用する計画言語です。 8 | 9 | * タグ: 一意で永続的な識別子 10 | * 要点: 要件または対象となる領域の簡潔な要約 11 | * 要件: 要件自体の詳細を記述したテキスト 12 | * 根拠: 要件を正当化する根拠 13 | * 優先度: 優先度とリソースの要求に関する記述 14 | * 利害関係者: 要件によって実質的に影響を受ける関係者 15 | * ステータス: 要件のステータス (ドラフト、レビュー済み、コミット済みなど) 16 | * 所有者: 要件の実装責任者 17 | * 作成者: 要件を作成した人物 18 | * リビジョン: 記述のバージョン番号 19 | * 日付: 最新のリビジョン日 20 | * 前提条件: 現在または将来、不正確であれば問題を引き起こす可能性のあるもの 21 | * リスク: 誤動作、遅延、その他の悪影響を引き起こす可能性のあるもの 22 | * 定義: 用語の定義 (用語集を使用することをお勧めします) 23 | 24 | -------------------------------------------------------------------------------- /locales/ko/템플릿/의사결정 기록 템플릿 사용 p언어/index.md: -------------------------------------------------------------------------------- 1 | # P언어를 이용한 의사결정 기록 템플릿 2 | 3 | https://www.iaria.org/conferences2012/filesICCGI12/Tutorial%20Specifying%20Effective%20Non-func.pdf를 참조하세요. 4 | 5 | ## P언어란 무엇인가요? 6 | 7 | P언어는 다음 키워드를 사용하는 계획 언어입니다. 8 | 9 | * 태그: 고유하고 지속적인 식별자 10 | * 요지: 요구사항이나 다루는 영역에 대한 간략한 요약 11 | * 요구사항: 요구사항 자체를 자세히 설명하는 텍스트 12 | * 근거(Rationale): 요구사항을 정당화하는 추론 13 | * 우선순위: 자원에 대한 우선순위 및 주장에 대한 설명 14 | * 이해관계자: 요구사항으로 인해 실질적으로 영향을 받는 당사자 15 | * 상태: 요구사항의 상태(초안, 검토, 커밋 등) 16 | * 소유자: 요구사항 구현을 담당하는 사람 17 | * 작성자 : 요구사항을 작성한 사람 18 | * 개정: 명세서의 버전 번호 19 | * 날짜 : 가장 최근 개정된 날짜 20 | * 가정: 지금 또는 나중에 사실이 아닐 경우 문제를 일으킬 수 있는 모든 것 21 | * 위험 : 오작동, 지연 또는 기타 부정적인 영향을 일으킬 수 있는 모든 것 22 | * 정의: 용어의 정의(용어집을 사용하는 것이 더 좋음) 23 | -------------------------------------------------------------------------------- /locales/cy/nogfennau/sut-i-ddechrau-defnyddio-adrs-gydag-offer/index.md: -------------------------------------------------------------------------------- 1 | ## Sut i ddechrau defnyddio ADRs gydag offer 2 | 3 | Gallwch chi ddechrau defnyddio ADRs gydag offer unrhyw ffordd rydych chi ei eisiau. 4 | 5 | Er enghraifft: 6 | 7 | * Os ydych chi'n hoffi defnyddio Google Drive a Golygu Ar -lein, yna gallwch chi greu Google Doc, neu Google Sheet. 8 | 9 | * Os ydych chi'n hoffi defnyddio rheolaeth fersiwn cod ffynhonnell, fel Git, yna gallwch chi greu ffeil ar gyfer pob ADR. 10 | 11 | * Os ydych chi'n hoffi defnyddio offer cynllunio prosiect, fel Atlassian Jira, yna gallwch ddefnyddio traciwr cynllunio'r offeryn. 12 | 13 | * Os ydych chi'n hoffi defnyddio wicis, fel mediawiki, yna gallwch chi greu wici ADR. -------------------------------------------------------------------------------- /locales/ja/テンプレート/index.md: -------------------------------------------------------------------------------- 1 | # Decision record templates 2 | 3 | * [Decision record template by Jeff Tyree and Art Akerman](decision-record-template-by-jeff-tyree-and-art-akerman) 4 | * [Decision record template by Michael Nygard](decision-record-template-by-michael-nygard) 5 | * [Decision record template by EdgeX](decision-record-template-by-edgex) 6 | * [Decision record template for Alexandrian pattern](decision-record-template-for-alexandrian-pattern) 7 | * [Decision record template for business case](decision-record-template-for-business-case) 8 | * [Decision record template of the MADR Project](decision-record-template-of-the-madr-project) 9 | * [Decision record template using Planguage](decision-record-template-using-planguage) 10 | -------------------------------------------------------------------------------- /locales/fr/documents/comment-commencer-à-utiliser-les-adr-avec-des-outils/index.md: -------------------------------------------------------------------------------- 1 | # Comment commencer à utiliser les ADR avec des outils 2 | 3 | Vous pouvez commencer à utiliser les ADR avec des outils comme vous le souhaitez. 4 | 5 | Par exemple: 6 | 7 | * Si vous aimez utiliser Google Drive et l'édition en ligne, vous pouvez créer un Google Doc ou Google Sheet. 8 | 9 | * Si vous aimez utiliser le contrôle de la version du code source, tel que GIT, vous pouvez créer un fichier pour chaque ADR. 10 | 11 | * Si vous aimez utiliser des outils de planification de projet, tels que Atlassian Jira, vous pouvez utiliser le tracker de planification de l'outil. 12 | 13 | * Si vous aimez utiliser des wikis, comme MediaWiki, vous pouvez créer un Wiki ADR. -------------------------------------------------------------------------------- /locales/es/plantillas/index.md: -------------------------------------------------------------------------------- 1 | # Plantilla de registro de decisiones 2 | 3 | * [Plantilla de registro de decisión de Jeff Tyree y Art Akerman](plantilla-de-registro-de-decisión-de-jeff-tyree-y-art-akerman/) 4 | * [Plantilla de registro de decisión de Michael Nygard](plantilla-de-registro-de-decisión-de-michael-nygard/) 5 | * [Plantilla de registro de decisión para el patrón alejandrino](plantilla-de-registro-de-decisión-para-el-patrón-alejandrino/) 6 | * [Plantilla de registro de decisión para caso de negocio](plantilla-de-registro-de-decisión-para-caso-de-negocio/) 7 | * [Plantilla de registro de decisión del proyecto MADR](plantilla-de-registro-de-decisión-del-proyecto-madr/) 8 | * [Plantilla de registro de decisión usando Planguage](plantilla-de-registro-de-decisión-usando-planguage/) 9 | -------------------------------------------------------------------------------- /CITATION.cff: -------------------------------------------------------------------------------- 1 | cff-version: 1.2.0 2 | title: Architecture decision record (ADR) 3 | message: >- 4 | If you use this work and you want to cite it, 5 | then you can use the metadata from this file. 6 | type: software 7 | authors: 8 | - given-names: Joel Parker 9 | family-names: Henderson 10 | email: joel@joelparkerhenderson.com 11 | affiliation: joelparkerhenderson.com 12 | orcid: 'https://orcid.org/0009-0000-4681-282X' 13 | identifiers: 14 | - type: url 15 | value: 'https://github.com/joelparkerhenderson/architecture-decision-record/' 16 | description: Architecture decision record (ADR) 17 | repository-code: 'https://github.com/joelparkerhenderson/architecture-decision-record/' 18 | abstract: >- 19 | Architecture decision record (ADR) 20 | license: See license file 21 | -------------------------------------------------------------------------------- /locales/cy/templedi/index.md: -------------------------------------------------------------------------------- 1 | # Templedi cofnodion penderfyniadau 2 | 3 | * [Templed cofnod penderfyniad gan Jeff Tyree ac Art Akerman](templed-cofnod-penderfyniad-gan-jeff-tyree-and-art-akerman) 4 | * [Templed cofnod penderfyniad gan Michael Nygard](templed-cofnod-penderfyniad-gan-michael-nygard) 5 | * [Templed cofnod penderfyniad gan EdgeX](templed-cofnod-penderfyniad-gan-edgex) 6 | * [Templed cofnod penderfyniad ar gyfer patrwm Alecsandraidd](templed-cofnod-penderfyniad-ar-gyfer-patrwm-alecsandraidd) 7 | * [Templed cofnod penderfyniad ar gyfer achos busnes](templed-cofnod-penderfyniad-ar-gyfer-achos-busnes) 8 | * [Templed cofnod benderfyniad y Prosiect MADR](templed-cofnod-penderfyniad-y-prosiect-madr) 9 | * [Templed cofnod penderfyniad gan ddefnyddio Planguage](templed-cofnod-penderfyniad-gan-planguage) 10 | -------------------------------------------------------------------------------- /locales/en/documents/file-name-conventions-for-adrs/index.md: -------------------------------------------------------------------------------- 1 | # File name conventions 2 | 3 | If you choose to create your ADRs using typical text files, then you may want to come up with your own ADR file name convention. 4 | 5 | We prefer to use a file name convention that has a specific format. 6 | 7 | Examples: 8 | 9 | * choose-database.md 10 | 11 | * format-timestamps.md 12 | 13 | * manage-passwords.md 14 | 15 | * handle-exceptions.md 16 | 17 | Our file name convention: 18 | 19 | * The name has a present tense imperative verb phrase. This helps readability and matches our commit message format. 20 | 21 | * The name uses lowercase and dashes (same as this repo). This is a balance of readability and system usability. 22 | 23 | * The extension is markdown. This can be useful for easy formatting. 24 | -------------------------------------------------------------------------------- /locales/ko/서류/adr을-위한-팀워크-조언/index.md: -------------------------------------------------------------------------------- 1 | # ADR을 위한 팀워크 조언 2 | 3 | 팀에서 의사결정 기록 사용을 고려하고 있다면 다음은 여러 팀과 협력하면서 배운 몇 가지 조언입니다. 4 | 5 | "무엇"을 강요하기보다는 "왜"에 대해 함께 이야기함으로써 팀원을 이끌 수 있는 기회가 있습니다. 예를 들어, 의사 결정 기록은 팀이 더 현명하게 생각하고 더 효과적으로 의사소통할 수 있는 방법입니다. 결정 기록이 사후 강제 서류 요구 사항일 뿐이라면 가치가 없습니다. 6 | 7 | 일부 팀은 "ADR"이라는 약어보다 "결정"이라는 이름을 더 선호합니다. 일부 팀에서 "결정"이라는 디렉터리 이름을 사용하면 마치 전구가 켜지는 것과 같으며 팀은 공급업체 결정, 계획 결정, 일정 결정 등과 같은 더 많은 정보를 디렉터리에 넣기 시작합니다. 정보는 동일한 템플릿을 사용할 수 있습니다. 우리는 사람들이 약어("ADR")보다 단어("결정")로 더 빨리 배우고 "기록"이라는 단어가 제거되면 진행 중인 문서를 작성하려는 동기가 더 높다고 가정합니다. 일부 개발자와 일부 관리자도 마찬가지입니다. "건축"이라는 단어를 싫어합니다. 8 | 9 | 이론적으로는 불변성이 이상적입니다. 실제로 우리 팀에서는 가변성이 더 잘 작동했습니다. 날짜 스탬프와 함께 기존 ADR에 새 정보를 삽입하고 결정 후 정보가 도착했다는 메모를 삽입합니다. 이러한 접근 방식은 우리 모두가 업데이트할 수 있는 "살아있는 문서"로 이어집니다. 일반적인 업데이트는 새로운 팀원, 새로운 제품, 실제 사용 결과, 공급업체 기능, 가격 계획, 라이선스 계약 등과 같은 사후 제3자 변경 사항을 통해 정보를 얻는 경우입니다. -------------------------------------------------------------------------------- /locales/ja/ドキュメント/teamwork-advice-for-adrs/index.md: -------------------------------------------------------------------------------- 1 | # ADR向けチームワークアドバイス 2 | 3 | チームで意思決定記録の活用を検討されている方は、ここの多くのチームとの協働を通して得られたアドバイスが参考になります。 4 | 5 | 「何を」ではなく「なぜ」を話し合うことで、チームメイトを導く機会が得られます。例えば、意思決定記録は、チームがよりスマートに考え、より効果的なコミュニケーションを図るための手段です。しかし、事後的に強制的に書類作成を求められるような意思決定記録では、意味がありません。 6 | 7 | チームによっては、「ADR」という略語よりも「決定」という名称を好むところもあります。とあるチームでは、「decisions」というディレクトリを使うことで、まるで電球が点いたかのように、ベンダーの決定、計画の決定、スケジュールの決定など、より多くの情報をディレクトリに入力し始めました。これらの情報はすべて同じテンプレートを使用できます。私たちは、略語（「ADR」）よりも単語（「decisions」）の方が学習が早くなる、また「record」という単語を削除することで作業中のドキュメントを作成する意欲が高まる、そして一部の開発者やマネージャーは「architecture」という単語を嫌う、という仮説を立てています。 8 | 9 | 理論上、ADRは不変であることが理想的です。しかし実際、私たちのチームでは可変性の方がうまく機能していました。新しい情報を既存のADRに挿入し、日付スタンプと、決定後に情報が届いたことを示すメモを添えます。このようなアプローチにより、全員が更新できる「生きた文書」が生まれます。例えば典型的な更新の例でいうと、新しいチームメンバー、新しい提供物、実際の使用してみた結果、あるいはベンダーの機能、価格プラン、ライセンス契約などのサードパーティの事後的な変更などによって情報を入手した場合です。 10 | -------------------------------------------------------------------------------- /locales/en/templates/decision-record-template-by-michael-nygard/index.md: -------------------------------------------------------------------------------- 1 | # Decision record template by Michael Nygard 2 | 3 | This is the template in [Documenting architecture decisions - Michael Nygard](http://thinkrelevance.com/blog/2011/11/15/documenting-architecture-decisions). 4 | You can use [adr-tools](https://github.com/npryce/adr-tools) for managing the ADR files. 5 | 6 | In each ADR file, write these sections: 7 | 8 | # Title 9 | 10 | ## Status 11 | 12 | What is the status, such as proposed, accepted, rejected, deprecated, superseded, etc.? 13 | 14 | ## Context 15 | 16 | What is the issue that we're seeing that is motivating this decision or change? 17 | 18 | ## Decision 19 | 20 | What is the change that we're proposing and/or doing? 21 | 22 | ## Consequences 23 | 24 | What becomes easier or more difficult to do because of this change? 25 | -------------------------------------------------------------------------------- /locales/cy/nogfennau/confensiynau-enw-ffeil/index.md: -------------------------------------------------------------------------------- 1 | # Confensiynau Enw Ffeil 2 | 3 | Os dewiswch greu eich ADRs gan ddefnyddio ffeiliau testun nodweddiadol, yna efallai yr hoffech feddwl am eich Confensiwn Enw Ffeil ADR eich hun. 4 | 5 | Mae'n well gennym ddefnyddio confensiwn enw ffeil sydd â fformat penodol. 6 | 7 | Enghreifftiau: 8 | 9 | * dewiswch-database.md 10 | 11 | * format-timestamps.md 12 | 13 | * rheoli-passwords.md 14 | 15 | * trin-exceptions.md 16 | 17 | Ein Confensiwn Enw Ffeil: 18 | 19 | * Mae gan yr enw ymadrodd berf hanfodol amser presennol. Mae hyn yn helpu darllenadwyedd ac yn cyd -fynd â'n fformat neges ymrwymo. 20 | 21 | * Mae'r enw'n defnyddio llythrennau bach a rhuthrau (yr un fath â'r repo hwn). Mae hwn yn gydbwysedd o ddarllenadwyedd a defnyddioldeb system. 22 | 23 | * Mae'r estyniad yn marcio. Gall hyn fod yn ddefnyddiol ar gyfer fformatio hawdd. -------------------------------------------------------------------------------- /locales/cy/templedi/templed-cofnod-penderfyniad-gan-michael-nygard/index.md: -------------------------------------------------------------------------------- 1 | # Templed cofnod penderfyniad gan Michael Nygard 2 | 3 | Dyma'r templed yn [Dogfennu penderfyniadau pensaernïaeth - Michael Nygard](http://thinkrelevance.com/blog/2011/11/15/documenting-architecture-decisions). 4 | Gallwch ddefnyddio [adr-tools](https://github.com/npryce/adr-tools) ar gyfer rheoli'r ffeiliau ADR. 5 | 6 | Ym mhob ffeil ADR, ysgrifennwch yr adrannau hyn: 7 | 8 | # Teitl 9 | 10 | ## Statws 11 | 12 | Beth yw'r statws, megis y rhai a gynigir, a dderbyniwyd, a wrthodwyd, a anghymeradwywyd, a ddisodlwyd, ac ati? 13 | 14 | ## Cyd-destun 15 | 16 | Beth yw'r mater yr ydym yn ei weld sy'n ysgogi'r penderfyniad neu'r newid hwn? 17 | 18 | ## Penderfyniad 19 | 20 | Beth yw'r newid rydym yn ei gynnig a/neu'n ei wneud? 21 | 22 | ## Canlyniadau 23 | 24 | Beth sy'n dod yn haws neu'n anos i'w wneud oherwydd y newid hwn? -------------------------------------------------------------------------------- /locales/ko/서류/지속-가능한-결정을-달성하기-위한-지침/index.md: -------------------------------------------------------------------------------- 1 | # 지속 가능한 결정을 달성하기 위한 지침 2 | 3 | 4 | 5 | 우리는 지속 가능한 결정을 내리기 위한 지침과 평가가 될 수 있는 다음과 같은 교훈을 얻었습니다. 6 | 7 | 1. 초기 의사결정 문서화를 위해 간결하고 최소한의 접근 방식을 사용하십시오. 8 | 9 | 2. 대상 아키텍처를 문서화하고 이해하는 데 충분히 관련된 모든 중요한 결정의 우선순위를 지정하고 포착합니다. 10 | 11 | 3. 초기 작업이 완료된 후에만 본격적인 템플릿을 사용하여 특히 중요한 결정을 자세히 설명합니다. 즉, 의사 결정자가 아키텍처 결정에 만족하고 이러한 결정을 조만간 수정할 필요가 없다고 확신할 때입니다. ). 12 | 13 | 4. 1단계의 린/최소 버전을 올바른 세분성 수준의 문서화된 결정의 짧은 버전으로 사용하여 사소하거나 명백한 결정뿐만 아니라 자세한 결정에 대한 개요를 제공합니다. 14 | 15 | 5. 가능한 한 지침 모델이나 기타 소스에서 얻은 기존 건축 지식을 활용하십시오. 그러한 지식을 검토하고 확장하여 특정 결정의 맥락에 맞추십시오. 16 | 17 | 6. 의사결정과 요구사항 및 아키텍처 설계/코드 사이에 추적성 링크가 설정되어 있는지 확인하십시오. 18 | 19 | 7. 변경 후 추적성 링크가 동기화되는지 확인하기 위해 자동화된 일관성 검사를 제공합니다. 의사결정과 기타 소프트웨어 아티팩트 간의 종속성 수를 제한합니다. 20 | 21 | 8 정당화에 대한 지침을 결과적으로 강력하게 적용하십시오. 이는 근거를 제공하기 때문에 의사결정 문서에서 가장 중요한 부분입니다. -------------------------------------------------------------------------------- /locales/es/plantillas/plantilla-de-registro-de-decisión-de-michael-nygard/index.md: -------------------------------------------------------------------------------- 1 | # Plantilla de registro de decisiones de Michael Nygard 2 | 3 | Esta es la plantilla en [Documentación de decisiones de arquitectura - Michael Nygard] (http://thinkrelevance.com/blog/2011/11/15/documenting-architecture-decisions). 4 | Puede utilizar [adr-tools](https://github.com/npryce/adr-tools) para administrar los archivos ADR. 5 | 6 | En cada archivo ADR, escriba estas secciones: 7 | 8 | # Título 9 | 10 | ## Estado 11 | 12 | ¿Cuál es el estado, como propuesto, aceptado, rechazado, obsoleto, reemplazado, etc.? 13 | 14 | ## Contexto 15 | 16 | ¿Cuál es el problema que estamos viendo que está motivando esta decisión o cambio? 17 | 18 | ## Decisión 19 | 20 | ¿Cuál es el cambio que estamos proponiendo y/o haciendo? 21 | 22 | ## Consecuencias 23 | 24 | ¿Qué se vuelve más fácil o más difícil de hacer debido a este cambio? -------------------------------------------------------------------------------- /locales/fr/modèles/index.md: -------------------------------------------------------------------------------- 1 | # Modèles d'enregistrement de décision 2 | 3 | * [Modèle d'enregistrement de décision par Jeff Tyree et Art Akerman](modèle-denregistrement-de-décision-par-jeff-tyree-et-art-akerman) 4 | * [Modèle d'enregistrement de décision par Michael Nygard](modèle-denregistrement-de-décision-par-michael-nygard) 5 | * [Modèle d'enregistrement de décision par EdgeX](modèle-denregistrement-de-décision-par-edgex) 6 | * [Modèle d'enregistrement de décision pour le modèle alexandrin](modèle-denregistrement-de-décision-pour-le-modèle-alexandrin) 7 | * [Modèle d'enregistrement de décision pour l'analyse de rentabilisation](modèle-denregistrement-de-décision-pour-lanalyse-de-rentabilisation) 8 | * [Modèle d'enregistrement de décision du projet MADR](modèle-denregistrement-de-décision-du-projet-madr) 9 | * [Modèle d'enregistrement de décision utilisant Plangage](modèle-denregistrement-de-décision-utilisant-plangage) 10 | -------------------------------------------------------------------------------- /locales/fr/modèles/modèle-denregistrement-de-décision-par michael-nygard/index.md: -------------------------------------------------------------------------------- 1 | # Modèle d'enregistrement de décision par Michael Nygard 2 | 3 | Il s'agit du modèle dans [Documentation des décisions d'architecture - Michael Nygard] (http://thinkrelevance.com/blog/2011/11/15/documenting-architecture-decisions). 4 | Vous pouvez utiliser [adr-tools](https://github.com/npryce/adr-tools) pour gérer les fichiers ADR. 5 | 6 | Dans chaque fichier ADR, écrivez ces sections : 7 | 8 | # Titre 9 | 10 | ## Statut 11 | 12 | Quel est le statut : proposé, accepté, rejeté, obsolète, remplacé, etc. ? 13 | 14 | ## Contexte 15 | 16 | Quel est le problème que nous constatons et qui motive cette décision ou ce changement ? 17 | 18 | ## Décision 19 | 20 | Quel est le changement que nous proposons et/ou faisons ? 21 | 22 | ## Conséquences 23 | 24 | Qu’est-ce qui devient plus facile ou plus difficile à faire à cause de ce changement ? 25 | -------------------------------------------------------------------------------- /locales/ja/ドキュメント/guidelines-to-achieve-sustainable-decisions/index.md: -------------------------------------------------------------------------------- 1 | # 持続可能な意思決定を実現するためのガイドライン 2 | 3 | 4 | 5 | 私たちは、この作業を通して、持続可能な意思決定を実現するためのガイドラインと評価基準となる以下の教訓を学びました。 6 | 7 | 1. 初期の意思決定文書には、無駄を省いたミニマリスト的なアプローチを採用する。 8 | 9 | 2. 対象アーキテクチャの文書化と理解に十分関連する重要な意思決定をすべて優先順位付けし、記録する。 10 | 11 | 3. 特に重要な意思決定については、初期作業が完了した後（つまり、意思決定者がアーキテクチャ上の意思決定に満足し、これらの意思決定をすぐに修正する必要がないと確信した後）にのみ、本格的なテンプレートを使用して詳細を記述する。 12 | 13 | 4. ステップ1で作成した簡潔なバージョンを、適切な粒度で文書化された意思決定の短縮版として使用し、詳細な意思決定だけでなく、些細な意思決定や明白な意思決定についても概要を示す。 14 | 15 | 5. 可能な限り、ガイダンスモデルやその他の情報源から得られる既存のアーキテクチャに関する知識を活用します。これらの知識をレビュー・拡張し、具体的な意思決定のコンテキストに適合させます。 16 | 17 | 6. 意思決定と要件、そしてアーキテクチャ設計／実装との間にトレーサビリティがしっかりと繋がっていることを確認する。 18 | 19 | 7. 変更後にトレーサビリティの繋がりが同期されていることを確認するために、自動化された整合性チェックを提供する。意思決定と他のソフトウェア成果物との間の依存関係の数を制限する。 20 | 21 | 8. 根拠の紐づいたガイドラインを、結果的かつ強力に適用する。このガイドラインは、合理性を示すものであるため、意思決定文書の中で最も重要な部分。 -------------------------------------------------------------------------------- /locales/es/documentos/convenciones-de-nombre-de-archivo/index.md: -------------------------------------------------------------------------------- 1 | # Convenciones de nombre de archivo 2 | 3 | Si elige crear sus ADR usando archivos de texto típicos, es posible que desee crear su propia convención de nombre de archivo ADR. 4 | 5 | Preferimos usar una convención de nombre de archivo que tenga un formato específico. 6 | 7 | Ejemplos: 8 | 9 | * elija-database.md 10 | 11 | * format-timestamps.md 12 | 13 | * administrar-passwords.md 14 | 15 | * mango-excepciones.md 16 | 17 | Nuestra convención de nombre de archivo: 18 | 19 | * El nombre tiene una frase verbal imperativa de tiempo presente. Esto ayuda a la legibilidad y coincide con nuestro formato de mensaje de confirmación. 20 | 21 | * El nombre usa minúsculas y guiones (igual que este repositorio). Este es un equilibrio de legibilidad y usabilidad del sistema. 22 | 23 | * La extensión es Markdown. Esto puede ser útil para un fácil formato. -------------------------------------------------------------------------------- /locales/en/templates/decision-record-template-for-alexandrian-pattern/index.md: -------------------------------------------------------------------------------- 1 | # Decision record template for Alexandrian pattern 2 | 3 | ## Introduction 4 | 5 | * Prologue (Summary) 6 | * Discussion (Context) 7 | * Solution (Decision) 8 | * Consequences (Results) 9 | 10 | ## Specifics ## 11 | 12 | * Prologue (Summary) 13 | * Statement to summarize: 14 | * In the context of (use case)
15 | facing (concern)
16 | we decided for (option)
17 | to achieve (quality)
18 | accepting (downside). 19 | * Discussion (Context) 20 | * Explains the forces at play (technical, political, social, project). 21 | * This is the story explaining the problem we are looking to resolve. 22 | * Solution 23 | * Explains how the decision will solve the problem. 24 | * Consequences 25 | * Explains the results of the decision over the long term. 26 | * Did it work, not work, was changed, upgraded, etc. 27 | -------------------------------------------------------------------------------- /locales/fr/documents/conventions-de-noms-de-fichiers/index.md: -------------------------------------------------------------------------------- 1 | # Conventions de noms de fichiers 2 | 3 | Si vous choisissez de créer votre ADR à l'aide de fichiers texte typiques, vous souhaiterez peut-être trouver votre propre convention de nom de fichier ADR. 4 | 5 | Nous préférons utiliser une convention de nom de fichier qui a un format spécifique. 6 | 7 | Exemples: 8 | 9 | * choisir-database.md 10 | 11 | * format-timestamps.md 12 | 13 | * gérer-les-mots-de-passe.md 14 | 15 | * manche-exception.md 16 | 17 | Notre convention de nom de fichier: 18 | 19 | * Le nom a une phrase verbale impérative actuelle. Cela aide la lisibilité et correspond à notre format de message de validation. 20 | 21 | * Le nom utilise des minuscules et des tirets (identiques à ce référentiel). Il s'agit d'un équilibre entre lisibilité et convivialité du système. 22 | 23 | * L'extension est Markdown. Cela peut être utile pour une mise en forme facile. -------------------------------------------------------------------------------- /locales/es/plantillas/plantilla-de-registro-de-decisión-para-el-patrón-alejandrino/index.md: -------------------------------------------------------------------------------- 1 | # Plantilla de registro de decisión para el patrón alejandrino 2 | 3 | ## Introducción 4 | 5 | * Prólogo (Resumen) 6 | * Discusión (Contexto) 7 | * Solución (Decisión) 8 | * Consecuencias (Resultados) 9 | 10 | ## Detalles ## 11 | 12 | * Prólogo (Resumen) 13 | * Declaración para resumir: 14 | * En el contexto de (caso de uso)
15 | enfrentando (preocupación)
16 | nos decidimos por (opción)
17 | lograr (calidad)
18 | aceptar (desventaja). 19 | * Discusión (Contexto) 20 | * Explica las fuerzas en juego (técnicas, políticas, sociales, de proyecto). 21 | * Esta es la historia que explica el problema que buscamos resolver. 22 | * Solución 23 | * Explica cómo la decisión resolverá el problema. 24 | * Consecuencias 25 | * Explica los resultados de la decisión a largo plazo. 26 | * Funcionó, no funcionó, fue cambiado, actualizado, etc. -------------------------------------------------------------------------------- /locales/cy/templedi/templed-cofnod-penderfyniad-ar-gyfer-patrwm-alecsandraidd/index.md: -------------------------------------------------------------------------------- 1 | # Templed cofnod penderfyniad ar gyfer patrwm Alecsandraidd 2 | 3 | ## Rhagymadrodd 4 | 5 | * Prologue (Crynodeb) 6 | * Trafodaeth (Cyd-destun) 7 | * Ateb (Penderfyniad) 8 | * Canlyniadau (Canlyniadau) 9 | 10 | ## Manylebau ## 11 | 12 | * Prologue (Crynodeb) 13 | * Datganiad i grynhoi: 14 | * Yng nghyd-destun (achos defnydd)
15 | wynebu (pryder)
16 | penderfynon ni ar gyfer (opsiwn)
17 | i gyflawni (ansawdd)
18 | derbyn (anfantais). 19 | * Trafodaeth (Cyd-destun) 20 | * Yn egluro'r grymoedd sydd ar waith (technegol, gwleidyddol, cymdeithasol, prosiect). 21 | * Dyma'r stori sy'n esbonio'r broblem yr ydym am ei datrys. 22 | * Ateb 23 | * Egluro sut y bydd y penderfyniad yn datrys y broblem. 24 | * Canlyniadau 25 | * Yn egluro canlyniadau'r penderfyniad dros y tymor hir. 26 | * A weithiodd, nid gweithio, ei newid, ei uwchraddio, ac ati. -------------------------------------------------------------------------------- /locales/ja/ドキュメント/decision-sustainability-criteria/index.md: -------------------------------------------------------------------------------- 1 | # 意思決定の持続可能性基準 2 | 3 | 4 | 5 | 意思決定の持続可能性を詳細に定義するために、5 つの主要な基準を導き出しました。 6 | 7 | ## 戦略的 8 | 9 | 意思決定において、戦略的な結果を検討する人は、意思決定の長期的な影響（例えば、将来の運用や保守の取り組みなど）を考慮する必要があります。 10 | 11 | ## 測定可能で管理可能 12 | 13 | 意思決定の成果は、客観的な基準、理想的には数値基準（例えば、品質属性シナリオやワークショップ4 で普及するようなもの）に基づいて、時間の経過とともに測定・評価できます。すべてのきめ細かな意思決定を網羅することは不可能であるため、アーキテクトは意思決定の粒度をある程度の詳細レベル（設計クラスの作成など）に制限する必要があります。これにより、意思決定の持続可能性が向上し、トレーサビリティのリンク数が減少します。さらに、意思決定間の依存関係の数を制限することで、変更による波及効果を軽減できます。 14 | 15 | ## 達成可能かつ現実的 16 | 17 | 問題に対するソリューションの適合根拠は、実用的に選択し、明確にする必要があります。例えば、アーキテクトは、過剰なエンジニアリングや不足したエンジニアリングを避けるよう配慮した（つまり、「十分に良い」アプローチを適用すべきである）ことを示します。 18 | 19 | ## 要件に基づいているか 20 | 21 | 意思決定は、ドメイン固有の計の経験とコンテキストに基づいて行う必要があります。社内環境だけでなく、開発チームの現在のスキル、トレーニング予算、プロセスなど、プロジェクトの要件と制約も考慮する必要があります。 22 | 23 | ## 時代を超えられるか 24 | 25 | 意思決定は、すぐに時代遅れになる可能性が低い経験と知識に基づいて行うべきです。例えば、アーキテクトはプラットフォームに依存しないアーキテクチャパターンや戦略を選択します。 -------------------------------------------------------------------------------- /locales/ja/ドキュメント/suggestions-for-writing-good-adrs/index.md: -------------------------------------------------------------------------------- 1 | ## 良いADR作成のための提案 2 | 3 | 良いADRの特徴： 4 | 5 | * 根拠を示すこと: 特定のADを実施する理由を説明します。これには、「背景」（下記参照）、様々な選択肢の長所と短所、機能の比較、費用対効果の検討などが含まれます。 6 | 7 | * 具体的であること: 各ADRは、複数のADではなく、1つのADについて記述する必要があります。 8 | 9 | * タイムスタンプ: ADRの各項目がいつ作成されたかを明確にします。これは、コスト、スケジュール、規模感など、時間の経過とともに変化する可能性のある要素において特に重要です。 10 | 11 | * 変更不可であること: ADR内の既存の情報を変更しないでください。代わりに、新しい情報を追加してADRを修正するか、新しいADRを作成して既存のADRを置き換えます。 12 | 13 | ADRにおける適切な「背景」セクションの特徴： 14 | 15 | * 組織の状況とビジネス上の優先事項を説明する。 16 | 17 | * チームの社会的・スキル構成に基づいた根拠と考慮事項を記載する。 18 | 19 | * 関連する長所と短所を記載し、ニーズと目標に沿った言葉で説明する。 20 | 21 | ADRにおける優れた「結果」セクションの特徴： 22 | 23 | * 意思決定の結果として何が起こるかを説明します。これには、影響、成果、アウトプット、フォローアップなどが含まれます。 24 | 25 | * 後続のADRに関する情報も含めます。1つのADRが、より大きな包括的な選択を行い、それがさらにより小さな意思決定の必要性を生み出すなど、より多くのADRの必要性を引き起こすことは比較的よくあります。 26 | 27 | * 事後レビュープロセスがあれば含めます。チームが1か月後に各ADRをレビューし、ADRの情報と実際の状況を比較することで、学習と成長を図るのが一般的です。 28 | 29 | 新しいADRが以前のADRに代わる場合があります： 30 | 31 | * 以前のADRを置き換える、または無効にするADが作成された場合は、新しいADRを作成する必要があります。 32 | -------------------------------------------------------------------------------- /locales/ko/서류/의사결정-지속가능성-기준/index.md: -------------------------------------------------------------------------------- 1 | # 의사결정 지속가능성 기준 2 | 3 | 4 | 5 | 의사결정 지속가능성을 자세히 정의하기 위해 우리는 다섯 가지 핵심 기준을 도출했습니다. 6 | 7 | ## 전략적 8 | 9 | 의사 결정 과정에서 전략적 결과를 검토하는 사람은 의사 결정의 장기적인 영향(예: 향후 운영 및 유지 관리 노력) 등을 고려해야 합니다. 10 | 11 | ## 측정 및 관리 가능 12 | 13 | 객관적인 기준, 이상적으로는 수치 기준(예: 품질 속성 시나리오 및 워크숍4에 의해 전파됨)에 따라 시간이 지남에 따라 의사결정 결과를 측정하고 평가할 수 있습니다. 세밀한 결정을 모두 포착하는 것은 불가능하므로 설계자는 결정의 세분성을 특정 세부 수준(예: 디자인 클래스 생성)으로 제한해야 합니다. 이는 보다 지속 가능한 의사 결정과 추적성 링크 감소로 이어질 것입니다. 더욱이, 결정 간의 종속성 수를 제한하면 변경 사항의 파급 효과가 줄어듭니다. 14 | 15 | ## 달성 가능하고 현실적 16 | 17 | 문제에 대한 해결책을 맞추는 이론적 근거는 실용적으로 선택되어야 하며 명시적이어야 합니다. 예를 들어, 설계자는 과도한 엔지니어링이나 과소 엔지니어링을 피하기 위해 주의를 기울였다는 것을 나타낼 수 있습니다(즉, "충분히 좋은" 접근 방식을 적용해야 함). 18 | 19 | ## 요구사항에 뿌리를 두고 있음 20 | 21 | 의사결정은 도메인별 아키텍처 경험과 맥락을 바탕으로 이루어져야 합니다. 개발 팀의 현재 기술, 교육 예산 및 프로세스를 포함하여 회사 환경은 물론 프로젝트 요구 사항 및 제약 조건도 고려해야 합니다. 22 | 23 | ## 시대를 초월한 24 | 25 | 결정은 곧 구식이 되지 않을 경험과 지식을 바탕으로 이루어져야 합니다. 예를 들어 건축가는 플랫폼 중립적인 아키텍처 패턴이나 전술을 선택할 수 있습니다. -------------------------------------------------------------------------------- /locales/fr/modèles/modèle-denregistrement-de-décision-pour-le modèle-alexandrin/index.md: -------------------------------------------------------------------------------- 1 | # Modèle d'enregistrement de décision pour le modèle alexandrin 2 | 3 | ## Introduction 4 | 5 | * Prologue (Résumé) 6 | * Discussion (Contexte) 7 | * Solution (Décision) 8 | * Conséquences (Résultats) 9 | 10 | ## Détails ## 11 | 12 | * Prologue (Résumé) 13 | * Déclaration pour résumer : 14 | * Dans le cadre de (cas d'utilisation)
15 | faire face (préoccupation)
16 | nous avons opté pour (option)
17 | atteindre (la qualité)
18 | accepter (inconvénient). 19 | * Discussion (Contexte) 20 | * Explique les forces en jeu (techniques, politiques, sociales, projet). 21 | * Ceci est l'histoire expliquant le problème que nous cherchons à résoudre. 22 | * Solution 23 | * Explique comment la décision résoudra le problème. 24 | * Conséquences 25 | * Explique les résultats de la décision sur le long terme. 26 | * Est-ce que cela a fonctionné, n'a pas fonctionné, a été modifié, mis à niveau, etc. 27 | -------------------------------------------------------------------------------- /locales/en/templates/index.md: -------------------------------------------------------------------------------- 1 | # Decision record templates 2 | 3 | * [Decision record template by Jeff Tyree and Art Akerman](decision-record-template-by-jeff-tyree-and-art-akerman) 4 | * [Decision record template by Michael Nygard](decision-record-template-by-michael-nygard) 5 | * [Decision record template by EdgeX](decision-record-template-by-edgex) 6 | * [Decision record template by arc42](locales/en/templates/decision-record-template-by-arc42/) 7 | * [Decision record template for Alexandrian pattern](decision-record-template-for-alexandrian-pattern) 8 | * [Decision record template for business case](decision-record-template-for-business-case) 9 | * [Decision record template of the MADR Project](decision-record-template-of-the-madr-project) 10 | * [Decision record template using Planguage](decision-record-template-using-planguage) 11 | * [Decision record template by Gareth Morgan](decision-record-template-by-gareth-morgan) 12 | * [Decision record template by GIG Cymru NHS Wales](locales/en/templates/decision-record-template-by-gig-cymru-nhs-wales/) 13 | -------------------------------------------------------------------------------- /locales/ko/서류/좋은-adr-작성을-위한-제안/index.md: -------------------------------------------------------------------------------- 1 | # 좋은 ADR 작성을 위한 제안 2 | 3 | 좋은 ADR의 특징: 4 | 5 | * 근거: 특정 AD를 수행하는 이유를 설명하십시오. 여기에는 컨텍스트(아래 참조), 다양한 잠재적 선택의 장단점, 기능 비교, 비용/이점 논의 등이 포함될 수 있습니다. 6 | 7 | * 구체적: 각 ADR은 여러 개의 AD가 아닌 약 하나의 AD여야 합니다. 8 | 9 | * 타임스탬프: ADR의 각 항목이 기록되는 시기를 식별합니다. 이는 비용, 일정, 확장 등과 같이 시간이 지남에 따라 변경될 수 있는 측면에 특히 중요합니다. 10 | 11 | * 불변: ADR의 기존 정보를 변경하지 마십시오. 대신, 새로운 정보를 추가하여 ADR을 수정하거나 새로운 ADR을 생성하여 ADR을 대체하십시오. 12 | 13 | ADR에서 좋은 "컨텍스트" 섹션의 특징은 다음과 같습니다. 14 | 15 | * 조직의 상황과 비즈니스 우선순위를 설명하세요. 16 | 17 | * 팀의 사회적 및 기술 구성을 기반으로 한 이론적 근거와 고려 사항을 포함합니다. 18 | 19 | * 관련된 장단점을 포함하고 귀하의 필요와 목표에 맞는 용어로 설명하십시오. 20 | 21 | ADR에서 좋은 "결과" 섹션의 특징은 다음과 같습니다. 22 | 23 | * 결정을 내린 후 어떤 결과가 나오는지 설명하세요. 여기에는 효과, 결과, 결과, 후속 조치 등이 포함될 수 있습니다. 24 | 25 | * 후속 ADR에 대한 정보를 포함합니다. 하나의 ADR이 더 많은 ADR의 필요성을 촉발하는 것은 비교적 흔한 일입니다. 예를 들어 하나의 ADR이 중대한 선택을 하여 더 작은 결정이 필요한 경우입니다. 26 | 27 | * 사후 검토 프로세스를 포함합니다. 학습하고 성장하기 위해 팀에서는 한 달 후에 각 ADR을 검토하고 ADR 정보를 실제 사례와 비교하는 것이 일반적입니다. 28 | 29 | 새로운 ADR은 이전 ADR을 대신할 수 있습니다. 30 | 31 | * 이전 ADR을 대체하거나 무효화하는 AD가 생성되면 새로운 ADR을 생성해야 합니다. -------------------------------------------------------------------------------- /locales/cy/nogfennau/beth-yw-cofnod-penderfyniad-pensaernïaeth/index.md: -------------------------------------------------------------------------------- 1 | ## Beth yw cofnod penderfyniad pensaernïaeth? 2 | 3 | Mae Cofnod Penderfyniad Pensaernïaeth ** ** (ADR) yn ddogfen sy'n cyfleu penderfyniad pensaernïol pwysig a wnaed ynghyd â'i gyd -destun a'i ganlyniadau. 4 | 5 | Mae Penderfyniad Pensaernïaeth ** ** (AD) yn ddewis dylunio meddalwedd sy'n mynd i'r afael â gofyniad sylweddol. 6 | 7 | Log Penderfyniad Pensaernïaeth ** ** (ADL) yw'r casgliad o'r holl ADRs a grëwyd ac a gynhelir ar gyfer prosiect (neu sefydliad) penodol. 8 | 9 | Mae gofyniad pensaernïol arwyddocaol ** (ASR) yn ofyniad sy'n cael effaith fesuradwy ar bensaernïaeth system feddalwedd. 10 | 11 | Mae'r rhain i gyd o fewn pwnc ** Rheoli Gwybodaeth Pensaernïaeth ** (AKM). 12 | 13 | Nod y ddogfen hon yw darparu trosolwg cyflym o ADRs, sut i'w creu, a ble i chwilio am ragor o wybodaeth. 14 | 15 | Byrfoddau: 16 | 17 | *** AD **: Penderfyniad Pensaernïaeth 18 | 19 | *** ADL **: log penderfyniad pensaernïaeth 20 | 21 | *** ADR **: cofnod penderfyniad pensaernïaeth 22 | 23 | *** AKM **: Rheoli Gwybodaeth Bensaernïaeth 24 | 25 | *** ASR **: gofyniad pensaernïol arwyddocaol 26 | -------------------------------------------------------------------------------- /locales/en/documents/what-is-an-architecture-decision-record/index.md: -------------------------------------------------------------------------------- 1 | ## What is an architecture decision record? 2 | 3 | An **architecture decision record** (ADR) is a document that captures an important architectural decision made along with its context and consequences. 4 | 5 | An **architecture decision** (AD) is a software design choice that addresses a significant requirement. 6 | 7 | An **architecture decision log** (ADL) is the collection of all ADRs created and maintained for a particular project (or organization). 8 | 9 | An **architecturally-significant requirement** (ASR) is a requirement that has a measurable effect on a software system’s architecture. 10 | 11 | All these are within the topic of **architecture knowledge management** (AKM). 12 | 13 | The goal of this document is to provide a fast overview of ADRs, how to create them, and where to look for more information. 14 | 15 | Abbreviations: 16 | 17 | * **AD**: architecture decision 18 | 19 | * **ADL**: architecture decision log 20 | 21 | * **ADR**: architecture decision record 22 | 23 | * **AKM**: architecture knowledge management 24 | 25 | * **ASR**: architecturally-significant requirement 26 | -------------------------------------------------------------------------------- /locales/ko/서류/adr-사용을-시작하는-방법/index.md: -------------------------------------------------------------------------------- 1 | # ADR 사용을 시작하는 방법 2 | 3 | ADR 사용을 시작하려면 팀원과 이러한 영역에 대해 이야기하세요. 4 | 5 | 결정 식별: 6 | 7 | * AD는 얼마나 긴급하고 중요한가요? 8 | 9 | * 지금 만들어야 합니까, 아니면 더 많은 정보가 알려질 때까지 기다릴 수 있습니까? 10 | 11 | * 개인 및 집단 경험뿐만 아니라 인정된 설계 방법 및 관행도 의사 결정에 도움이 될 수 있습니다. 12 | 13 | * 제품의 할일 목록을 보완하는 의사결정의 할일 목록을 이상적으로 유지하세요. 14 | 15 | 의사결정: 16 | 17 | * 일반적인 의사결정 기술과 소프트웨어 아키텍처 특정 기술(예: 대화 매핑) 모두 다양한 의사결정 기술이 존재합니다. 18 | 19 | * 그룹의사결정은 활발한 연구주제입니다. 20 | 21 | 결정 제정 및 집행: 22 | 23 | * AD는 소프트웨어 설계에 사용됩니다. 따라서 시스템에 자금을 지원하고 개발하고 운영하는 시스템의 이해관계자에게 전달되고 승인되어야 합니다. 24 | 25 | * 구조적으로 분명한 코딩 스타일과 구조적 관심사 및 결정에 초점을 맞춘 코드 검토는 서로 관련된 두 가지 관행입니다. 26 | 27 | * 소프트웨어 진화에서 소프트웨어 시스템을 현대화할 때 AD도 (재)고려되어야 합니다. 28 | 29 | 의사결정 공유(선택사항): 30 | 31 | * 프로젝트 전반에 걸쳐 많은 AD가 반복됩니다. 32 | 33 | * 따라서 과거의 좋은 결정과 나쁜 결정에 대한 경험은 명시적 지식 관리 전략을 사용할 때 재사용 가능한 귀중한 자산이 될 수 있습니다. 34 | 35 | 결정 문서: 36 | 37 | * 의사결정 캡처를 위한 다양한 템플릿과 도구가 존재합니다. 38 | 39 | * 민첩한 커뮤니티를 참조하세요. M. Nygard의 ADR. 40 | 41 | * 전통적인 소프트웨어 엔지니어링 및 아키텍처 설계 프로세스를 참조하세요. IBM UMF와 CapitalOne의 Tyree 및 Akerman이 제안한 테이블 레이아웃. 42 | 43 | 이상: 44 | 45 | * 위 단계는 [건축적 결정](https://en.wikipedia.org/wiki/Architectural_decision)에 대한 Wikipedia 항목에서 채택되었습니다. -------------------------------------------------------------------------------- /locales/cy/templedi/templed-cofnod-penderfyniad-gan-planguage/index.md: -------------------------------------------------------------------------------- 1 | # Templed cofnod penderfyniad gan ddefnyddio Planguage 2 | 3 | Gweler https://www.iaria.org/conferences2012/filesICCGI12/Tutorial%20Specifying%20Effective%20Non-func.pdf 4 | 5 | ## Beth yw Planguage? 6 | 7 | Mae Planguage yn iaith gynllunio sy'n defnyddio'r geiriau allweddol hyn: 8 | 9 | * Tag: Dynodwr unigryw, parhaus 10 | * Gist: Crynodeb byr o'r gofyniad neu'r maes dan sylw 11 | * Gofyniad: Y testun sy'n manylu ar y gofyniad ei hun 12 | * Rhesymeg: Y rhesymu sy'n cyfiawnhau'r gofyniad 13 | * Blaenoriaeth: Datganiad o flaenoriaeth a hawliad ar adnoddau 14 | * Rhanddeiliaid: Partïon yr effeithir arnynt yn sylweddol gan y gofyniad 15 | * Statws: Statws y gofyniad (drafft, wedi'i adolygu, wedi ymrwymo, ac ati) 16 | * Perchennog: Y person sy'n gyfrifol am weithredu'r gofyniad 17 | * Awdur: Y person a ysgrifennodd y gofyniad 18 | * Adolygu: Rhif fersiwn ar gyfer y datganiad 19 | * Dyddiad: Dyddiad y diwygiad diweddaraf 20 | * Tybiaethau: Unrhyw beth a allai achosi problemau os yw'n anwir nawr neu'n hwyrach 21 | * Risgiau: Unrhyw beth a allai achosi camweithio, oedi, neu effeithiau negyddol eraill 22 | * Diffiniedig: Diffiniad o derm (gwell defnyddio geirfa) -------------------------------------------------------------------------------- /locales/en/templates/decision-record-template-using-planguage/index.md: -------------------------------------------------------------------------------- 1 | # Decision record template using Planguage 2 | 3 | See https://www.iaria.org/conferences2012/filesICCGI12/Tutorial%20Specifying%20Effective%20Non-func.pdf 4 | 5 | ## What is Planguage? 6 | 7 | Planguage is a planning language that uses these keywords: 8 | 9 | * Tag: A unique, persistent identifier 10 | * Gist: A brief summary of the requirement or area addressed 11 | * Requirement: The text that details the requirement itself 12 | * Rationale: The reasoning that justifies the requirement 13 | * Priority: A statement of priority and claim on resources 14 | * Stakeholders: Parties materially affected by the requirement 15 | * Status: The status of the requirement (draft, reviewed, committed, etc.) 16 | * Owner: The person responsible for implementing the requirement 17 | * Author: The person that wrote the requirement 18 | * Revision: A version number for the statement 19 | * Date: The date of the most recent revision 20 | * Assumptions: Anything that could cause problems if untrue now or later 21 | * Risks: Anything that could cause malfunction, delay, or other negative impacts 22 | * Defined: The definition of a term (better to use a glossary) 23 | 24 | -------------------------------------------------------------------------------- /locales/fr/documents/quest-ce-quun-dossier-de-décision-darchitecture/index.md: -------------------------------------------------------------------------------- 1 | # Qu'est-ce qu'un dossier de décision d'architecture? 2 | 3 | Un ** dossier de décision d'architecture ** (ADR) est un document qui capture une décision architecturale importante prise avec son contexte et ses conséquences. 4 | 5 | Une ** décision d'architecture ** (AD) est un choix de conception de logiciels qui répond à une exigence importante. 6 | 7 | Un ** Log de décision d'architecture ** (ADL) est la collection de tous les ADR créés et entretenus pour un projet (ou une organisation) particulier. 8 | 9 | Une ** exigence architecturale ** (ASR) est une exigence qui a un effet mesurable sur l'architecture d'un système logiciel. 10 | 11 | Tout cela est dans le sujet de ** Architecture Knowledge Management ** (AKM). 12 | 13 | L'objectif de ce document est de fournir un aperçu rapide des ADR, comment les créer et où chercher plus d'informations. 14 | 15 | Abréviations: 16 | 17 | * ** AD **: Décision d'architecture 18 | 19 | * ** ADL **: Journal de décision d'architecture 20 | 21 | * ** ADR **: Enregistrement de décision d'architecture 22 | 23 | * ** AKM **: Gestion des connaissances en architecture 24 | 25 | * ** ASR **: exigence architecturale significative -------------------------------------------------------------------------------- /locales/ja/ドキュメント/how-to-start-using-adrs/index.md: -------------------------------------------------------------------------------- 1 | # ADR の始め方 2 | 3 | ADR の活用を始めるには、以下の点についてチームメンバーと話し合ってください。 4 | 5 | 意思決定の特定: 6 | 7 | * どの程度ADに緊急性と重要性があるのか 8 | 9 | * 今すぐ行う必要があるか、それとも、詳細が判明するまで待つことができるか 10 | 11 | * 個人および集団の経験。そして広く認められた設計手法やプラクティス。これらは意思決定の特定に役立ちます。 12 | 13 | * 理想を言うと、プロダクトの ToDo リストを補完する、意思決定 ToDo リストを保守できればよいです。 14 | 15 | 意思決定： 16 | 17 | * 意思決定手法には、数多くの手段が存在します。例えば、ダイアログマッピングなど一般的な手法とソフトウェアアーキテクチャ特有の手法の両方があります。 18 | 19 | * グループによる意思決定は活発に研究されています。 20 | 21 | 意思決定の制定と執行： 22 | 23 | * AD はソフトウェア設計で使用されるため、システムの投資者、開発者、運用者などの関係者に伝達され、承認される必要があります。 24 | 25 | * アーキテクチャ的に明確なコーディングスタイルと、アーキテクチャ上の懸念事項と意思決定に焦点を当てたコードレビューは、共に行われるべき実践です。 26 | 27 | * ソフトウェアの大きな変革においてソフトウェアシステムを近代化する際にも、AD は（再）検討する必要があります。 28 | 29 | 意思決定の共有（オプション）： 30 | 31 | * 多くのADはプロジェクト間で繰り返し発生します。 32 | 33 | * したがって、良いものも悪いものも含めた過去の意思決定に関する経験は、明白な知識管理戦略をとる際に、貴重な再利用可能な資産となり得ます。 34 | 35 | 意思決定のドキュメント化： 36 | 37 | * 意思決定を記録するためのテンプレートやツールは数多く存在します。 38 | 39 | * アジャイルコミュニティ（M. NygardのADRなど）を参照してください。 40 | 41 | * 従来のソフトウェアエンジニアリングおよびアーキテクチャ設計プロセス（IBM UMFやCapitalOneのTyreeとAkermanが提案したテーブルレイアウトなど）を参照してください。 42 | 43 | 詳細はこちら： 44 | 45 | * 上記の手順は、Wikipedia の [Architectural Decision（英語記事）](https://en.wikipedia.org/wiki/Architectural_decision) の項目から引用したものです。 46 | -------------------------------------------------------------------------------- /locales/es/documentos/qué-es-un-registro-de-decisión-de-arquitectura/index.md: -------------------------------------------------------------------------------- 1 | ## ¿Qué es un registro de decisión de arquitectura? 2 | 3 | Un registro de decisión de arquitectura ** ** (ADR) es un documento que captura una decisión arquitectónica importante tomada junto con su contexto y consecuencias. 4 | 5 | Una decisión de arquitectura ** ** (AD) es una opción de diseño de software que aborda un requisito significativo. 6 | 7 | Un registro de decisión de arquitectura ** (ADL) es la colección de todos los ADR creados y mantenidos para un proyecto (u organización) en particular. 8 | 9 | Un requisito de ** arquitectónicamente significativo ** (ASR) es un requisito que tiene un efecto medible en la arquitectura de un sistema de software. 10 | 11 | Todos estos están dentro del tema de ** Gestión del conocimiento de la arquitectura ** (AKM). 12 | 13 | El objetivo de este documento es proporcionar una descripción rápida de los ADR, cómo crearlos y dónde buscar más información. 14 | 15 | Abreviaturas: 16 | 17 | *** AD **: Decisión de arquitectura 18 | 19 | *** ADL **: Registro de decisiones de arquitectura 20 | 21 | *** ADR **: Registro de decisión de arquitectura 22 | 23 | *** AKM **: Gestión del conocimiento de la arquitectura 24 | 25 | *** asr **: requisito arquitectúramente significativo 26 | -------------------------------------------------------------------------------- /locales/fr/modèles/modèle-denregistrement-de-décision utilisant-plangage/index.md: -------------------------------------------------------------------------------- 1 | # Modèle d'enregistrement de décision utilisant Plangage 2 | 3 | Voir https://www.iaria.org/conferences2012/filesICCGI12/Tutorial%20Specifying%20Effective%20Non-func.pdf 4 | 5 | ## Qu'est-ce que le Plangage ? 6 | 7 | Plangage est un langage de planification qui utilise ces mots-clés : 8 | 9 | * Tag : un identifiant unique et persistant 10 | * Gist : Un bref résumé de l'exigence ou du domaine abordé 11 | * Exigence : le texte qui détaille l'exigence elle-même 12 | * Justification : le raisonnement qui justifie l'exigence 13 | * Priorité : une déclaration de priorité et une réclamation sur les ressources 14 | * Parties prenantes : parties matériellement affectées par l'exigence 15 | * Statut : le statut de l'exigence (projet, révisé, validé, etc.) 16 | * Propriétaire : la personne responsable de la mise en œuvre de l'exigence 17 | * Auteur : la personne qui a rédigé l'exigence 18 | * Révision : un numéro de version pour la déclaration 19 | * Date : La date de la révision la plus récente 20 | * Hypothèses : tout ce qui pourrait causer des problèmes s'il était faux maintenant ou plus tard 21 | * Risques : tout ce qui pourrait entraîner un dysfonctionnement, un retard ou d'autres impacts négatifs 22 | *Défini : La définition d'un terme (mieux vaut utiliser un glossaire) -------------------------------------------------------------------------------- /locales/zh/文档/how-to-start-using-adrs/index.md: -------------------------------------------------------------------------------- 1 | # 如何开始使用 ADR 2 | 3 | 要开始使用 ADR，请与团队成员讨论以下内容。 4 | 5 | 决策识别： 6 | 7 | * AD 的紧急程度和重要性如何？ 8 | 9 | * 必须现在就做，还是可以等到了解更多信息后再做？ 10 | 11 | * 个人和集体经验以及公认的设计方法和实践都可以帮助做出决策。 12 | 13 | * 理想情况下，应维护一份与产品待办事项清单相对应的决策待办事项清单。 14 | 15 | 做出决策： 16 | 17 | * A number of decision making techniques exists, both general ones and software architecture specific ones, for instance, dialogue mapping. 18 | 19 | * Group decision making is an active research topic. 20 | 21 | 决定的制定和执行： 22 | 23 | * ADs are used in software design; hence they have to be communicated to, and accepted by, the stakeholders of the system that fund, develop, and operate it. 24 | 25 | * Architecturally evident coding styles and code reviews that focus on architectural concerns and decisions are two related practices. 26 | 27 | * ADs also have to be (re-)considered when modernizing a software system in software evolution. 28 | 29 | 决策共享（可选）： 30 | 31 | * Many ADs recur across projects. 32 | 33 | * Hence, experiences with past decisions, both good and bad, can be valuable reusable assets when employing an explicit knowledge management strategy. 34 | 35 | 决策文件： 36 | 37 | * Many templates and tools for decision capturing exist. 38 | 39 | * See agile communities, e.g. M. Nygard's ADRs. 40 | 41 | * See traditional software engineering and architecture design processes, e.g. table layouts suggested by IBM UMF and by Tyree and Akerman from CapitalOne. 42 | 43 | 更多： 44 | 45 | * The steps above are adopted from the Wikipedia entry on [Architectural Decision](https://en.wikipedia.org/wiki/Architectural_decision) 46 | -------------------------------------------------------------------------------- /locales/en/documents/teamwork-advice-for-adrs/index.md: -------------------------------------------------------------------------------- 1 | # Teamwork advice for ADRs 2 | 3 | If you're considering using decision records with your team, then here's some advice that we've learned by working with many teams. 4 | 5 | You have an opportunity to lead your teammates, by talking together about the "why", rather than mandating the "what". For example, decision records are a way for teams to think smarter and communicate better; decision records are not valuable if they're just an after-the-fact forced paperwork requirement. 6 | 7 | Some teams much prefer the name "decisions" over the abbreviation "ADRs". When some teams use the directory name "decisions", then it's as if a light bulb turns on, and the team starts putting more information into the directory, such as vendor decisions, planning decisions, scheduling decisions, etc. All of these kinds of information can use the same template. We hypothesize that people learn faster with words ("decisions") over abbreviations ("ADRs"), and people are more motivated to write work-in-progress docs when the word "record" is removed, and also some developers and some managers dislike the word "architecture". 8 | 9 | In theory, immutability is ideal. In practice, mutability has worked better for our teams. We insert the new info the existing ADR, with a date stamp, and a note that the info arrived after the decision. This kind of approach leads to a "living document" that we all can update. Typical updates are when we get information thanks to new teammates, or new offerings, or real-world results of our usages, or after-the-fact third-party changes such as vendor capabilties, pricing plans, license agreements, etc. 10 | -------------------------------------------------------------------------------- /locales/ja/テンプレート/madrプロジェクトの意思決定記録テンプレート/index.md: -------------------------------------------------------------------------------- 1 | # [解決された問題と解決策の短いタイトル] 2 | 3 | * ステータス: [提案 | 却下 | 承認 | 非推奨 | … | [ADR-0005](0005-example.md) に置き換え]等 4 | * 決定者: [決定に関与した全員をリストアップ] 5 | * 日付: [決定が最後に更新された YYYY-MM-DD] 6 | 7 | 技術的なストーリー: [説明 | チケット/課題の URL] 8 | 9 | ## 背景と問題提起 10 | 11 | [背景と問題提起を、例えば2～3文で自由記述してください。問題を質問形式で明確に表現してもよいでしょう。] 12 | 13 | ## 意思決定推進者 14 | 15 | * [推進者1、例: 力、直面している懸念事項、…] 16 | * [推進者2、例: 力、直面している懸念事項、…] 17 | * … 18 | 19 | ## 検討対象となるオプション 20 | 21 | * [オプション 1] 22 | * [オプション 2] 23 | * [オプション 3] 24 | * … 25 | 26 | ## 意思決定結果 27 | 28 | 選択された選択肢：「[選択肢 1]」。[理由。例：k.o.基準を満たす唯一の選択肢、意思決定要因 | フォースフォースを解決する | … | が最善の結果をもたらす（下記参照）]。 29 | 30 | ### 肯定的な結果 31 | 32 | * [例：品質特性の満足度の向上、フォローアップの意思決定が必要、 …] 33 | * … 34 | 35 | ### 否定的な結果 36 | 37 | * [例：品質特性の低下、フォローアップの意思決定が必要、 …] 38 | * … 39 | 40 | ## オプションの長所と短所 41 | 42 | ### [オプション 1] 43 | 44 | [例 | 説明 | 詳細情報へのポインタ | …] 45 | 46 | * 良い。なぜなら [議論 a] 47 | * 良い。なぜなら [議論 b] 48 | * 悪い。なぜなら [議論 c] 49 | * … 50 | 51 | ### [オプション 2] 52 | 53 | [例 | 説明 | 詳細情報へのポインタ | …] 54 | 55 | * 良い。なぜなら [議論 a] 56 | * 良い。なぜなら [議論 b] 57 | * 悪い。なぜなら [議論 c] 58 | * … 59 | 60 | ### [オプション 3] 61 | 62 | [例 | 説明 | 詳細情報へのポインタ | …] 63 | 64 | * 良い。なぜなら [議論 a] 65 | * 良い。なぜなら [議論 b] 66 | * 悪い。なぜなら [議論 c] 67 | * … 68 | 69 | ## リンク 70 | 71 | * [リンクの種類] [ADR へのリンク] 72 | * … 73 | -------------------------------------------------------------------------------- /locales/ko/템플릿/알렉산드리아 패턴에 대한 결정 기록 템플릿/index.md: -------------------------------------------------------------------------------- 1 | # [해결된 문제 및 솔루션의 짧은 제목] 2 | 3 | * 상태: [제안됨 | 거부됨 | 허용됨 | 더 이상 사용되지 않음 | ... | [ADR-0005](0005-example.md)]로 대체됨 4 | * 결정자: [결정에 관련된 모든 사람을 나열] 5 | * 날짜: [결정이 마지막으로 업데이트된 YYYY-MM-DD] 6 | 7 | 기술 스토리: [설명 | 티켓/발행 URL] 8 | 9 | ## 상황 및 문제 설명 10 | 11 | [문맥과 문제 설명을 예를 들어 2~3개의 문장을 사용하여 자유 형식으로 설명합니다. 질문 형식으로 문제를 명확히 설명할 수도 있습니다.] 12 | 13 | ## 의사결정 동인 14 | 15 | * [드라이버 1, 예를 들어 세력, 우려에 직면, ...] 16 | * [드라이버 2, 예를 들어 세력, 우려에 직면, ...] 17 | * … 18 | 19 | ## 고려되는 옵션 20 | 21 | * [옵션 1] 22 | * [옵션 2] 23 | * [옵션 3] 24 | * … 25 | 26 | ## 결정 결과 27 | 28 | 선택한 옵션: "[옵션 1]", 왜냐하면 [정의. 예를 들어, k.o를 충족하는 유일한 옵션입니다. 기준 결정 동인 | 강제력을 해결하는 | ... | 가장 잘 나옵니다(아래 참조)]. 29 | 30 | ### 긍정적인 결과 31 | 32 | * [예: 품질속성 만족도 향상, 후속결정 필요, …] 33 | * … 34 | 35 | ### 부정적인 결과 36 | 37 | * [예: 품질 특성 저하, 후속 결정 필요, …] 38 | * … 39 | 40 | ## 옵션의 장점과 단점 41 | 42 | ### [옵션 1] 43 | 44 | [예 | 설명 | 자세한 정보에 대한 포인터 | …] 45 | 46 | * 좋아요, 왜냐하면 [인수 a] 47 | * 좋아요, 왜냐하면 [인수 b] 48 | * 나쁘다. 왜냐하면 [인수 c] 49 | * … 50 | 51 | ### [옵션 2] 52 | 53 | [예 | 설명 | 자세한 정보에 대한 포인터 | …] 54 | 55 | * 좋아요, 왜냐하면 [인수 a] 56 | * 좋아요, 왜냐하면 [인수 b] 57 | * 나쁘다. 왜냐하면 [인수 c] 58 | * … 59 | 60 | ### [옵션 3] 61 | 62 | [예 | 설명 | 자세한 정보에 대한 포인터 | …] 63 | 64 | * 좋아요, 왜냐하면 [인수 a] 65 | * 좋아요, 왜냐하면 [인수 b] 66 | * 나쁘다. 왜냐하면 [인수 c] 67 | * … 68 | 69 | ## 링크 70 | 71 | * [링크 유형] [ADR에 링크] 72 | * … -------------------------------------------------------------------------------- /locales/ko/템플릿/madr 프로젝트의 결정 기록 템플릿/index.md: -------------------------------------------------------------------------------- 1 | # [해결된 문제 및 솔루션의 짧은 제목] 2 | 3 | * 상태: [제안됨 | 거부됨 | 허용됨 | 더 이상 사용되지 않음 | ... | [ADR-0005](0005-example.md)]로 대체됨 4 | * 결정자: [결정에 관련된 모든 사람을 나열] 5 | * 날짜: [결정이 마지막으로 업데이트된 YYYY-MM-DD] 6 | 7 | 기술 스토리: [설명 | 티켓/발행 URL] 8 | 9 | ## 상황 및 문제 설명 10 | 11 | [문맥과 문제 설명을 예를 들어 2~3개의 문장을 사용하여 자유 형식으로 설명합니다. 질문 형식으로 문제를 명확히 설명할 수도 있습니다.] 12 | 13 | ## 의사결정 동인 14 | 15 | * [드라이버 1, 예를 들어 세력, 우려에 직면, ...] 16 | * [드라이버 2, 예를 들어 세력, 우려에 직면, ...] 17 | * … 18 | 19 | ## 고려되는 옵션 20 | 21 | * [옵션 1] 22 | * [옵션 2] 23 | * [옵션 3] 24 | * … 25 | 26 | ## 결정 결과 27 | 28 | 선택한 옵션: "[옵션 1]", 왜냐하면 [정의. 예를 들어, k.o를 충족하는 유일한 옵션입니다. 기준 결정 동인 | 강제력을 해결하는 | ... | 가장 잘 나옵니다(아래 참조)]. 29 | 30 | ### 긍정적인 결과 31 | 32 | * [예: 품질속성 만족도 향상, 후속결정 필요, …] 33 | * … 34 | 35 | ### 부정적인 결과 36 | 37 | * [예: 품질 특성 저하, 후속 결정 필요, …] 38 | * … 39 | 40 | ## 옵션의 장점과 단점 41 | 42 | ### [옵션 1] 43 | 44 | [예 | 설명 | 자세한 정보에 대한 포인터 | …] 45 | 46 | * 좋아요, 왜냐하면 [인수 a] 47 | * 좋아요, 왜냐하면 [인수 b] 48 | * 나쁘다. 왜냐하면 [인수 c] 49 | * … 50 | 51 | ### [옵션 2] 52 | 53 | [예 | 설명 | 자세한 정보에 대한 포인터 | …] 54 | 55 | * 좋아요, 왜냐하면 [인수 a] 56 | * 좋아요, 왜냐하면 [인수 b] 57 | * 나쁘다. 왜냐하면 [인수 c] 58 | * … 59 | 60 | ### [옵션 3] 61 | 62 | [예 | 설명 | 자세한 정보에 대한 포인터 | …] 63 | 64 | * 좋아요, 왜냐하면 [인수 a] 65 | * 좋아요, 왜냐하면 [인수 b] 66 | * 나쁘다. 왜냐하면 [인수 c] 67 | * … 68 | 69 | ## 링크 70 | 71 | * [링크 유형] [ADR에 링크] 72 | * … 73 | -------------------------------------------------------------------------------- /locales/en/examples/continuous-integration/index.md: -------------------------------------------------------------------------------- 1 | # Decision Record for continuous integration 2 | 3 | Title: Decision to Implement Continuous Integration 4 | 5 | ## Context 6 | 7 | The company has been experiencing challenges with the development process as a result of manual testing, build processes, and deployments. This has led to frequent delays, errors and inconsistencies in the quality and delivery of the software. 8 | 9 | ## Decision 10 | 11 | To implement continuous integration as a solution to the challenges experienced in the development process. 12 | 13 | ## Rationale 14 | 15 | Continuous integration will automatically build, test and deploy code changes to the delivery environment in a timely and efficient manner. It will enable integration of new features into the codebase without interfering with the stability of the software. Continuous integration will enhance the quality and delivery of the software, reduce the time taken to resolve errors and improve stakeholder satisfaction. 16 | 17 | ## Consequences 18 | 19 | Positive: 20 | 21 | - Improved quality and delivery of software 22 | 23 | - Time and cost savings through automation 24 | 25 | - Enhanced collaboration and integration within the development team 26 | 27 | Negative: 28 | 29 | - Initial costs associated with implementing the technology 30 | 31 | - Upfront investment in people, tools and processes required to implement continuous integration 32 | 33 | - Potential risk of technical difficulties during the implementation. 34 | 35 | ## Conclusion 36 | 37 | The benefits of implementing continuous integration outweigh the costs of investment and the potential risks. Therefore, the decision to implement continuous integration has been approved. 38 | -------------------------------------------------------------------------------- /locales/en/documents/guidelines-to-achieve-sustainable-decisions/index.md: -------------------------------------------------------------------------------- 1 | # Guidelines to Achieve Sustainable Decisions 2 | 3 | 4 | 5 | We learned the following lessons in our work that can serve as guidelines and assessment for achieving sustainable decisions: 6 | 7 | 1. Use a lean/minimalistic approach for the initial decision documentation. 8 | 9 | 2. Prioritize and capture all important decisions that are relevant enough for documenting and understanding the target architecture. 10 | 11 | 3. Detail the particularly important decisions with full-blown templates only after the initial work has been done (that is, when the decision makers are content with the architectural decisions made and confident that these decisions don’t have to be revised any time soon). 12 | 13 | 4. Use the lean/minimalistic versions from step 1 as a short version of documented decisions with the right granularity level to provide an overview of the detailed decisions, as well as for trivial or obvious decisions. 14 | 15 | 5. Wherever possible, use existing architectural knowledge, either from guidance models or from other sources. Review and extend such knowledge and fit it to the context of the specific decision. 16 | 17 | 6. Ensure that traceability links are established between decisions and both requirements and architectural designs/code. 18 | 19 | 7. Provide automated consistency checking to make sure the traceability links are in sync after a change. Limit the number of dependencies between decisions and other software artifacts. 20 | 21 | 8. Apply the guidelines for the justifications consequently and forcefully—they’re the most important part of the decision documentation because they give the rationale. 22 | -------------------------------------------------------------------------------- /locales/fr/documents/lignes-directrices-pour-atteindre-des-décisions-durables/index.md: -------------------------------------------------------------------------------- 1 | # Lignes directrices pour atteindre des décisions durables 2 | 3 | 4 | 5 | Nous avons appris les leçons suivantes dans notre travail qui peuvent servir de directives et d'évaluation pour obtenir des décisions durables: 6 | 7 | 1. Utilisez une approche maigre / minimaliste pour la documentation de décision initiale. 8 | 9 | 2. Prioriser et capturer toutes les décisions importantes qui sont suffisamment pertinentes pour documenter et comprendre l'architecture cible. 10 | 11 | 3. Détaillez les décisions particulièrement importantes avec des modèles à part ). 12 | 13 | 4. Utilisez les versions maigres / minimalistes de l'étape 1 comme une version courte des décisions documentées avec le bon niveau de granularité pour fournir un aperçu des décisions détaillées, ainsi que pour les décisions triviales ou évidentes. 14 | 15 | 5. Dans la mesure du possible, utilisez des connaissances architecturales existantes, soit à partir de modèles de guidage, soit à partir d'autres sources. Examiner et étendre ces connaissances et l'ajuster au contexte de la décision spécifique. 16 | 17 | 6. Assurez-vous que les liens de traçabilité sont établis entre les décisions et les exigences et les conceptions / code architecturaux. 18 | 19 | 7. Fournissez la vérification de la cohérence automatisée pour vous assurer que les liens de traçabilité sont synchronisés après un changement. Limitez le nombre de dépendances entre les décisions et d'autres artefacts logiciels. 20 | 21 | 8 Appliquez les directives pour les justifications par conséquent et avec force - ils sont la partie la plus importante de la documentation de décision car elles donnent la justification. -------------------------------------------------------------------------------- /locales/ja/テンプレート/EdgeX Foundryによる意思決定記録テンプレート/index.md: -------------------------------------------------------------------------------- 1 | # アーキテクチャ決定記録 (ADR) テンプレート 2 | 3 | これは EdgeX FoundryのADRのテンプレートです。 4 | 5 | テンプレート元: https://docs.edgexfoundry.org/2.3/design/adr/template/ 6 | 7 | 8 | ### 編集者 9 | 10 | ADR編集者を列挙します。 11 | 12 | 形式: 13 | 14 | - 氏名（組織名） 15 | 16 | 17 | ## 変更記録 18 | 19 | ドキュメントの変更内容を、状態、日付、PRのURLを含めて列挙します。 20 | 21 | 状態は、保留中、承認済み、修正済み、非推奨のいずれかです。 22 | 23 | 日付は ISO 8601 (YYYY-MM-DD) 形式の文字列です。 24 | 25 | PRは変更を送信したプルリクエストで、差分、コントリビューター、レビュアーなどの情報が含まれます。 26 | 27 | 形式: 28 | 29 | - \[ADR のステータス (承認済み、修正済みなど)\]\(プルリクエストのURL\) YYYY-MM-DD 30 | 31 | 32 | ## 参照ユースケース 33 | 34 | 関連するユースケース/要件ドキュメントをすべて列挙してください。 35 | 36 | ADRには、少なくとも1つの関連する承認済みユースケースが必要です。 37 | 38 | 形式: 39 | 40 | - \[ユースケース名\]\(URL\) 41 | 42 | ADRがユースケースのすべての要件に対応していない場合は、説明を追加してください。 43 | 44 | ## 背景 45 | 46 | 説明: 47 | 48 | - そのデザインがアーキテクチャ的に重要である理由 - ADR の必要性（単純な問題解決と PR ではなく） 49 | 50 | - 高レベルの設計アプローチ（詳細は以下の提案設計に記載） 51 | 52 | 53 | ## 提案設計 54 | 55 | 設計の詳細（可能な限り実装には触れない） 56 | 57 | 概要： 58 | 59 | - 影響を受ける（変更される）サービス／モジュール 60 | 61 | - 追加される新規サービス／モジュール 62 | 63 | - モデルおよびDTOへの影響（変更／追加／削除） 64 | 65 | - APIへの影響（変更／追加／削除） 66 | 67 | - 一般的な構成への影響​​（新規セクションの設定、変更／追加／削除） 68 | 69 | - DevOpsへの影響 70 | 71 | 72 | ## 考慮事項 73 | 74 | ADRの議論において生じた代替案、懸念事項、付随的または関連する問題、疑問点を文書化してください。 75 | 76 | それらが解決または緩和されたかどうか、またどのように緩和されたかを記載してください。 77 | 78 | 79 | ## 決定事項 80 | 81 | 合意された重要な実装の詳細、注意事項、将来的な検討事項、残存または延期された設計上の課題を文書化します。 82 | 83 | 提案された設計で満たされていない要件があれば、それを文書化します。 84 | 85 | 86 | ## その他の関連 ADR 87 | 88 | 機能のサブコンポーネントの設計上の決定、この設計の結果として非推奨となった設計など、関連する ADR をすべてリストします。 89 | 90 | 形式: 91 | 92 | - \[ADRタイトル\]\(URL\) - 関連性 93 | 94 | ## 参考文献 95 | 96 | 追加の参考文献を列挙してください。 97 | 98 | 形式: 99 | 100 | - \[タイトル\]\(URL\) 101 | -------------------------------------------------------------------------------- /locales/cy/nogfennau/cyngor-gwaith-tîm-ar-gyfer-adrs/index.md: -------------------------------------------------------------------------------- 1 | # Cyngor gwaith tîm ar gyfer ADRs 2 | 3 | Os ydych chi'n ystyried defnyddio cofnodion penderfyniadau gyda'ch tîm, yna dyma ychydig o gyngor rydyn ni wedi'i ddysgu trwy weithio gyda llawer o dimau. 4 | 5 | Mae gennych gyfle i arwain eich cyd -chwaraewyr, trwy siarad gyda'i gilydd am y "pam", yn hytrach na gorfodi'r "beth". Er enghraifft, mae cofnodion penderfyniadau yn ffordd i dimau feddwl yn ddoethach a chyfathrebu'n well; Nid yw cofnodion penderfyniadau yn werthfawr os mai dim ond gofyniad gwaith papur gorfodol ar ôl y ffaith ydyn nhw. 6 | 7 | Mae'n well gan rai timau'r enw "penderfyniadau" dros y talfyriad "ADRS". Pan fydd rhai timau'n defnyddio'r enw cyfeiriadur "penderfyniadau", yna mae fel petai bwlb golau yn troi ymlaen, ac mae'r tîm yn dechrau rhoi mwy o wybodaeth yn y cyfeiriadur, megis penderfyniadau gwerthwr, penderfyniadau cynllunio, penderfyniadau amserlennu, ac ati. Mae'r holl fathau hyn o Gall gwybodaeth ddefnyddio'r un templed. Rydym yn damcaniaethu bod pobl yn dysgu'n gyflymach gyda geiriau ("penderfyniadau") dros fyrfoddau ("ADRs"), ac mae pobl yn fwy cymhelliant i ysgrifennu docs gwaith ar y gweill pan fydd y gair "record" yn cael ei dynnu, a hefyd rhai datblygwyr a rhai rheolwyr Ddim yn hoffi'r gair "pensaernïaeth". 8 | 9 | Mewn theori, mae anfarwoldeb yn ddelfrydol. Yn ymarferol, mae treiglad wedi gweithio'n well i'n timau. Rydym yn mewnosod y wybodaeth newydd yr ADR presennol, gyda stamp dyddiad, a nodyn bod y wybodaeth wedi cyrraedd ar ôl y penderfyniad. Mae'r math hwn o ddull yn arwain at "ddogfen fyw" y gallwn ni i gyd ei diweddaru. Diweddariadau nodweddiadol yw pan gawn wybodaeth diolch i gyd-chwaraewyr newydd, neu offrymau newydd, neu ganlyniadau'r byd go iawn o'n defnyddiau, neu newidiadau trydydd parti ar ôl y ffaith fel capabilties gwerthwyr, cynlluniau prisio, cytundebau trwydded, ac ati. -------------------------------------------------------------------------------- /locales/cy/nogfennau/canllawiau-i-gyflawni-penderfyniadau-cynaliadwy/index.md: -------------------------------------------------------------------------------- 1 | # Canllawiau i gyflawni penderfyniadau cynaliadwy 2 | 3 | 4 | 5 | Fe wnaethon ni ddysgu'r gwersi canlynol yn ein gwaith a all wasanaethu fel canllawiau ac asesiad ar gyfer cyflawni penderfyniadau cynaliadwy: 6 | 7 | 1. Defnyddiwch ddull main/minimalaidd ar gyfer y ddogfennaeth penderfyniad cychwynnol. 8 | 9 | 2. Blaenoriaethu a dal yr holl benderfyniadau pwysig sy'n ddigon perthnasol ar gyfer dogfennu a deall y bensaernïaeth darged. 10 | 11 | 3. Manylion y penderfyniadau arbennig o bwysig gyda thempledi wedi'u chwythu'n llawn dim ond ar ôl i'r gwaith cychwynnol gael ei wneud (hynny yw, pan fydd y rhai sy'n gwneud penderfyniadau yn fodlon â'r penderfyniadau pensaernïol a wnaed ac yn hyderus nad oes rhaid i'r penderfyniadau hyn gael eu hadolygu ar unrhyw adeg yn fuan ). 12 | 13 | 4. Defnyddiwch y fersiynau heb lawer o fraster/minimalaidd o Gam 1 fel fersiwn fer o benderfyniadau wedi'u dogfennu gyda'r lefel gronynnedd gywir i ddarparu trosolwg o'r penderfyniadau manwl, yn ogystal ag ar gyfer penderfyniadau dibwys neu amlwg. 14 | 15 | 5. Lle bynnag y bo hynny'n bosibl, defnyddiwch wybodaeth bensaernïol bresennol, naill ai o fodelau canllaw neu o ffynonellau eraill. Adolygu ac ymestyn gwybodaeth o'r fath a'i ffitio i gyd -destun y penderfyniad penodol. 16 | 17 | 6. Sicrhewch fod cysylltiadau olrhain yn cael eu sefydlu rhwng penderfyniadau a gofynion a dyluniadau/cod pensaernïol. 18 | 19 | 7. Darparu gwirio cysondeb awtomataidd i sicrhau bod y cysylltiadau olrhain mewn sync ar ôl newid. Cyfyngu ar nifer y dibyniaethau rhwng penderfyniadau ac arteffactau meddalwedd eraill. 20 | 21 | 8 Cymhwyso'r canllawiau ar gyfer y cyfiawnhad o ganlyniad ac yn rymus - dyna ran bwysicaf y ddogfennaeth benderfynu oherwydd eu bod yn rhoi'r rhesymeg. -------------------------------------------------------------------------------- /locales/en/documents/decision-sustainability-criteria/index.md: -------------------------------------------------------------------------------- 1 | # Decision Sustainability Criteria 2 | 3 | 4 | 5 | To define decision sustainability in detail, we derived five key criteria. 6 | 7 | ## Strategic 8 | 9 | During decision making, someone looking at strategic consequences should consider things such as the decisions’ long-term impact—for example, future operations and maintenance effort. 10 | 11 | ## Measurable and Manageable 12 | 13 | You can measure and evaluate a decision’s outcome over time according to objective criteria, ideally numeric ones (as, for instance, propagated by quality attribute scenarios and workshops4). Capturing all fine-grained decisions isn’t possible, so architects must limit the decisions’ granularity to a certain level of detail (such as creating a design class). This will lead to a more sustainable set of decisions and fewer traceability links. Moreover, limiting the number of dependencies between decisions reduces changes’ ripple effect. 14 | 15 | ## Achievable and Realistic 16 | 17 | The rationale for fitting the solution to the problem should be chosen pragmatically and made explicit. For example, architects can indicate that they have taken care to avoid over- or underengineering (that is, they should apply the “good enough” approach). 18 | 19 | ## Rooted in Requirements 20 | 21 | Decision making should be grounded in domain-specific architecting experience and context. It should take into account the company environment as well as project requirements and constraints, including the development team’s current skills, training budget, and process. 22 | 23 | ## Timeless 24 | 25 | Decisions should be based on experience and knowledge that won’t likely be soon outdated. For example, architects can choose platform-neutral architectural patterns or tactics. 26 | -------------------------------------------------------------------------------- /locales/en/examples/index.md: -------------------------------------------------------------------------------- 1 | # Decision record examples 2 | 3 | * [CSS framework](css-framework) 4 | 5 | * [Environment variable configuration](environment-variable-configuration) 6 | 7 | * [Metrics, monitors, alerts](metrics-monitors-alerts) 8 | 9 | * [Microsoft Azure DevOps](microsoft-azure-devops) 10 | 11 | * [Monorepo vs multirepo](monorepo-vs-multirepo) 12 | 13 | * [Programming languages](programming-languages) 14 | 15 | * [Secrets storage](secrets-storage) 16 | 17 | * [snake_case v. camelCase for a REST API](snake-case-v-camelcase-for-a-rest-api) 18 | 19 | * [Timestamp format](timestamp-format) 20 | 21 | ChatGPT examples: 22 | 23 | * [API using JSON v. gRPC](api-using-json-v-grpc) 24 | 25 | * [Choosing a database technology](choosing-a-database-technology) 26 | 27 | Specific programming languages: 28 | 29 | * [Go programming language](go-programming-language) 30 | 31 | * [Rust programming language](rust-programming-language) 32 | 33 | * [Java programming language](java-programming-language) 34 | 35 | * [Python programming language](python-programming-language) 36 | 37 | Specific databases: 38 | 39 | * [MySQL database](mysql-database) 40 | 41 | * [PostgreSQL database](postgresql-database) 42 | 43 | Specific container orchestration: 44 | 45 | * [Docker Swarm container orchestration](docker-swarm-container-orchestration) 46 | 47 | * [Kubernetes container orchestration](kubernetes-container-orchestration) 48 | 49 | Specific web frameworks, libraries, and styles: 50 | 51 | * [React front end JavaScript library](react-front-end-javascript-library) 52 | 53 | * [Ruby on Rails framework](ruby-on-rails-framework) 54 | 55 | * [Svelte front end JavaScript library](svelte-front-end-javascript-library) 56 | 57 | * [SvelteKit framework](sveltekit-framework) 58 | 59 | * [Tailwind CSS](tailwind-css) 60 | 61 | * [Vue front end JavaScript library](vue-front-end-javascript-library) -------------------------------------------------------------------------------- /locales/en/documents/suggestions-for-writing-good-adrs/index.md: -------------------------------------------------------------------------------- 1 | ## Suggestions for writing good ADRs 2 | 3 | Characteristics of a good ADR: 4 | 5 | * Rationale: Explain the reasons for doing the particular AD. This can include the context (see below), pros and cons of various potential choices, feature comparions, cost/benefit discussions, and more. 6 | 7 | * Specific: Each ADR should be about one AD, not multiple ADs. 8 | 9 | * Timestamps: Identify when each item in the ADR is written. This is especially important for aspects that may change over time, such as costs, schedules, scaling, and the like. 10 | 11 | * Immutable: Don't alter existing information in an ADR. Instead, amend the ADR by adding new information, or supersede the ADR by creating a new ADR. 12 | 13 | Characteristics of a good "Context" section in an ADR: 14 | 15 | * Explain your organization's situation and business priorities. 16 | 17 | * Include rationale and considerations based on social and skills makeups of your teams. 18 | 19 | * Include pros and cons that are relevant, and describe them in terms that align with your needs and goals. 20 | 21 | Characteristics of good "Consequences" section in an ADR: 22 | 23 | * Explain what follows from making the decision. This can include the effects, outcomes, outputs, follow ups, and more. 24 | 25 | * Include information about any subsequent ADRs. It's relatively common for one ADR to trigger the need for more ADRs, such as when one ADR makes a big overarching choice, which in turn creates needs for more smaller decisions. 26 | 27 | * Include any after-action review processes. It's typical for teams to review each ADR one month later, to compare the ADR information with what's happened in actual practice, in order to learn and grow. 28 | 29 | A new ADR may take the place of a previous ADR: 30 | 31 | * When an AD is made that replaces or invalidates a previous ADR, then a new ADR should be created 32 | -------------------------------------------------------------------------------- /locales/ko/템플릿/결정 기록 템플릿별 edgex/index.md: -------------------------------------------------------------------------------- 1 | # 아키텍처 결정 기록(ADR) 템플릿 2 | 3 | EdgeX Foundry의 ADR 템플릿입니다. 4 | 5 | 출처: https://docs.edgexfoundry.org/2.3/design/adr/template/ 6 | 7 | 8 | ### 제출자 9 | 10 | ADR 제출자를 나열합니다. 11 | 12 | 형식: 13 | 14 | - 이름 (조직) 15 | 16 | 17 | ## 변경 로그 18 | 19 | 다음을 포함하여 문서의 변경 사항을 나열합니다. 상태, 날짜 및 PR URL. 20 | 21 | 상태는 다음 중 하나입니다: 보류 중(pending), 승인됨(approved), 수정됨(amended), 더 이상 사용되지 않음(deprecated) 22 | 23 | 날짜는 ISO 8601(YYYY-MM-DD) 문자열입니다. 24 | 25 | PR은 차이점(diff), 기여자, 검토자와 같은 정보를 포함하여 변경 사항을 제출한 풀 리퀘스트입니다. 26 | 27 | 형식: 28 | 29 | - \[ADR 상태(예: approved, amended 등\]\(풀 리퀘스트 URL\) YYYY-MM-DD 30 | 31 | 32 | ## 참조된 사용 사례 33 | 34 | 관련된 모든 사용 사례/요구 사항 문서를 나열합니다. 35 | 36 | ADR에는 관련 있고 승인된 사용 사례가 적어도 하나 이상 필요합니다. 37 | 38 | 형식: 39 | 40 | - \[사용 사례 이름\]\(URL\) 41 | 42 | ADR이 사용 사례의 모든 요구 사항을 해결하지 못하는 경우 설명을 추가합니다. 43 | 44 | 45 | ## 문맥 46 | 47 | 다음을 설명해야 합니다: 48 | 49 | - 설계가 구조적으로(architecturally) 얼마나, (간단한 이슈나 문제 해결을 위한 PR과 다르게) ADR을 해야할만큼, 중요한지 50 | 51 | - 높은 수준의 설계 접근 방식(자세한 내용은 아래 설계 제안에 설명되어 있음) 52 | 53 | 54 | ## 설계 제안 55 | 56 | 설계 세부 사항(가능한 경우 구현하지 않음) 57 | 58 | 개요: 59 | 60 | - 영향을 받을(또는 변경될) 서비스/모듈 61 | 62 | - 추가될 새로운 서비스/모듈 63 | 64 | - 모델 및 DTO 영향(변경/추가/제거) 65 | 66 | - API 영향(변경/추가/제거) 67 | 68 | - 일반적인 구성 영향(새 섹션 설정, 변경/추가/제거) 69 | 70 | - 데브옵스 영향 71 | 72 | 73 | ## 고려사항 74 | 75 | ADR 토론에서 나온 대안, 우려 사항, 부수적이거나 관련한 이슈, 질문을 문서화합니다. 76 | 77 | 해결 또는 완화되었는지 여부/방법을 표시합니다. 78 | 79 | 80 | ## 결정 81 | 82 | 합의된 중요한 구현 세부 사항, 주의 사항, 향후 고려 사항, 남아 있거나 연기된 설계 이슈를 문서화합니다. 83 | 84 | 설계 제안을 충족하지 않는 부분의 요구사항을 문서화합니다. 85 | 86 | 87 | ## 기타 관련 ADR 88 | 89 | 기능 하위 요소에 대한 설계 결정, 이 설계의 결과로 더 이상 사용되지 않는 설계 등과 같은 관련 ADR을 나열합니다. 90 | 91 | 형식: 92 | 93 | - \[ADR 제목\]\(URL\) - 관련성 94 | 95 | 96 | ## 참고자료 97 | 98 | 추가 참고문헌을 나열합니다. 99 | 100 | 형식: 101 | 102 | - \[제목\]\(URL\) 103 | -------------------------------------------------------------------------------- /locales/en/examples/kubernetes-container-orchestration/index.md: -------------------------------------------------------------------------------- 1 | # Architecture Decision Record: Kubernetes container orchestration 2 | 3 | ## Problem Statement 4 | 5 | We need to select a container orchestration platform for our growing cloud-native application portfolio. Our current legacy platform deployment is too slow, and not agile enough to keep up with our growing needs. We’re looking for a system that will allow us to scale our services in the most efficient way possible without compromising on agility or ease of use. 6 | 7 | ## Considered Alternatives 8 | 9 | 1. Docker Swarm 10 | 11 | 2. Kubernetes 12 | 13 | 3. Apache Mesos 14 | 15 | ## Decision Made 16 | 17 | After conducting a thorough analysis of each container orchestration platform, we have decided to adopt Kubernetes as the best option for our enterprise needs. Our reasons for choosing Kubernetes are as follows: 18 | 19 | 1. **Scalability:** Kubernetes’s unique design is perfect for scaling applications, and as our requirements for scalability evolve over time, Kubernetes has the built-in ability to meet these changes without any issues. 20 | 21 | 2. **Decentralized Architecture:** Kubernetes’ master-worker topology ensures a decentralized architecture which ensures that there is no single point of failure. 22 | 23 | 3. **Community Support:** Kubernetes has the largest and most active open-source community, which means it has a large number of contributors, developers, and vendors making it easier for us to get help and find resources. 24 | 25 | 4. **Ecosystem Support:** Kubernetes has a growing ecosystem with a variety of third-party tools, integrations with container registries, CI/CD pipelines, data storage, and more. 26 | 27 | Therefore, we have decided to adopt Kubernetes as our container orchestration platform for the present and the immediate future. 28 | 29 |
Credit: this page is generated by ChatGPT, then edited for clarity and format.
-------------------------------------------------------------------------------- /locales/es/documentos/consejo-de-trabajo-en-equipo-para-adrs/index.md: -------------------------------------------------------------------------------- 1 | # Consejo de trabajo en equipo para ADRS 2 | 3 | Si está considerando usar registros de decisión con su equipo, aquí hay algunos consejos que hemos aprendido trabajando con muchos equipos. 4 | 5 | Tienes la oportunidad de liderar a tus compañeros de equipo, hablando juntos sobre el "por qué", en lugar de ordenar el "qué". Por ejemplo, los registros de decisión son una forma para que los equipos piensen más inteligente y se comuniquen mejor; Los registros de decisión no son valiosos si son solo un requisito de papeleo forzado después del hecho. 6 | 7 | Algunos equipos prefieren el nombre de "decisiones" sobre la abreviatura "ADR". Cuando algunos equipos usan las "decisiones" del nombre del directorio, entonces es como si se encienda una bombilla, y el equipo comienza a poner más información en el directorio, como decisiones de proveedores, decisiones de planificación, decisiones de programación, etc. La información puede usar la misma plantilla. Presumimos que las personas aprenden más rápido con las palabras ("decisiones") sobre las abreviaturas ("ADR"), y las personas están más motivadas para escribir documentos de trabajo en progreso cuando se elimina la palabra "registro", y también algunos desarrolladores y algunos gerentes No me gusta la palabra "arquitectura". 8 | 9 | En teoría, la inmutabilidad es ideal. En la práctica, la mutabilidad ha funcionado mejor para nuestros equipos. Insertamos la nueva información del ADR existente, con un sello de fecha, y una nota que la información llegó después de la decisión. Este tipo de enfoque lleva a un "documento vivo" que todos podemos actualizar. Las actualizaciones típicas son cuando obtenemos información gracias a nuevos compañeros de equipo, nuevas ofertas, o resultados del mundo real de nuestros usos, o cambios de terceros después de los hechos, como capacidades de proveedores, planes de precios, acuerdos de licencia, etc. 10 | -------------------------------------------------------------------------------- /locales/es/documentos/directrices-para-lograr-decisiones-sostenibles/index.md: -------------------------------------------------------------------------------- 1 | # Directrices para lograr decisiones sostenibles 2 | 3 | 4 | 5 | Aprendimos las siguientes lecciones en nuestro trabajo que pueden servir como directrices y evaluación para lograr decisiones sostenibles: 6 | 7 | 1. Use un enfoque Lean/Minimalista para la documentación de decisión inicial. 8 | 9 | 2. Priorice y capture todas las decisiones importantes que sean lo suficientemente relevantes como para documentar y comprender la arquitectura objetivo. 10 | 11 | 3. Detalle las decisiones particularmente importantes con plantillas en toda regla solo después de que se haya realizado el trabajo inicial (es decir, cuando los tomadores de decisiones se contentan con las decisiones arquitectónicas tomadas y confían en que estas decisiones no tienen que revisarse pronto ). 12 | 13 | 4. Use las versiones Lean/Minimalista del Paso 1 como una versión corta de las decisiones documentadas con el nivel de granularidad correcto para proporcionar una visión general de las decisiones detalladas, así como para decisiones triviales o obvias. 14 | 15 | 5. Siempre que sea posible, use el conocimiento arquitectónico existente, ya sea a partir de modelos de orientación o de otras fuentes. Revise y extienda dicho conocimiento y lo ajuste al contexto de la decisión específica. 16 | 17 | 6. Asegúrese de que se establezcan enlaces de trazabilidad entre las decisiones y los requisitos y los diseños/código arquitectónico. 18 | 19 | 7. Proporcione una verificación de consistencia automatizada para asegurarse de que los enlaces de trazabilidad estén sincronizados después de un cambio. Limite el número de dependencias entre decisiones y otros artefactos de software. 20 | 21 | 8 Aplicar las pautas para las justificaciones consecuentemente y con fuerza: son la parte más importante de la documentación de decisión porque dan la justificación. -------------------------------------------------------------------------------- /locales/cy/nogfennau/meini-prawf-cynaliadwyedd-penderfynu/index.md: -------------------------------------------------------------------------------- 1 | # Meini Prawf Cynaliadwyedd Penderfynu 2 | 3 | 4 | 5 | Er mwyn diffinio cynaliadwyedd penderfyniadau yn fanwl, gwnaethom ddeillio pum maen prawf allweddol. 6 | 7 | ## Strategol 8 | 9 | Wrth wneud penderfyniadau, dylai rhywun sy’n edrych ar ganlyniadau strategol ystyried pethau fel effaith hirdymor y penderfyniadau ’-er enghraifft, gweithrediadau yn y dyfodol ac ymdrech cynnal a chadw. 10 | 11 | ## Mesuradwy ac yn hylaw 12 | 13 | Gallwch fesur a gwerthuso canlyniad penderfyniad dros amser yn unol â meini prawf gwrthrychol, yn ddelfrydol rhai rhifol (fel, er enghraifft, wedi'u lluosogi gan senarios priodoledd ansawdd a gweithdai4). Nid yw dal yr holl benderfyniadau graen mân yn bosibl, felly rhaid i benseiri gyfyngu gronynnedd y penderfyniadau i lefel benodol o fanylion (megis creu dosbarth dylunio). Bydd hyn yn arwain at set fwy cynaliadwy o benderfyniadau a llai o gysylltiadau olrhain. Ar ben hynny, mae cyfyngu ar nifer y dibyniaethau rhwng penderfyniadau yn lleihau effaith cryfhau newidiadau. 14 | 15 | ## Cyflawnadwy a realistig 16 | 17 | Dylai'r rhesymeg dros ffitio'r ateb i'r broblem gael ei ddewis yn bragmatig a'i wneud yn eglur. Er enghraifft, gall penseiri nodi eu bod wedi cymryd gofal i osgoi gor-beiriannu neu danseilio (hynny yw, dylent gymhwyso'r dull “digon da”). 18 | 19 | ## wedi'i wreiddio mewn gofynion 20 | 21 | Dylai gwneud penderfyniadau gael ei seilio ar brofiad pensaernïaeth a chyd-destun pensaernïaeth parth-benodol. Dylai ystyried amgylchedd y cwmni yn ogystal â gofynion a chyfyngiadau prosiect, gan gynnwys sgiliau cyfredol y tîm datblygu, cyllideb hyfforddi a phroses. 22 | 23 | ## Amserol 24 | 25 | Dylai penderfyniadau fod yn seiliedig ar brofiad a gwybodaeth nad ydynt yn debygol o fod wedi dyddio cyn bo hir. Er enghraifft, gall penseiri ddewis patrymau neu dactegau pensaernïol niwtral platfform. -------------------------------------------------------------------------------- /locales/cy/nogfennau/awgrymiadau-ar-gyfer-ysgrifennu-adrs-da/index.md: -------------------------------------------------------------------------------- 1 | ## Awgrymiadau ar gyfer ysgrifennu ADRs da 2 | 3 | Nodweddion ADR da: 4 | 5 | * Rhesymeg: Esboniwch y rhesymau dros wneud yr hysbyseb benodol. Gall hyn gynnwys cyd -destun (gweler isod), manteision ac anfanteision amrywiol ddewisiadau posib, cymhariadau nodwedd, trafodaethau cost/budd, a mwy. 6 | 7 | * Penodol: Dylai pob ADR fod tua un hysbyseb, nid hysbysebion lluosog. 8 | 9 | * Timestamps: Nodwch pryd mae pob eitem yn yr ADR wedi'i hysgrifennu. Mae hyn yn arbennig o bwysig ar gyfer agweddau a allai newid dros amser, megis costau, amserlenni, graddio, ac ati. 10 | 11 | * Na ellir ei symud: Peidiwch â newid y wybodaeth bresennol mewn ADR. Yn lle hynny, diwygiwch yr ADR trwy ychwanegu gwybodaeth newydd, neu ddisodli'r ADR trwy greu ADR newydd. 12 | 13 | Nodweddion adran "cyd -destun" dda mewn ADR: 14 | 15 | * Esboniwch sefyllfa a blaenoriaethau busnes eich sefydliad. 16 | 17 | * Cynhwyswch resymeg ac ystyriaethau yn seiliedig ar golurion cymdeithasol a sgiliau eich timau. 18 | 19 | * Cynhwyswch fanteision ac anfanteision sy'n berthnasol, a'u disgrifio mewn termau sy'n cyd -fynd â'ch anghenion a'ch nodau. 20 | 21 | Nodweddion adran "Canlyniadau" da mewn ADR: 22 | 23 | * Esboniwch beth sy'n dilyn o wneud y penderfyniad. Gall hyn gynnwys yr effeithiau, canlyniadau, allbynnau, gwaith dilynol, a mwy. 24 | 25 | * Cynhwyswch wybodaeth am unrhyw ADRs dilynol. Mae'n gymharol gyffredin i un ADR sbarduno'r angen am fwy o ADRs, megis pan fydd un ADR yn gwneud dewis trosfwaol mawr, sydd yn ei dro yn creu anghenion am benderfyniadau mwy llai. 26 | 27 | * Cynhwyswch unrhyw brosesau adolygu ar ôl gweithredu. Mae'n nodweddiadol i dimau adolygu pob ADR fis yn ddiweddarach, i gymharu'r wybodaeth ADR â'r hyn sydd wedi digwydd mewn ymarfer gwirioneddol, er mwyn dysgu a thyfu. 28 | 29 | Gall ADR newydd gymryd lle ADR blaenorol: 30 | 31 | * Pan wneir hysbyseb sy'n disodli neu'n annilysu ADR blaenorol, yna dylid creu ADR newydd -------------------------------------------------------------------------------- /locales/en/documents/how-to-start-using-adrs/index.md: -------------------------------------------------------------------------------- 1 | # How to start using ADRs 2 | 3 | To start using ADRs, talk with your teammates about these areas. 4 | 5 | Decision identification: 6 | 7 | * How urgent and how important is the AD? 8 | 9 | * Does it have to be made now, or can it wait until more is known? 10 | 11 | * Both personal and collective experience, as well as recognized design methods and practices, can assist with decision identification. 12 | 13 | * Ideally maintain a decision todo list that complements the product todo list. 14 | 15 | Decision making: 16 | 17 | * A number of decision making techniques exists, both general ones and software architecture specific ones, for instance, dialogue mapping. 18 | 19 | * Group decision making is an active research topic. 20 | 21 | Decision enactment and enforcement: 22 | 23 | * ADs are used in software design; hence they have to be communicated to, and accepted by, the stakeholders of the system that fund, develop, and operate it. 24 | 25 | * Architecturally evident coding styles and code reviews that focus on architectural concerns and decisions are two related practices. 26 | 27 | * ADs also have to be (re-)considered when modernizing a software system in software evolution. 28 | 29 | Decision sharing (optional): 30 | 31 | * Many ADs recur across projects. 32 | 33 | * Hence, experiences with past decisions, both good and bad, can be valuable reusable assets when employing an explicit knowledge management strategy. 34 | 35 | Decision documentation: 36 | 37 | * Many templates and tools for decision capturing exist. 38 | 39 | * See agile communities, e.g. M. Nygard's ADRs. 40 | 41 | * See traditional software engineering and architecture design processes, e.g. table layouts suggested by IBM UMF and by Tyree and Akerman from CapitalOne. 42 | 43 | For more: 44 | 45 | * The steps above are adopted from the Wikipedia entry on [Architectural Decision](https://en.wikipedia.org/wiki/Architectural_decision) 46 | 47 | -------------------------------------------------------------------------------- /locales/en/examples/agile-software-development/index.md: -------------------------------------------------------------------------------- 1 | # Decision record for agile software development 2 | 3 | Title Introduction of Agile Software Development 4 | 5 | Date: [Insert Date] 6 | 7 | Team Members Present: [Insert Names] 8 | 9 | ## Background 10 | 11 | The Team has been considering the adoption of Agile software development methodology to increase productivity, improve efficiency, and better adapt to the rapidly changing software development industry. 12 | 13 | Key Points: 14 | 15 | - Agile emphasizes iterative development, frequent communication, and flexibility in requirements 16 | 17 | - Agile can lead to better collaboration among team members 18 | 19 | - Agile can help anticipate and respond to changes in project scope and requirements 20 | 21 | - Agile can lead to improved time-to-market and better overall project outcomes 22 | 23 | ## Decision 24 | 25 | After much deliberation and discussion, the Team has decided to adopt Agile software development methodology. 26 | 27 | ## Reasoning 28 | 29 | We believe that Agile will help us better adapt to the rapidly changing software development industry and help us deliver high-quality products to our customers. Our decision to adopt Agile was based on an assessment of our current workflow, discussions with industry experts, and our long-term organizational goals. 30 | 31 | ## Action Items 32 | 33 | - Assess team member familiarity with Agile methodology and provide necessary training and resources as required 34 | 35 | - Develop and communicate Agile-based project management processes and workflows 36 | 37 | - Establish key performance indicators (KPIs) to track the effectiveness of the Agile methodology 38 | 39 | - Monitor progress towards KPIs to evaluate the effectiveness of the new Agile methodology 40 | 41 | ## Conclusion 42 | 43 | The adoption of Agile software development methodology is an important decision for our team. We believe that our transition to Agile will help us deliver better products efficiently and effectively. 44 | -------------------------------------------------------------------------------- /locales/fr/documents/conseils-de-travail-déquipe-pour-les-adr/index.md: -------------------------------------------------------------------------------- 1 | # Conseils de travail d'équipe pour les ADR 2 | 3 | Si vous envisagez d'utiliser des dossiers de décision avec votre équipe, voici quelques conseils que nous avons appris en travaillant avec de nombreuses équipes. 4 | 5 | Vous avez l'occasion de diriger vos coéquipiers, en parlant ensemble du "pourquoi", plutôt que d'imposer le "quoi". Par exemple, les dossiers de décision sont un moyen pour les équipes de penser plus intelligemment et de mieux communiquer; Les dossiers de décision ne sont pas précieux s'ils ne sont qu'une exigence de paperasse forcée après le fruits. 6 | 7 | Certaines équipes préfèrent de loin le nom des "décisions" à l'abréviation "ADRS". Lorsque certaines équipes utilisent le nom du répertoire "décisions", alors c'est comme si une ampoule s'allume, et que l'équipe commence à mettre plus d'informations dans le répertoire, telles que les décisions des fournisseurs, les décisions de planification, les décisions de planification, etc. Tous ces types de Les informations peuvent utiliser le même modèle. Nous émettons l'hypothèse que les gens apprennent plus rapidement avec les mots ("décisions") sur les abréviations ("ADR"), et les gens sont plus motivés pour rédiger des documents de travail lorsque le mot "enregistrement" est supprimé, ainsi que certains développeurs et certains gestionnaires déteste le mot «architecture». 8 | 9 | En théorie, l'immuabilité est idéale. Dans la pratique, la mutabilité a mieux fonctionné pour nos équipes. Nous insérons les nouvelles informations de l'ADR existante, avec un tampon de date et une note que les informations sont arrivées après la décision. Ce type d'approche mène à un "document de vie" que nous pouvons tous mettre à jour. Les mises à jour typiques sont lorsque nous obtenons des informations grâce aux nouveaux coéquipiers, ou à de nouvelles offres, ou aux résultats réels de nos usages, ou des modifications de tiers après le fait telles que les capabilties des fournisseurs, les plans de prix, les accords de licence, etc. -------------------------------------------------------------------------------- /locales/es/documentos/criterios-de-sostenibilidad-de-decisión/index.md: -------------------------------------------------------------------------------- 1 | # Criterios de sostenibilidad de decisión 2 | 3 | 4 | 5 | Para definir la sostenibilidad de la decisión en detalle, derivamos cinco criterios clave. 6 | 7 | ## estratégico 8 | 9 | Durante la toma de decisiones, alguien que analice las consecuencias estratégicas debe considerar cosas como el impacto a largo plazo de las decisiones, por ejemplo, operaciones futuras y esfuerzos de mantenimiento. 10 | 11 | ## Medible y manejable 12 | 13 | Puede medir y evaluar el resultado de una decisión a lo largo del tiempo de acuerdo con los criterios objetivos, idealmente numéricos (como, por ejemplo, propagados por escenarios de atributos de calidad y talleres4). La captura de todas las decisiones de grano fino no es posible, por lo que los arquitectos deben limitar la granularidad de las decisiones a un cierto nivel de detalle (como crear una clase de diseño). Esto conducirá a un conjunto de decisiones más sostenible y menos enlaces de trazabilidad. Además, limitar el número de dependencias entre las decisiones reduce el efecto de dominio de los cambios. 14 | 15 | ## alcanzable y realista 16 | 17 | La justificación para ajustar la solución al problema debe elegirse pragmáticamente y hacerse explícito. Por ejemplo, los arquitectos pueden indicar que han tenido cuidado de evitar la sobrenadería o subenvenimiento (es decir, deben aplicar el enfoque "lo suficientemente bueno"). 18 | 19 | ## arraigado en requisitos 20 | 21 | La toma de decisiones debe basarse en la experiencia y el contexto de arquitectura específica del dominio. Debe tener en cuenta el entorno de la empresa, así como los requisitos y limitaciones del proyecto, incluidas las habilidades actuales, el presupuesto de capacitación y el proceso del equipo de desarrollo. 22 | 23 | ## atemporal 24 | 25 | Las decisiones deben basarse en la experiencia y el conocimiento que probablemente no estarán anticuados pronto. Por ejemplo, los arquitectos pueden elegir patrones de arquitectura neutrales de plataforma o tácticas. -------------------------------------------------------------------------------- /locales/es/documentos/sugerencias-para-escribir-buenos-adr/index.md: -------------------------------------------------------------------------------- 1 | ## Sugerencias para escribir buenos ADR 2 | 3 | Características de un buen ADR: 4 | 5 | * Justificación: explique las razones para hacer el anuncio particular. Esto puede incluir el contexto (ver más abajo), pros y contras de varias opciones potenciales, comparaciones de características, discusiones de costos/beneficios y más. 6 | 7 | * Específico: cada ADR debe ser aproximadamente un anuncio, no múltiples anuncios. 8 | 9 | * Marcas de tiempo: identifique cuándo se escribe cada elemento en el ADR. Esto es especialmente importante para aspectos que pueden cambiar con el tiempo, como costos, horarios, escala y similares. 10 | 11 | * Inmutable: no altere la información existente en un ADR. En su lugar, modifique el ADR agregando nueva información o reemplazar el ADR creando un nuevo ADR. 12 | 13 | Características de una buena sección de "contexto" en un ADR: 14 | 15 | * Explique la situación y las prioridades comerciales de su organización. 16 | 17 | * Incluya justificación y consideraciones basadas en maquilladores sociales y de habilidades de sus equipos. 18 | 19 | * Incluya pros y contras que sean relevantes, y descrita en términos que se alineen con sus necesidades y objetivos. 20 | 21 | Características de las buenas "consecuencias" en un ADR: 22 | 23 | * Explique qué sigue al tomar la decisión. Esto puede incluir los efectos, los resultados, los resultados, los seguimientos y más. 24 | 25 | * Incluya información sobre cualquier ADR posterior. Es relativamente común que un ADR active la necesidad de más ADR, como cuando un ADR hace una gran opción general, lo que a su vez crea necesidades para decisiones más pequeñas. 26 | 27 | * Incluya cualquier proceso de revisión posterior a la acción. Es típico que los equipos revisen cada ADR un mes después, comparar la información de ADR con lo que sucedió en la práctica real, para aprender y crecer. 28 | 29 | Un nuevo ADR puede tomar el lugar de un ADR anterior: 30 | 31 | * Cuando se realiza un anuncio que reemplaza o invalida un ADR anterior, entonces se debe crear un nuevo ADR -------------------------------------------------------------------------------- /locales/en/examples/api-using-json-v-grpc/index.md: -------------------------------------------------------------------------------- 1 | # Architecture Decision Record: API using JSON v. gRPC 2 | 3 | ## Status 4 | 5 | Accepted 6 | 7 | ## Context 8 | 9 | We are designing an API for a new service that will be used by multiple clients. We have been considering two options for implementing the API: using JSON over HTTP or using gRPC. 10 | 11 | JSON over HTTP is a widely-used approach for building APIs, and it is supported by many programming languages and frameworks. This approach is simple, lightweight, and easy to understand, making it a good choice for many projects. However, it can be less efficient than other options, especially when it comes to handling large amounts of data. 12 | 13 | gRPC, on the other hand, is a newer technology that offers a more efficient way of building APIs. It uses binary serialization to transfer data, which can be faster and more compact than using JSON. gRPC also supports bidirectional streaming, making it a good choice for real-time applications. 14 | 15 | ## Decision 16 | 17 | After considering the pros and cons of both options, we have decided to use gRPC for our API. Although JSON over HTTP is a simpler option, we believe that gRPC will provide a more efficient and scalable solution for our service. We also anticipate that our API will handle a large amount of data, and gRPC's binary serialization will be more efficient for this use case. 18 | 19 | In addition, we believe that gRPC's support for bidirectional streaming will be beneficial for real-time applications that we may develop in the future. 20 | 21 | ## Consequences 22 | 23 | By choosing gRPC, we will need to use a different set of tools and libraries to build our API compared to using JSON over HTTP. This may require additional time and effort to learn and implement these technologies. Additionally, clients who want to use our API will need to use gRPC-compatible libraries, which may not be as widely supported as JSON over HTTP libraries. 24 | 25 | However, we believe that the benefits of using gRPC outweigh these potential drawbacks, and we are confident that this decision will result in a more efficient and scalable API. -------------------------------------------------------------------------------- /locales/cy/nogfennau/sut-i-ddechrau-defnyddio-adrs/index.md: -------------------------------------------------------------------------------- 1 | # Sut i ddechrau defnyddio ADRs 2 | 3 | I ddechrau defnyddio ADRs, siaradwch â'ch cyd -chwaraewyr am yr ardaloedd hyn. 4 | 5 | Adnabod Penderfyniadau: 6 | 7 | * Pa mor frys a pha mor bwysig yw'r hysbyseb? 8 | 9 | * A oes rhaid ei wneud nawr, neu a all aros nes bod mwy yn hysbys? 10 | 11 | * Gall profiad personol a chyfunol, yn ogystal â dulliau ac arferion dylunio cydnabyddedig, gynorthwyo gydag adnabod penderfyniadau. 12 | 13 | * Yn ddelfrydol, cadw rhestr todo penderfyniad sy'n ategu'r rhestr TODO cynnyrch. 14 | 15 | Gwneud penderfyniadau: 16 | 17 | * Mae nifer o dechnegau gwneud penderfyniadau yn bodoli, mae rhai cyffredinol a phensaernïaeth meddalwedd yn benodol i rai, er enghraifft, mapio deialog. 18 | 19 | * Mae gwneud penderfyniadau grŵp yn bwnc ymchwil gweithredol. 20 | 21 | Deddfu a gorfodi penderfyniadau: 22 | 23 | * Defnyddir hysbysebion wrth ddylunio meddalwedd; Felly mae'n rhaid eu cyfleu i randdeiliaid y system sy'n cronni, datblygu a gweithredu gan, a derbyn. 24 | 25 | * Mae arddulliau codio amlwg yn bensaernïol ac adolygiadau cod sy'n canolbwyntio ar bryderon pensaernïol a phenderfyniadau yn ddau arfer cysylltiedig. 26 | 27 | * Rhaid ystyried hysbysebion hefyd (ail-) wrth foderneiddio system feddalwedd yn esblygiad meddalwedd. 28 | 29 | Rhannu Penderfyniadau (dewisol): 30 | 31 | * Mae llawer o hysbysebion yn digwydd eto ar draws prosiectau. 32 | 33 | * Felly, gall profiadau â phenderfyniadau yn y gorffennol, da a drwg, fod yn asedau gwerthfawr y gellir eu hailddefnyddio wrth ddefnyddio strategaeth rheoli gwybodaeth benodol. 34 | 35 | Dogfennaeth Penderfyniad: 36 | 37 | * Mae llawer o dempledi ac offer ar gyfer dal penderfyniadau yn bodoli. 38 | 39 | * Gweler cymunedau ystwyth, e.e. ADRs M. Nygard. 40 | 41 | * Gweler Prosesau Peirianneg Meddalwedd a Phensaernïaeth Traddodiadol, e.e. Cynlluniau bwrdd a awgrymwyd gan IBM UMF a chan Tyree ac Akerman o Capitalone. 42 | 43 | Am fwy: 44 | 45 | * Mabwysiadir y camau uchod o'r cofnod Wikipedia ar [penderfyniad pensaernïol] (https://en.wikipedia.org/wiki/Architectural_Decision) -------------------------------------------------------------------------------- /locales/en/examples/high-trust-teamwork/index.md: -------------------------------------------------------------------------------- 1 | # Decision Record for High Trust Teamwork 2 | 3 | Date: [Insert Date] 4 | 5 | Participants: [Insert Names of Participants] 6 | 7 | Decision Reach: [Unanimous/ Majority decision/ Individual Decision] 8 | 9 | ## Decision Description 10 | 11 | The decision to adopt High Trust Teamwork as a core value and belief in our team and organizational culture. 12 | 13 | ## Alternatives Considered 14 | 15 | We considered alternative approaches to teamwork, including low trust or no trust teamwork, as well as other frameworks such as cognitive diversity teams, centralized decision-making teams, and agile teams. 16 | 17 | ## Benefits and Risks 18 | 19 | The benefits of high trust teamwork include improved collaboration, better decision-making, increased motivation and engagement, higher job satisfaction and retention rates, and enhanced innovation and creativity. The risks associated with high trust teamwork include the potential for trust breaches, conflicts, and misunderstandings due to miscommunications or not adhering to the high trust principles. 20 | 21 | ## Decision Outcome 22 | 23 | It was unanimously agreed upon to adopt high trust teamwork as the core value and belief in our team and organizational culture. We acknowledged the importance of building and maintaining trust through transparency, honesty, integrity, and respect, and recognized that this approach would help us to establish a positive and rewarding work environment. 24 | 25 | ## Action Items 26 | 27 | To implement high trust teamwork, we will take the following steps: 28 | 29 | 1. Define high trust principles and practices and communicate these to all team members 30 | 31 | 2. Establish regular feedback mechanisms and communication channels to keep the team updated on progress, challenges, and opportunities 32 | 33 | 3. Attend training on high trust teamwork and actively participate in team-building activities 34 | 35 | 4. Encourage and recognize behaviors that demonstrate high trust principles in action 36 | 37 | 5. Develop a plan to address potential trust breaches, conflicts, or misunderstandings and have a process to handle such situations effectively 38 | -------------------------------------------------------------------------------- /locales/fr/documents/critères-de-durabilité-de-décision/index.md: -------------------------------------------------------------------------------- 1 | # Critères de durabilité de décision 2 | 3 | 4 | 5 | Pour définir la durabilité de la décision en détail, nous avons dérivé cinq critères clés. 6 | 7 | ## stratégique 8 | 9 | Pendant la prise de décision, une personne qui examine les conséquences stratégiques devrait considérer des choses telles que l'impact à long terme des décisions - par exemple, les opérations futures et les efforts de maintenance. 10 | 11 | ## mesurable et gérable 12 | 13 | Vous pouvez mesurer et évaluer le résultat d'une décision au fil du temps en fonction des critères objectifs, idéalement numériques (comme, par exemple, propagés par des scénarios d'attribut de qualité et des ateliers4). La capture de toutes les décisions à grain fin n'est pas possible, donc les architectes doivent limiter la granularité des décisions à un certain niveau de détail (comme la création d'une classe de conception). Cela conduira à un ensemble plus durable de décisions et à moins de liens de traçabilité. De plus, la limitation du nombre de dépendances entre les décisions réduit l'effet d'entraînement des changements. 14 | 15 | ## réalisable et réaliste 16 | 17 | La justification de l'ajustement de la solution au problème doit être choisie de manière pragmatique et rendue explicite. Par exemple, les architectes peuvent indiquer qu'ils ont pris soin d'éviter la sur-intention ou la sous-intention (c'est-à-dire qu'ils devraient appliquer l'approche «assez bonne»). 18 | 19 | ## Enraciné dans les exigences 20 | 21 | La prise de décision doit être fondée sur l'expérience architectée et le contexte architectives spécifiques au domaine. Il devrait prendre en compte l'environnement de l'entreprise ainsi que les exigences et les contraintes du projet, y compris les compétences actuelles de l'équipe de développement, le budget de formation et le processus. 22 | 23 | ## Intemporel 24 | 25 | Les décisions devraient être basées sur l'expérience et les connaissances qui ne seront probablement pas bientôt dépassées. Par exemple, les architectes peuvent choisir des modèles architecturaux ou des tactiques architecturaux neutres. -------------------------------------------------------------------------------- /locales/fr/documents/suggestions-pour-écrire-de-bonnes-adr/index.md: -------------------------------------------------------------------------------- 1 | # Suggestions pour écrire de bonnes ADR 2 | 3 | Caractéristiques d'un bon ADR: 4 | 5 | * Justification: Expliquez les raisons de faire l'annonce particulière. Cela peut inclure le contexte (voir ci-dessous), les avantages et les inconvénients de divers choix potentiels, les comparations de fonctionnalités, les discussions sur les coûts / avantages, etc. 6 | 7 | * Spécifique: chaque ADR doit être environ une annonce, pas plusieurs annonces. 8 | 9 | * Timestaps: Identifiez quand chaque élément de l'ADR est écrit. Ceci est particulièrement important pour les aspects qui peuvent changer avec le temps, tels que les coûts, les horaires, la mise à l'échelle, etc. 10 | 11 | * Immutable: ne modifiez pas les informations existantes dans un ADR. Au lieu de cela, modifiez l'ADR en ajoutant de nouvelles informations ou remplacez l'ADR en créant un nouvel ADR. 12 | 13 | Caractéristiques d'une bonne section "contexte" dans une ADR: 14 | 15 | * Expliquez la situation et les priorités commerciales de votre organisation. 16 | 17 | * Incluez la justification et les considérations basées sur les maquillage social et de compétences de vos équipes. 18 | 19 | * Incluez les avantages et les inconvénients qui sont pertinents et décrivez-les en termes qui correspondent à vos besoins et à vos objectifs. 20 | 21 | Caractéristiques de la bonne section "conséquences" dans une ADR: 22 | 23 | * Expliquez ce qui suit de prendre la décision. Cela peut inclure les effets, les résultats, les sorties, les suivis, etc. 24 | 25 | * Inclure des informations sur les ADR ultérieurs. Il est relativement courant pour un ADR de déclencher le besoin de plus de ADR, comme lorsqu'un ADR fait un grand choix global, ce qui crée à son tour des besoins pour des décisions plus petites. 26 | 27 | * Inclure tout processus d'examen après action. Il est typique pour les équipes d'examiner chaque ADR un mois plus tard, de comparer les informations ADR avec ce qui s'est passé dans la pratique réelle, afin d'apprendre et de grandir. 28 | 29 | Un nouvel ADR peut remplacer un ADR précédent: 30 | 31 | * Lorsqu'une annonce est faite qui remplace ou invalide un ADR précédent, alors un nouvel ADR doit être créé -------------------------------------------------------------------------------- /locales/ja/テンプレート/ビジネスケース用意思決定記録テンプレート/index.md: -------------------------------------------------------------------------------- 1 | # ビジネスケース用意思決定記録テンプレート 2 | 3 | このADRテンプレートは、判断基準、候補、コストなど、意思決定に関するビジネスケースの作成に重点を置いています。 4 | 5 | 6 | ## トップレベル 7 | 8 | * 役職 9 | * ステータス 10 | * 評価基準 11 | * 検討すべき候補者 12 | * 各候補者の調査と分析 13 | * 基準を満たしているか満たしていないか、またその理由 14 | * コスト分析 15 | * SWOT分析 16 | * 意見とフィードバック 17 | * 推薦 18 | 19 | 20 | ## ロウレベルの詳細な説明 21 | 22 | **タイトル**: 23 | 24 | * Gitのコミットメッセージのように、50文字未満の短いフレーズ。 25 | 26 | **ステータス**: 27 | 28 | * 提案、承認、拒否、非推奨、置き換えなどのいずれか。 29 | 30 | **評価基準**: 31 | 32 | * 概要: 発見したい内容とその理由を簡潔に説明してください。 33 | 34 | * 詳細 35 | 36 | **検討すべき候補** 37 | 38 | * 要約：候補をどのように発見したかを簡潔に説明し、外れ値があれば注意喚起してください。 39 | 40 | * すべての候補と関連する選択肢をリストアップしてください。潜在的な解決策として何を評価していますか？ 41 | 42 | * 詳細 43 | 44 | **各候補者の調査と分析** 45 | 46 | * 要約：調査方法を簡潔に説明し、パターン、クラスター、外れ値に注目してください。 47 | 48 | * 基準を満たしているか満たしていないか、またその理由を記載してください。 49 | 50 | * 要約 51 | 52 | * 詳細 53 | 54 | * コスト分析 55 | 56 | * 要約 57 | 58 | * 例 59 | 60 | * ライセンス（契約合意や法的義務など） 61 | 62 | * トレーニング（スキルアップや変更管理など） 63 | 64 | * 運用（サポートや保守など） 65 | 66 | * 計測（帯域幅やCPU使用率など） 67 | 68 | * SWOT分析 69 | 70 | * 要約 71 | 72 | * 強み 73 | 74 | * 弱み 75 | 76 | * 機会 77 | 78 | * 脅威 79 | 80 | * 社内の意見とフィードバック 81 | 82 | * 要約 83 | 84 | * 例 85 | 86 | * チームによる（できれば担当者が作成） 87 | 88 | * 他のステークホルダーからの意見 89 | 90 | * 品質特性、すなわち横断機能要件 91 | 92 | * 外部からの意見とフィードバック 93 | 94 | * 要約 95 | 96 | * 意見提供者は誰ですか？ 97 | 98 | * 他に検討した候補は何ですか？ 99 | 100 | * 何を作成していますか？ 101 | 102 | * 例 103 | 104 | * B2B または B2C 105 | 106 | * 社外向けまたは従業員専用 107 | 108 | * デスクトップまたはモバイル 109 | 110 | * パイロット版または本番環境 111 | 112 | * モノリス版またはマイクロサービス版 113 | 114 | * 候補をどのように評価しましたか？ 115 | 116 | * なぜそれを選んだのですか？ 117 | 118 | * その後、どのような変化がありましたか？ 119 | 120 | * 例 121 | 122 | * 選んだもののパフォーマンスはどうですか？ 123 | 124 | * 実際の運用環境におけるユーザートラフィックの何パーセントが選んだものを経由していますか？ 125 | 126 | * 継続的デリバリーパイプライン、コンテンツ管理システム、分析機能、メトリクスなど、どのような統合が行われていますか？ 127 | 128 | * 現在の知見を踏まえて、人々にどのようなアドバイスをしますか？ 129 | 130 | * 逸話 131 | 132 | **推奨事項**: 133 | 134 | * 概要 135 | 136 | * 詳細 137 | -------------------------------------------------------------------------------- /locales/es/documentos/cómo-comenzar-a-usar-adrs/index.md: -------------------------------------------------------------------------------- 1 | # Cómo comenzar a usar ADRS 2 | 3 | Para comenzar a usar ADR, hable con sus compañeros de equipo sobre estas áreas. 4 | 5 | Identificación de decisión: 6 | 7 | * ¿Qué tan urgente y qué tan importante es el anuncio? 8 | 9 | * ¿Tiene que hacerse ahora, o puede esperar hasta que se conozca más? 10 | 11 | * Tanto la experiencia personal como la colectiva, así como los métodos y prácticas de diseño reconocidos, pueden ayudar con la identificación de decisiones. 12 | 13 | * Idealmente, mantenga una lista de decisión que complementa la lista de TODO del producto. 14 | 15 | Toma de decisiones: 16 | 17 | * Existen una serie de técnicas de toma de decisiones, tanto generales como la arquitectura de software específicas, por ejemplo, el mapeo de diálogo. 18 | 19 | * La toma de decisiones grupales es un tema de investigación activo. 20 | 21 | Promulgación de decisiones y aplicación: 22 | 23 | * Los anuncios se utilizan en el diseño de software; Por lo tanto, deben ser comunicados y aceptados por los interesados del sistema que financian, desarrollan y operan. 24 | 25 | * Los estilos de codificación y las revisiones de código arquitectónicamente evidentes que se centran en las preocupaciones y decisiones arquitectónicas son dos prácticas relacionadas. 26 | 27 | * Los anuncios también deben ser (re) considerados al modernizar un sistema de software en la evolución del software. 28 | 29 | Compartir decisiones (opcional): 30 | 31 | * Muchos anuncios se repiten en todos los proyectos. 32 | 33 | * Por lo tanto, las experiencias con decisiones pasadas, tanto buenas como malas, pueden ser activos reutilizables valiosos al emplear una estrategia explícita de gestión del conocimiento. 34 | 35 | Documentación de decisión: 36 | 37 | * Existen muchas plantillas y herramientas para la captura de decisiones. 38 | 39 | * Ver comunidades ágiles, p. M. Nygard's ADRS. 40 | 41 | * Consulte los procesos tradicionales de diseño de ingeniería de software y arquitectura, p. Diseños de mesa sugeridos por IBM UMF y por Tyree y Akerman de CapitalOne. 42 | 43 | Para más: 44 | 45 | * Los pasos anteriores se adoptan de la entrada de Wikipedia en [Decisión arquitectónica] (https://en.wikipedia.org/wiki/architectural_decision) -------------------------------------------------------------------------------- /locales/ko/템플릿/의사결정 기록 템플릿-by-jeff-tyree-and-art-akerman/index.md: -------------------------------------------------------------------------------- 1 | # Jeff Tyree와 Art Akerman의 의사결정 기록 템플릿 2 | 3 | 이것은 ["Architecture Decisions: Demystifying Architecture" by Jeff Tyree 및 Art Akerman, Capital One Financial](https://www.utdallas.edu/~chung/SA/zz-Impreso-architecture_decisions-)에 게시된 아키텍처 결정 설명 템플릿입니다. tyree-05.pdf). 4 | 5 | * **문제**: 현재 이 문제를 해결하는 이유에 대해 질문을 남기지 않고 해결 중인 아키텍처 설계 문제를 설명하세요. 최소한의 접근 방식에 따라 수명 주기의 다양한 지점에서 해결해야 하는 문제만 해결하고 문서화합니다. 6 | 7 | * **결정**: 아키텍처의 방향, 즉 선택한 위치를 명확하게 설명합니다. 8 | 9 | * **상태**: 보류, 결정, 승인 등 결정 상태입니다. 10 | 11 | * **그룹**: 통합, 프레젠테이션, 데이터 등과 같은 간단한 그룹화를 사용하여 일련의 의사결정을 구성하는 데 도움을 줄 수 있습니다. John Kyaruzi 및 Jan van Katwijk의 이벤트, 일정, 위치와 같은 보다 추상적인 범주를 포함하는 보다 정교한 아키텍처 온톨로지를 사용할 수도 있습니다. 예를 들어, 이 온톨로지를 사용하면 시스템이 이벤트 아래에 정보를 요구하는 발생을 처리하는 의사결정을 그룹화할 수 있습니다. 12 | 13 | * **가정**: 결정을 내리는 환경의 기본 가정(비용, 일정, 기술 등)을 명확하게 설명합니다. 환경적 제약(예: 허용되는 기술 표준, 엔터프라이즈 아키텍처, 일반적으로 사용되는 패턴 등)으로 인해 고려하는 대안이 제한될 수 있습니다. 14 | 15 | * **제약사항**: 선택한 대안(결정)이 제기할 수 있는 환경에 대한 추가 제약사항을 캡처합니다. 16 | 17 | * **직위**: 고려한 직위(실행 가능한 옵션 또는 대안)를 나열합니다. 여기에는 긴 설명이 필요한 경우가 많으며 때로는 모델과 다이어그램도 필요합니다. 이것은 완전한 목록이 아닙니다. 하지만 "...에 대해 생각해 보셨나요?"라는 질문은 듣고 싶지 않습니다. 최종 검토 중; 이로 인해 신뢰성이 떨어지고 다른 아키텍처 결정에 대한 의문이 제기됩니다. 이 섹션은 또한 귀하가 다른 사람의 의견을 듣는 데 도움이 됩니다. 다른 의견을 명시적으로 언급하는 것은 귀하의 결정에 그들의 옹호자를 포함시키는 데 도움이 됩니다. 18 | 19 | * **인론**: 구현 비용, 총 소유 비용, 시장 출시 시간, 필요한 개발 리소스 가용성 등의 항목을 포함하여 직위를 선택한 이유를 설명합니다. 이것은 아마도 결정 자체만큼 중요할 것입니다. 20 | 21 | * **의미**: REMAP 메타모델에서 알 수 있듯이 결정에는 많은 의미가 따릅니다. 예를 들어, 결정으로 인해 다른 결정을 내리거나, 새로운 요구 사항을 생성하거나, 기존 요구 사항을 수정해야 할 필요성이 발생할 수 있습니다. 환경에 추가적인 제약을 가합니다. 고객과 범위나 일정을 재협상해야 합니다. 또는 추가 직원 교육이 필요합니다. 결정의 의미를 명확하게 이해하고 기술하는 것은 동의를 얻고 아키텍처 실행을 위한 로드맵을 만드는 데 매우 효과적일 수 있습니다. 22 | 23 | * **관련 결정**: 많은 결정이 관련되어 있다는 것은 분명합니다. 여기에 나열할 수 있습니다. 그러나 실제로는 추적성 매트릭스, 의사결정 트리 또는 메타모델이 더 유용하다는 사실을 발견했습니다. 메타모델은 복잡한 관계를 도식적으로 표시하는 데 유용합니다(예: Rose 모델). 24 | 25 | * **관련 요구 사항**: 의사결정은 비즈니스 중심으로 이루어져야 합니다. 책임을 보여주기 위해 결정을 목표나 요구 사항에 명시적으로 매핑하십시오. 여기에 관련 요구 사항을 열거할 수 있지만 추적성 매트릭스를 참조하는 것이 더 편리하다는 것을 알았습니다. 각 요구 사항 충족에 대한 각 아키텍처 결정의 기여도를 평가한 다음 모든 결정에서 요구 사항이 얼마나 잘 충족되는지 평가할 수 있습니다. 결정이 요구 사항을 충족하는 데 도움이 되지 않으면 해당 결정을 내리지 마세요. 26 | 27 | * **관련 아티팩트**: 이 결정이 영향을 미치는 관련 아키텍처, 디자인 또는 범위 문서를 나열합니다. 28 | 29 | * **관련 원칙**: 기업이 합의한 일련의 원칙을 갖고 있는 경우 결정이 그 중 하나 이상과 일치하는지 확인하십시오. 이는 도메인이나 시스템에 따른 정렬을 보장하는 데 도움이 됩니다. 30 | 31 | * **참고**: 의사 결정 과정은 몇 주가 걸릴 수 있으므로 사회화 과정에서 팀이 논의하는 메모와 문제를 기록하는 것이 유용하다는 것을 알았습니다. 32 | -------------------------------------------------------------------------------- /locales/ko/템플릿/비즈니스 사례에 대한 의사결정 기록 템플릿/index.md: -------------------------------------------------------------------------------- 1 | # 비즈니스 사례에 대한 의사결정 기록 템플릿 2 | 3 | 이 ADR 템플릿은 기준, 옵션(candidates) 및 비용을 포함하여 결정에 대한 비즈니스 사례 생성을 강조합니다. 4 | 5 | 6 | ## 상위 수준 7 | 8 | * 제목 9 | * 상태 10 | * 평가 기준 11 | * 고려해야 할 옵션 12 | * 각 옵션에 대한 조사 및 분석 13 | * 기준을 충족/불만족하며 그 이유 14 | * 비용 분석 15 | * SWOT 분석 16 | * 의견 및 피드백 17 | * 추천 18 | 19 | 20 | ## 하위 수준 상세 내용 21 | 22 | **제목**: 23 | 24 | * Git 커밋 메시지와 같이 50자 미만의 짧은 현재형 명령문입니다. 25 | 26 | **상태**: 27 | 28 | * 제안됨, 수락됨, 거부됨, 더 이상 사용되지 않음, 대체됨 등 중 하나입니다. 29 | 30 | **평가 기준**: 31 | 32 | * 요약: 우리가 발굴하려는 내용과 그 이유를 간략하게 설명합니다. 33 | 34 | * 세부사항 35 | 36 | **고려할 옵션**: 37 | 38 | * 요약: 옵션을 어떻게 발견했는지 간략하게 설명하고 이상값에 주의를 환기시킵니다. 39 | 40 | * 모든 옵션 및 관련 옵션을 나열하십시오. 우리는 잠재적인 해결책으로 무엇을 평가하고 있나요? 41 | 42 | * 세부사항 43 | 44 | **각 옵션에 대한 조사 및 분석**: 45 | 46 | * 요약: 연구 방법을 간략하게 설명하고 패턴, 클러스터 및 이상값에 주목합니다. 47 | 48 | * 기준을 충족/불만족하며 그 이유 49 | 50 | * 요약 51 | 52 | * 세부 사항 53 | 54 | * 비용 분석 55 | 56 | * 요약 57 | 58 | * 예시 59 | 60 | * 계약 동의, 법적 약속 등 라이선스 부여 61 | 62 | * 기술 향상, 변화 관리 등의 교육 63 | 64 | * 지원, 유지보수 등 운영 65 | 66 | * 대역폭, CPU 사용량 등의 측정 67 | 68 | * SWOT 분석 69 | 70 | * 요약 71 | 72 | * 강점 73 | 74 | * 약점 75 | 76 | * 기회 77 | 78 | * 위협 79 | 80 | * 내부 의견 및 피드백 81 | 82 | * 요약 83 | 84 | * 예시 85 | 86 | * 팀 작성, 이상적으로는 실제 사람이 작성함 87 | 88 | * 기타 이해관계자로부터 89 | 90 | * 품질 속성(일명 교차 기능 요구 사항) 91 | 92 | * 외부 의견 및 피드백 93 | 94 | * 요약 95 | 96 | * 의견을 제시하는 사람은 누구입니까? 97 | 98 | * 당신이 고려한 다른 옵션은 무엇입니까? 99 | 100 | * 당신은 무엇을 만들고 있나요? 101 | 102 | * 예시 103 | 104 | * B2B 또는 B2C 105 | 106 | * 외부용 또는 직원 전용 107 | 108 | * 데스크톱 또는 모바일 109 | 110 | * 파일럿 또는 프로덕션 111 | 112 | * 모놀리스 또는 마이크로서비스 113 | 114 | * 옵션들을 어떻게 평가했나요? 115 | 116 | * 우승자를 선택한 이유는 무엇입니까? 117 | 118 | * 그 이후로 무슨 일이 일어나고 있나요? 119 | 120 | * 예시 121 | 122 | * 우승자의 실적은 어떻습니까? 123 | 124 | * 실제 프로덕션 사용자 트래픽의 몇 %가 승자를 통해 전달됩니까? 125 | 126 | * 지속적인 전달 파이프라인, 콘텐츠 관리 시스템, 분석 및 지표 등과 같이 어떤 종류의 통합이 관련되어 있습니까? 127 | 128 | * 당신이 지금 알고 있는 것을 알면서 사람들에게 무엇을 다르게 하라고 조언하시겠습니까? 129 | 130 | * 일화 131 | 132 | **추천**: 133 | 134 | * 요약 135 | 136 | * 세부 사항 137 | -------------------------------------------------------------------------------- /locales/en/examples/postgresql-database/index.md: -------------------------------------------------------------------------------- 1 | # Architecture Decision Record: PostgreSQL database 2 | 3 | Title: Use of PostgreSQL Database 4 | 5 | ## Context 6 | 7 | Our organization is currently evaluating options for the most suitable database management system to be used in our upcoming project. We have narrowed our search down to two options – PostgreSQL and MySQL. After careful consideration, we have decided to use PostgreSQL due to its advanced features and performance capabilities. 8 | 9 | ## Decision 10 | 11 | We will use PostgreSQL as the preferred database management system for our organization's upcoming project. 12 | 13 | ## Justification 14 | 15 | After analyzing and comparing the features of both PostgreSQL and MySQL, we have come to the conclusion that PostgreSQL is the better option because of the following reasons: 16 | 17 | 1. **Advanced features:** PostgreSQL has a wide range of advanced features like JSON support, full-text search, and spatial data management, which are essential for our project. 18 | 19 | 2. **Performance:** PostgreSQL has a proven track record of excellent performance capabilities, which will ensure that our project runs smoothly without any performance issues. 20 | 21 | 3. **Community support:** PostgreSQL has a large and active community that provides regular updates and support, making it easier to resolve any issues that arise during the project development phase. 22 | 23 | 4. **Scalability:** PostgreSQL is highly scalable, and it can handle large amounts of data with ease, which will be essential for our project. 24 | 25 | 5. **Security:** PostgreSQL has a robust security mechanism that will ensure that our project data is secure at all times, and it meets all our organization's security requirements. 26 | 27 | ## Alternatives 28 | 29 | The other option that we considered was MySQL. MySQL is also a highly capable database management system, but it lacks some of the advanced features that PostgreSQL offers, and its performance capacity is not as good as that of PostgreSQL. 30 | 31 | ## Conclusion 32 | 33 | Based on our analysis, we have decided to use PostgreSQL as the preferred database management system for our upcoming project. This decision has been made after careful consideration, and we believe that it will help us achieve our project goals efficiently and effectively. 34 | 35 |
Credit: this page is generated by ChatGPT, then edited for clarity and format.
-------------------------------------------------------------------------------- /locales/fr/documents/comment-commencer-à-utiliser-les-adr/index.md: -------------------------------------------------------------------------------- 1 | # Comment commencer à utiliser les ADR 2 | 3 | Pour commencer à utiliser les ADR, parlez avec vos coéquipiers de ces domaines. 4 | 5 | Identification de la décision: 6 | 7 | * Dans quelle mesure est-il urgent et est important l'annonce? 8 | 9 | * Doit-il être fait maintenant, ou peut-il attendre que plus soit connu? 10 | 11 | * Une expérience personnelle et collective, ainsi que des méthodes et pratiques de conception reconnues, peuvent aider à l'identification des décisions. 12 | 13 | * Idéalement, maintenir une liste de tâches de décision qui complète la liste des tâches du produit. 14 | 15 | Prise de décision: 16 | 17 | * Un certain nombre de techniques de prise de décision existent, à la fois générales et celles spécifiques à l'architecture logicielle, par exemple, la cartographie des dialogues. 18 | 19 | * La prise de décision de groupe est un sujet de recherche actif. 20 | 21 | Décision de décision et application: 22 | 23 | * Les annonces sont utilisées dans la conception de logiciels; Par conséquent, ils doivent être communiqués et acceptés par les parties prenantes du système qui le financent, le développent et l'exploitent. 24 | 25 | * Les styles de codage et les revues de code évidents architecturaux qui se concentrent sur les préoccupations et les décisions architecturales sont deux pratiques connexes. 26 | 27 | * Les annonces doivent également être (ré) considérées lors de la modernisation d'un système logiciel dans l'évolution des logiciels. 28 | 29 | Partage de décision (facultatif): 30 | 31 | * De nombreuses publicités se reproduisent dans les projets. 32 | 33 | * Par conséquent, les expériences avec les décisions passées, bonnes et mauvaises, peuvent être des actifs réutilisables précieux lors de l'utilisation d'une stratégie explicite de gestion des connaissances. 34 | 35 | Documentation de la décision: 36 | 37 | * De nombreux modèles et outils de capture de décision existent. 38 | 39 | * Voir les communautés agiles, par ex. ADRS de M. Nygard. 40 | 41 | * Voir les processus traditionnels d'ingénierie logicielle et de conception d'architecture, par ex. Disposés de table suggérés par IBM UMF et par Tyree et Akerman de Capitalone. 42 | 43 | Pour plus: 44 | 45 | * Les étapes ci-dessus sont adoptées à partir de l'entrée Wikipedia sur [DÉCISION ARCHITECTURAL] (https://en.wikipedia.org/wiki/architectural_decision) -------------------------------------------------------------------------------- /locales/en/examples/sveltekit-framework/index.md: -------------------------------------------------------------------------------- 1 | # Architecture Decision Record: SvelteKit framework 2 | 3 | * Date: [Current Date] 4 | 5 | * Status: [proposed, approved, rejected, deprecated] 6 | 7 | ## Context 8 | 9 | We are building a new web application that requires a scalable and efficient front-end architecture. After conducting a thorough analysis of various front-end frameworks, we have chosen SvelteKit as our preferred framework. 10 | 11 | ## Decision 12 | 13 | We have decided to implement the SvelteKit front-end architecture for our web application. SvelteKit provides an advanced front-end development system that is fast, efficient, and flexible. It can be used for optimizing large and small applications. 14 | 15 | ## Rationale 16 | 17 | SvelteKit is a new and comprehensive front-end solution that offers an array of features such as server-side rendering, hot reloading, simplified configuration, and many more. It enables us to create high-quality front-end architecture that can handle the largest applications with ease. 18 | 19 | SvelteKit's component-based architecture enables us to develop reusable and scalable UI components that can be integrated seamlessly between different projects. The framework offers excellent support for TypeScript, allowing us to create clean and structured code that is easy to maintain. 20 | 21 | In addition, SvelteKit provides an easy-to-use document management system that allows us to track all of our project's architectural decisions and changes. 22 | 23 | ## Alternatives Considered 24 | 25 | We have evaluated several alternatives, such as React, Vue, Angular, and Next.js, but with its features, ease of use, and robustness, SvelteKit was the clear choice for our project. 26 | 27 | ## Consequences 28 | 29 | Implementing SvelteKit front-end architecture will provide enhanced user experience, performance, and flexibility. We can achieve better productivity through the framework’s simpler configurations, component-based architecture, and modularity. As a result, our project can be more efficient and stable. 30 | 31 | ## Conclusion 32 | 33 | We decided to implement the SvelteKit front-end architecture to achieve a modern, scalable, and efficient web application with the features and modularity we need. With its excellent support for TypeScript, server-side rendering, and simplification of configurations, we feel that SvelteKit is the best choice for our project. 34 | 35 |
Credit: this page is generated by ChatGPT, then edited for clarity and format.
-------------------------------------------------------------------------------- /locales/en/examples/vue-front-end-javascript-library/index.md: -------------------------------------------------------------------------------- 1 | # Architecture Decision Record: Vue front-end JavaScript library 2 | 3 | Date: [Date of decision] 4 | 5 | Status: [Draft/Final/Postponed/Cancelled] 6 | 7 | Subject: Architecture Decision Record for Vue front-end JavaScript library 8 | 9 | ## Context 10 | 11 | Our web application requires a front-end JavaScript library to provide dynamic and responsive user interfaces. We have evaluated several popular libraries that include React, Angular, and Vue. Based on the evaluation, we have decided to use the Vue library as the primary front-end library for our web application. 12 | 13 | ## Decision 14 | 15 | We have decided to adopt the Vue front-end JavaScript library based on the following factors: 16 | 17 | 1. **Lightweight:** Vue is a lightweight library that offers functionality similar to that of React and Angular but with a smaller code footprint. 18 | 19 | 2. **Easy to learn:** Vue has a simple and intuitive API that makes it easy to learn and use. 20 | 21 | 3. **Flexibility:** Vue is a flexible library that works well with other libraries or frameworks to provide different functionalities. 22 | 23 | 4. **Performance:** Vue provides excellent performance with fast rendering and minimal overhead. 24 | 25 | 5. **Strong community:** Vue has a growing and strong community that offers support and resources to the users. 26 | 27 | ## Consequences 28 | 29 | The decision to use Vue as the primary front-end JavaScript library will have the following consequences: 30 | 31 | 1. Development and maintenance will be faster and easier because of the simplicity and flexibility of Vue. 32 | 33 | 2. Team members who are new to Vue can easily learn and use it because of its simple and intuitive API. 34 | 35 | 3. Integration with other libraries or frameworks will be easier because of the flexibility of Vue. 36 | 37 | 4. The application will have better performance and responsiveness with faster rendering and minimal overhead. 38 | 39 | 5. The team will have access to a growing and strong community that offers support and resources for Vue. 40 | 41 | ## Conclusion 42 | 43 | Based on the evaluation and the above factors, we have decided to use Vue as the primary front-end JavaScript library for our web application. This decision will provide us with the benefits of simplicity, flexibility, performance, and support from a growing and strong community. 44 | 45 |
Credit: this page is generated by ChatGPT, then edited for clarity and format.
-------------------------------------------------------------------------------- /locales/en/examples/java-programming-language/index.md: -------------------------------------------------------------------------------- 1 | # Architecture Decision Record: Java programming language 2 | 3 | Title: Choosing Java Programming Language for the Project 4 | 5 | Decision: After evaluating multiple programming languages, we have decided to use Java for our project. 6 | 7 | ### Background 8 | 9 | We intended to build a web-based application that could run on multiple operating systems. Our project required a language that could provide strong security features, handle concurrency, support large code bases, and be versatile enough to meet our future growth requirements. We evaluated several languages, considering their strengths and limitations, before deciding on Java. 10 | 11 | ### Considerations 12 | 13 | 1. **Security:** Java provides excellent security features through its well-defined security policies and access control. It also incorporates features like bytecode verification, which helps prevent malicious software from running on a system. 14 | 15 | 2. **Concurrency:** Java has built-in support for multithreading, which allows applications to perform several tasks simultaneously. This feature makes Java an excellent choice for developing large, complex applications with multiple features and functionalities. 16 | 17 | 3. **Large codebases:** Java supports object-oriented programming, which makes it a suitable choice for developing large codebases. Its modular nature and use of encapsulation and abstraction patterns further add to the software development process's ease. 18 | 19 | 4. **Versatility:** Java is versatile and provides the ability to use a wide range of libraries and frameworks, making it an excellent choice for both web-based and enterprise-level applications. 20 | 21 | ### Decision Outcome 22 | 23 | We have decided to use the Java programming language for our project, considering its security features, concurrency support, ability to handle large codebases, and versatility. This decision aligns with our project requirements, and we believe that choosing Java will ensure its success. 24 | 25 | ### Consequences 26 | 27 | 1. We will need developers who have experience with Java and can use it proficiently. 28 | 29 | 2. Any code written in the language must be compatible with the Java Virtual Machine (JVM). 30 | 31 | 3. Incorporating new features, functionalities, or frameworks may present some challenges. 32 | 33 | 4. Large, complex projects in Java may require more time and resources to develop. 34 | 35 |
Credit: this page is generated by ChatGPT, then edited for clarity and format.
-------------------------------------------------------------------------------- /locales/en/examples/ruby-on-rails-framework/index.md: -------------------------------------------------------------------------------- 1 | # Architecture Decision Record: Ruby on Rails Framework 2 | 3 | ## Context 4 | 5 | - The organization is developing a web application with complex business logic and multiple integrations with third-party services. 6 | 7 | - The team has experience in building web applications with Ruby on Rails. 8 | 9 | - There is a need to choose a web framework that promotes rapid development, scalability, and maintainability. 10 | 11 | ## Decision 12 | 13 | - Use Ruby on Rails as the framework for developing the web application. 14 | 15 | ## Justification 16 | 17 | - Ruby on Rails is a mature, stable, and widely adopted web framework that has proven its effectiveness in building complex web applications. 18 | 19 | - The framework follows the Model-View-Controller (MVC) architecture pattern, which promotes separation of concerns and enhances code reusability and maintainability. 20 | 21 | - Rails provides many built-in features, such as ActiveRecord for database interactions and ActionMailer for email management, which can save development time and simplify code. 22 | 23 | - The framework has a large and active community, with many reusable modules and plugins available to enhance functionality and resolve common problems. 24 | 25 | - Ruby on Rails supports Test-Driven Development (TDD) and Behavior-Driven Development (BDD), which enables developers to write automated tests for their code, ensuring that it works as expected and reducing bugs and regressions. 26 | 27 | - Ruby is a high-level language that promotes developer productivity and code readability, and acts as a powerful glue language for integrating with a wide range of third-party services and APIs. 28 | 29 | ## Consequences 30 | 31 | - The team needs to ensure that the web application's architecture and design follow Rails conventions and best practices to maximize the benefits of the framework. 32 | 33 | - Developers need to have a good understanding of the Ruby language and the Rails framework, although the Rails documentation and community can provide guidance and support. 34 | 35 | - There may be a learning curve for developers who are new to Ruby and Rails, although the benefits of the framework can justify the investment in training and onboarding. 36 | 37 | - The team needs to monitor the application's performance and scalability, and may need to fine-tune database queries and optimize caching to handle large amounts of data and traffic. 38 | 39 |
Credit: this page is generated by ChatGPT, then edited for clarity and format.
-------------------------------------------------------------------------------- /locales/en/examples/google-cloud-platform/index.md: -------------------------------------------------------------------------------- 1 | # Architecture Decision Record for Google Cloud Platform 2 | 3 | ## Context 4 | 5 | Google Cloud Platform (GCP) is a prominent cloud computing platform that offers various cloud services, including computing, storage, and networking solutions. This ADR aims to document the architectural decisions made for developing and implementing a GCP-based infrastructure for our organization. 6 | 7 | ## Decision 8 | 9 | Our organization has decided to use Google Cloud Platform as the cloud infrastructure for our application. The primary considerations for this decision are: 10 | 11 | - Cost-effectiveness 12 | 13 | - Scalability 14 | 15 | - Reliability 16 | 17 | - Flexibility 18 | 19 | ## Selections 20 | 21 | The following services from GCP have been selected to meet our requirements: 22 | 23 | - Compute Engine for virtual machines and computing resources 24 | 25 | - Cloud Storage for object storage and file hosting 26 | 27 | - Cloud SQL for managed database service 28 | 29 | - Firebase for app development and hosting 30 | 31 | ## Rationale 32 | 33 | - Cost-Effectiveness: Google Cloud Platform is highly cost-effective compared to other cloud platforms, making it an attractive option for organizations with budget constraints. 34 | 35 | - Scalability: GCP's easy-to-scale infrastructure enables handling any amount of traffic in real-time. 36 | 37 | - Reliability: GCP's managed services offer high reliability, with automated backups and disaster recovery capabilities that ensure high availability of resources and data. 38 | 39 | - Flexibility: The platform provides various tools and services across different domains such as AI, data analytics, and IoT, making it highly versatile. 40 | 41 | ## Consequences 42 | 43 | Migrating to Google Cloud Platform will require training our teams on GCP services, re-architecting the application to be compatible with the selected services, and updating the infrastructure code to support GCP services. However, it is expected that once the migration is completed, we will have a highly scalable, reliable, and cost-effective infrastructure for hosting our application. Also, we will need to manage the ongoing costs of provisioning resources on GCP. 44 | 45 | ## Conclusion 46 | 47 | Google Cloud Platform is an excellent choice for our cloud infrastructure due to its cost-effectiveness, scalability, reliability, and flexibility. By utilizing the selected services, we can provide a highly available and robust infrastructure for our application. 48 | -------------------------------------------------------------------------------- /locales/ja/テンプレート/Jeff TyreeとArt Akermanによる意思決定記録テンプレート/index.md: -------------------------------------------------------------------------------- 1 | # Jeff TyreeとArt Akermanによる意思決定記録テンプレート 2 | 3 | これは、[Capital One FinancialのJeff TyreeとArt Akerman著『Architecture Decisions: Demystifying Architecture』](https://www.utdallas.edu/~chung/SA/zz-Impreso-architecture_decisions-tyree-05.pdf)に掲載されているアーキテクチャ意思決定記述テンプレートです。 4 | 5 | * **課題**: 取り組んでいるアーキテクチャ設計上の課題について説明し、なぜ今その課題に取り組むのかという疑問を残さないようにしてください。最小限のアプローチに従い、ライフサイクルの様々な段階で対処が必要な課題のみを取り上げ、文書化してください。 6 | 7 | * **決定**: アーキテクチャの方向性、つまり選択した立場を明確に述べてください。 8 | 9 | * **ステータス**: 決定のステータス（保留中、決定済み、承認済みなど） 10 | 11 | * **グループ**: 統合、プレゼンテーション、データといった単純なグループ分けを用いて、一連の意思決定を整理することができます。また、John Kyaruzi氏とJan van Katwijk氏による、イベント、カレンダー、場所といったより抽象的なカテゴリを含む、より洗練されたアーキテクチャ[オントロジー](https://ja.wikipedia.org/wiki/%E3%82%AA%E3%83%B3%E3%83%88%E3%83%AD%E3%82%B8%E3%83%BC_%28%E6%83%85%E5%A0%B1%E7%A7%91%E5%AD%A6%29)を使用することもできます。例えば、このオントロジーを用いて、システムが情報を必要とする事象に対応する意思決定を「イベント」の下にグループ化することができます。 12 | 13 | * **前提**: 意思決定を行う環境における根本的な前提（コスト、スケジュール、テクノロジーなど）を明確に記述します。環境上の制約（一般的なテクノロジー標準、エンタープライズアーキテクチャ、一般的に採用されているパターンなど）によって、検討できる選択肢が制限される可能性があることに注意してください。 14 | 15 | * **制約**: 選択された代替案（決定）が環境にもたらす可能性のある追加の制約をすべて記録します。 16 | 17 | * **立場**: 検討した立場（実行可能な選択肢または代替案）をリストアップします。これらの説明には長い説明が必要になることが多く、モデルや図表が必要になる場合もあります。これは網羅的なリストではありません。しかし、最終レビュー中に「…について検討しましたか？」という質問は避けたいものです。これは信頼性の低下を招き、他のアーキテクチャ上の決定に疑問を投げかけることになります。このセクションは、他者の意見を聞いたことを確認するのにも役立ちます。他者の意見を明示的に述べることで、その支持者をあなたの決定に賛同させることができます。 18 | 19 | * **論拠**: 実装コスト、総所有コスト、市場投入までの時間、必要な開発リソースの可用性など、あるポジションを選択した理由を概説します。これは、おそらく決定自体と同じくらい重要です。 20 | 21 | * **影響**: REMAPメタモデル（注：Representation and Mainte 22 | nance of Process Knowledge）が示すように、決定には多くの影響が伴います。例えば、ある決定によって、別の決定を行う必要性が生じたり、新しい要件を作成したり、既存の要件を変更したり、環境に新たな制約が生じたり、顧客とスコープやスケジュールの再交渉が必要になったり、スタッフの追加トレーニングが必要になったりする可能性があります。決定の影響を明確に理解し、明確に伝えることは、承認を得てアーキテクチャ実行のロードマップを作成する上で非常に効果的です。 23 | 24 | * **関連する決定**: 多くの決定は関連していることは明らかであり、それをここで列挙します。ただし、実際には、トレーサビリティマトリックス、決定木、またはメタモデルの方が有用であることがわかりました。メタモデルは、複雑な関係を図式で示すのに役立ちます（[Rose](https://www.ibm.com/docs/ja/rsm/7.5.0?topic=migration-rational-rose-model)モデルなど）。 25 | 26 | * **関連する要件**: 決定はビジネス主導で行う必要があります。説明責任を示すために、決定を目標または要件に明示的にマッピングします。これらの関連要件をここで列挙することもできますが、私たちの経験上、トレーサビリティマトリックスを参照する方が便利であることがわかりました。各アーキテクチャ決定が各要件の達成にどのように貢献しているかを評価し、さらにすべての決定において要件がどの程度達成されているかを評価できます。ある決定が要件の達成に貢献しない場合は、その決定は行わないでください。 27 | 28 | * **関連成果物**: この決定が影響を与える関連するアーキテクチャ、設計、またはスコープに関するドキュメントの一覧。 29 | 30 | * **関連原則**: 企業内で合意済みの原則がある場合は、決定がそれらの原則の1つ以上と整合していることを確認してください。これにより、ドメインまたはシステム間の整合性を確保できます。 31 | 32 | * **メモ**: 意思決定プロセスには数週間かかる場合があるため、共有化プロセス中にチームが議論したメモや問題点を記録しておくことが有用であることがわかりました。 33 | 34 | -------------------------------------------------------------------------------- /locales/en/templates/decision-record-template-of-the-madr-project/index.md: -------------------------------------------------------------------------------- 1 | # [short title of solved problem and solution] 2 | 3 | * Status: [proposed | rejected | accepted | deprecated | … | superseded by [ADR-0005](0005-example.md)] 4 | * Deciders: [list everyone involved in the decision] 5 | * Date: [YYYY-MM-DD when the decision was last updated] 6 | 7 | Technical Story: [description | ticket/issue URL] 8 | 9 | ## Context and Problem Statement 10 | 11 | [Describe the context and problem statement, e.g., in free form using two to three sentences. You may want to articulate the problem in form of a question.] 12 | 13 | ## Decision Drivers 14 | 15 | * [driver 1, e.g., a force, facing concern, …] 16 | * [driver 2, e.g., a force, facing concern, …] 17 | * … 18 | 19 | ## Considered Options 20 | 21 | * [option 1] 22 | * [option 2] 23 | * [option 3] 24 | * … 25 | 26 | ## Decision Outcome 27 | 28 | Chosen option: "[option 1]", because [justification. e.g., only option, which meets k.o. criterion decision driver | which resolves force force | … | comes out best (see below)]. 29 | 30 | ### Positive Consequences 31 | 32 | * [e.g., improvement of quality attribute satisfaction, follow-up decisions required, …] 33 | * … 34 | 35 | ### Negative Consequences 36 | 37 | * [e.g., compromising quality attribute, follow-up decisions required, …] 38 | * … 39 | 40 | ## Pros and Cons of the Options 41 | 42 | ### [option 1] 43 | 44 | [example | description | pointer to more information | …] 45 | 46 | * Good, because [argument a] 47 | * Good, because [argument b] 48 | * Bad, because [argument c] 49 | * … 50 | 51 | ### [option 2] 52 | 53 | [example | description | pointer to more information | …] 54 | 55 | * Good, because [argument a] 56 | * Good, because [argument b] 57 | * Bad, because [argument c] 58 | * … 59 | 60 | ### [option 3] 61 | 62 | [example | description | pointer to more information | …] 63 | 64 | * Good, because [argument a] 65 | * Good, because [argument b] 66 | * Bad, because [argument c] 67 | * … 68 | 69 | ## Links 70 | 71 | * [Link type] [Link to ADR] 72 | * … 73 | -------------------------------------------------------------------------------- /locales/en/examples/amazon-web-services/index.md: -------------------------------------------------------------------------------- 1 | # Architecture Decision Record for Amazon Web Services 2 | 3 | Title: Adopting Amazon Web Services for Cloud Infrastructure 4 | 5 | ## Decision 6 | 7 | After a thorough evaluation of various cloud infrastructure platforms, it has been decided that Amazon Web Services (AWS) will be adopted by our organization for our cloud infrastructure needs. 8 | 9 | ## Background 10 | 11 | Our organization is growing rapidly and we need a reliable and scalable cloud infrastructure to meet the demands of our business. After considering a number of cloud infrastructure providers, it was concluded that AWS offers the most suitable range of services to meet our current and future requirements. 12 | 13 | ## Considerations 14 | 15 | There are numerous cloud infrastructure providers in the market that have proven to be reliable and efficient. However, AWS not only offers a comprehensive set of services to cater to our needs, but it also has an extensive customer base and a track record of successful deployments. AWS also provides a broad range of support and training resources to ensure that our team can work effectively with the platform. 16 | 17 | Furthermore, AWS has an extensive global presence with data centers located in various regions around the world. This ensures that our data is secure and our applications and services will be highly available. AWS also has a robust security framework that is critical for our business. 18 | 19 | Lastly, AWS provides a pay-as-you-go model which offers us the flexibility to scale our infrastructure based on demand. This means that we will only be charged for what we use, which allows us to optimize our costs and invest in other areas of the business. 20 | 21 | ## Decision 22 | 23 | Based on the evaluations performed and the advantages offered by AWS, it has been decided that AWS will be adopted for our cloud infrastructure needs. 24 | 25 | ## Consequences 26 | 27 | The adoption of AWS may require training for our teams to ensure that they are familiar with the platform and can effectively utilize it. There may also be some initial costs to move our current infrastructure to the AWS platform. 28 | 29 | ## Ownership 30 | 31 | The responsibility for ensuring the effective utilization of AWS and the management of associated risks will fall within the remit of the cloud infrastructure team. Any issues that arise must be addressed by this team. 32 | 33 | ## Review 34 | 35 | The decision to adopt AWS will be reviewed on an annual basis to ensure that it continues to meet our needs and that the benefits of the platform are being fully realized. 36 | --------------------------------------------------------------------------------