Date: DATE Status: status
[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.]
- [driver 1, e.g., a force, facing concern, …]
- [driver 2, e.g., a force, facing concern, …]
- …
- [option 1]
- [option 2]
- [option 3]
- …
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)].
- [e.g., improvement of quality attribute satisfaction, follow-up decisions required, …]
- …
- [e.g., compromising quality attribute, follow-up decisions required, …]
- …
[example | description | pointer to more information | …]
- Good, because [argument a]
- Good, because [argument b]
- Bad, because [argument c]
- …
[example | description | pointer to more information | …]
- Good, because [argument a]
- Good, because [argument b]
- Bad, because [argument c]
- …
[example | description | pointer to more information | …]
- Good, because [argument a]
- Good, because [argument b]
- Bad, because [argument c]
- …
[If relevant / it would help the discussion, please provide code examples here that would help in comparing the various options on the table.
A few possible options for doing this:
- A link to a gist or proof of concept repository
- A separate code block using github code fencing
- If necessary, you can add a new folder within the
docs/decisions
directory titled000X-decision-name-files
and add necessary code files there. Ideally use the same mechanism for storing all files related to a decision - the below examples are meant to show the full set of different options ]
console.log('Hello, World!');
- [Link type](link to adr)
- …