Connects change work to a Requirement relevant to that change.
When to use it
The Change Cockpit is the main UI for managing change types and their relationships. Use Change – Requirement to identify requirements relevant to a proposed or implemented change.
Records and direction
- Relationship type: Non-structure. Associates the records without creating a parent-child hierarchy.
- From: Change Request, Change Order, Change Task.
- To: Requirement.
How to use it
- Create the relation with drag and drop in a Structure widget: drag the intended Requirement onto the Change Request it relates to. Select Change – Requirement, review the source, target, and any offered values, then confirm.
- Alternatively, use Connect from the source record and choose the target and Change – 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
Improve Seal Design is connected to Pump Leakage Limit. Reviewers can assess the proposal against the criterion it needs to address.
What to check
The change work has traceability to a Requirement. Review the criterion, verification approach, and evidence when evaluating the change.
Choosing the relationship
Change – Requirement connects change work to a criterion. Requirement connects a Product, Item, Program, or Project to a criterion. Creating either link does not prove the requirement has been satisfied.
