Connects a Program, Project, Product, or Item to a Requirement relevant to it.
When to use it
Use Requirement to connect a recorded need or acceptance criterion to the product, item, or work it applies to.
Records and direction
- Relationship type: Non-structure. Associates the records without creating a parent-child hierarchy.
- From: Program, Project, Product, Item.
- To: Requirement.
How to use it
- Create the relation with drag and drop in a Structure widget: drag the intended Requirement onto the Product it relates to. Select Requirement, review the source, target, and any offered values, then confirm.
- Alternatively, use Connect from the source record and choose the target and 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
Industrial Pump P-Series is connected to Pump Leakage Limit. Reviewers can find the acceptance criterion from the product and inspect its verification method and evidence.
What to check
The related context identifies a relevant Requirement. The connection supports traceability; it does not establish that the requirement has been satisfied.
Choosing the relationship
Choose Requirement for applicability to a Product, Item, Program, or Project. Subrequirement creates a requirements hierarchy, and Compliance Reference identifies supporting documentary evidence.
