Improvement: Versioning of Requirements

[FScholPer]

What

Currently it is not possible to set a version to an requirement. Background is that currently for the version 1.0 I want to modify existing requirements or adding new requirements which should only be part of the tracing in context of the version 1.0.
Requirements for 0.5 should stay the same.

How

• Describe how the modification of existing requirements should be done (tagging, new artifact feature/component modification)

Example

• Modification of Communication Feature only in context of Version 1.0 Feature Modification for Cross-VM IPC score#916 Cross-VM IPC (#916) score#1371

Affects Detailed Design
Requirements / Architecture

Requirements / Architecture are not affected by this change?

How

No response

Estimates for realization

none

Category

• Affects Detailed Design

Requirements / Architecture

• Requirements / Architecture are not affected by this change?

[kroehnd]

A possible implementation of this would be to add an attribute called
Planned in Release: ReleaseVersion
or
Implemented in Release: ReleaseVersion
to indicate from which release on the requirement is applicable