Techstack
TODO
Adjust this pattern to your preferences.
Table of contents
Summary
TODO
| Track the status and outcome of decisions that affect the architecture design. | |
|---|---|
| When to use | - For any architecture decision with major impact on the implementation. - To support non-functional requirements of the software. - To ensure consensus about architecture direction in the project team. |
| Participants | - Person(s) investigating the decision. - People affected by the decision (stakeholders). |
| Requirements | - Decisions are preceded by a Spike to gather background information. - Inform stakeholders, process their feedback, involve them in decision-making. |
| Duration | About one hour to document the decision. |
| Expected outcome | An architecture decision has been made. |