This page contains some rudimentary documentation for the decision process used in FAE for the EVATool prototype.
These are the decision types used in the architectural decision process.
Symbol | Type | Explanation |
---|---|---|
Error | There are errors in the decision description; please fix immediately. | |
Todo | There are todos in the decision; must be fixed before closing. | |
Must | A decision (principle, solution, technology etc.) that is binding for all teams. Icon color indicates decision status (see tables below). | |
Should | A decision that is a recommendation for all teams, e.g. a technology that seemingly works well; teams can still deviate if they have good reasons to do so. Deviations must be reasoned by a team decision (see below). Icon color indicates decision status (see tables below). | |
Team | Team decision; can be taken without consulting anyone outside the team. Icon color indicates decision status (see tables below). |
All decisions can go through the following status (explained for “Must”, but “Should” and “Team” has the same status names and color codes).
Symbol | Keyword in Decision Log | Status | Explanation |
---|---|---|---|
_1_open | Open | An open decision has been created, but no resolution is available yet | |
_2_draft | Draft | A resolution is available and documented, but there has not yet been a discussion about it. | |
_3_agreed | Agreed | The resolution has been discussed and agreed upon in the group where the decision belongs. |