valid_from enforced as mandatory for feat_req/stkh_req in metamodel

[Ahmed-Elsaka-JC]

Description

Component: docs-as-code / score_metamodel
Severity: Medium (blocks docs build; forces process-non-conformant data)
Description:
The requirements-engineering process defines valid_from as an optional validity attribute for stakeholder and feature requirements. The attribute definition gd_req__req_attr_valid_from states requirements "can have" this attribute and is not tagged mandatory (unlike UID, title, status, safety, security). It is only intended for the "specification ahead of implementation" use case (future/past milestones).

However, the metamodel schema declares valid_from under mandatory_options for both feat_req and stkh_req

https://eclipse-score.github.io/process_description/main/process_areas/requirements_engineering/guidance/requirements_process_reqs.html#gd_req__req_attr_valid_from

https://github.com/eclipse-score/docs-as-code/blob/main/src/extensions/score_metamodel/metamodel.yaml#L353

https://github.com/eclipse-score/docs-as-code/blob/main/src/extensions/score_metamodel/metamodel.yaml#L325

[AlexanderLanin]

its not a bug, since that requirement was not yet implemented. This is a new feature.

[Ahmed-Elsaka-JC]

@AlexanderLanin

yes if requirement is not implemented and it is a new feature why did you mandate to set valid_from element ?

based on the follwoing it "can have" means optional :

Also in case of invalid requirement which will not be implemented , how can i put valid_from item ?

[MaximilianSoerenPollak]

@AlexanderLanin

yes if requirement is not implemented and it is a new feature why did you mandate to set valid_from element ?

based on the follwoing it "can have" means optional :

Also in case of invalid requirement which will not be implemented , how can i put valid_from item ?

We will ask this in process meeting today.

But as far as I know this is correct.