eclipse-score / eclipse-score/process_description

Improvement: Decision Record misses the fields to tick the impact on architecture/requirement/tooling

Open
#581 0 comments 0 reactions 1 assignee Claimed by @pahmann View on GitHub
Dominant language
HTML
Stars
4
Forks
22
Avg merge
9h 40m
Merged PRs (30d)
12

Description

### What

When we write e.g. an improvement we have to tick Detailed Design, requirements, architecture. But the decision record does not have it.

In the current way it is not guaranteed that the impact of the decision is traced.
Open part is also that a change request can make previous decision records obsolete.
Also, we still cannot track that one of the previous Decision Record will not be violated by a future architectural work, which is not aware of the decision records.

### How

_No response_

### Estimates for realization

4h

### Category

- [ ] Affects Detailed Design

### Requirements / Architecture

- [x] Requirements / Architecture are not affected by this change?

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.