Preserve assumed-system requirement traceability without rendering inherited requirements as standalone ASR pages

[vishwajitdandage]

Feature Request / Modification Description

Assumed System Requirements (ASRs) referenced by Feature Requirements through derived_from must be available to component traceability processing. Currently, this propagation is missing, so component traceability cannot resolve those ASR IDs.

A direct propagation of AssumedSystemRequirementsInfo through Feature Requirements fixes traceability, but causes an unintended documentation effect: the documentation generator treats the propagated provider as an owned ASR target and renders Feature Requirement content under the Assumed System section.

Expected Changes of work products

• Requirements
• Architecture
• Safety Analysis
• Security Analysis
• Detailed Design
• Implementation and Testing
• all

Impact analysis

NA

Safety or Security relevance

• none
• Safety relevant
• Security relevant

Expected required ASIL classification

QM

Expected Implementation Version (Release)

1.0

[vishwajitdandage]

Reference - #442 (comment)