Move feature requirements to component requirements #730

What

We found out that many of our feature requirements do not have component requirements which are derived from this.
See also status here.

So in meeting on 16th September it has been decided, that @aschemmel-tech and @TimoSteuerwaldETAS are working on that.

The outcome of the meeting between Alexander and me is documented as comments which can be found here.

During rework there were several other issues popping up. For example:

• requirements which were still in wrong state
• component requirements which are derived from wrong feature requirement
• (and partly no existing feature requirement to derive a component requirement
• General rephrasing of requirements to be more concrete
• Fixing typos
• Cleaning up glossary (especially in main repo), as many terms are not used at all
• Renamed requirements name to fit better to requirement name or description, so architecture and tests need to be updated accordingly
• Also the requirement mapping to the tests was partly wrong (and this still could be the case)

I used pretty verbose commit messages to point out why a specific change has been done. So this could be used as additional information for review.

These are the two PRs:

• Score-Repo: Feature requirements clarification for lifecycle score#3281
• Lifecycle-Repo: Feature requirements clarification for lifecycle #718

Please make sure that at first the PR in the main repo needs to be merged to main, before the lifecycle PR can be merged. Else the documentation build wont work.

Acceptance Criteria (DoD)

• Feature requirements are moved
• Documentation build passes

How

No response