Connects two Requirements to record a derivation relationship. It provides traceability between an existing requirement and a requirement developed from it.
When to use it
Use Derived Requirement when the team needs to trace a requirement developed from another requirement.
Records and direction
- Relationship type: Non-structure. Associates the records without creating a parent-child hierarchy.
- From: Requirement.
- To: Requirement.
How to use it
- Create the relation with drag and drop in a Structure widget: drag the intended Requirement onto the Requirement it relates to. Select Derived Requirement, review the source, target, and any offered values, then confirm.
- Alternatively, use Connect from the source record and choose the target and Derived Requirement relationship from the available options.
- Review the resulting connection in the structure or related information. Check the selected records, their versions where applicable, and the relationship filters if the link is not visible.
Example
Pump Performance Requirements is connected to Seal Leakage Requirement. The derived criterion’s description explains how it was developed from the broader expectation.
What to check
The relationship records derivation between the two Requirements. Keep the rationale in the requirement information so reviewers can understand the connection.
Choosing the relationship
Derived Requirement is non-structure. Use Subrequirement when a child belongs beneath a parent in a requirements hierarchy. Review derivation direction and descriptions before adding the link.
