Understand requirement relationships
Read crosswalk direction, inspect related requirements, and reuse links deliberately.
Open Relationships to explore connections across systems. For one system, choose it in Management systems and open Mappings for connections involving its declared frameworks, including the Crosswalk view. Declare a framework first if the system has no mappings to show.
Explore connected requirements
Switch between the available graph, matrix, and list views. Search for a requirement or use filters for systems, link kinds, and relation types. Include unlinked requirements when you need to see isolated entries. Select a node or pair to inspect the records behind the visualization, then open the requirement for its full details.
Filters can hide connections. Reset them before concluding that two requirements have no relationship. Treat truncated previews as a partial view and open the complete list or related record where offered.
Read the direction
A mapping detail identifies Source and Target, its relation, origin, rationale, and uses from each end.
| Relationship | Meaning from source to target |
|---|---|
| Equivalent | The same obligation in both frameworks. |
| Subset | The source is covered by the target. |
| Superset | The source covers the target and more. |
| Related | The requirements overlap but are not interchangeable. |
| Shared requirement | The same requirement appears in two management systems. |
When a preview is oriented from the other end, subset and superset switch places. Read labels such as from this requirement and the source and target headings before deciding what can be reused. Mappings and inherited results do not determine a register entry's satisfaction; each entry has its own assessment.
Reuse supporting content
Open the entry with the linked document, choose Reuse on related requirements, and select the intended candidates. Check their system and relationship labels before choosing Link to ... requirements, which shows the selected count. The content stays in its source project and the selected entries gain links to it.
Already-linked candidates need no additional link. If some selected entries are busy or inaccessible, review the result and retry after resolving those entries. A relationship alone does not grant project access.
Hide an unsuitable catalog mapping
Workspace Admins and Owners can choose Hide this mapping in a system crosswalk, enter a Reason, and confirm Hide mapping. Requirements stop suggesting each other through this mapping in the workspace. The catalog is unchanged. Use Restore on the hidden mapping when it should apply again.
Open a mapping detail to inspect its rationale, suppression information, and the systems using each end. Entries outside your access or marked not applicable may be excluded from the displayed uses.