Places a Requirement under another Requirement as a more detailed subrequirement.
When to use it
Use Subrequirement to break a broad requirement into smaller, separately managed requirements.
Records and direction
- Relationship type: Structure. Places the target record within the source record’s 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 Subrequirement, review the source, target, and any offered values, then confirm.
- Alternatively, use Connect from the source record and choose the target and Subrequirement 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 has Pump Leakage Limit beneath it. The parent describes the broader need, while the child captures a more detailed criterion.
What to check
The child Requirement appears within the parent’s structure. Review each description so the breakdown remains understandable.
Choosing the relationship
Subrequirement is a Structure relationship. Use Derived Requirement for a non-structure derivation link. Adding a child requirement does not by itself prove the parent requirement is fulfilled.
