Relationships
When items are connected, their relationship is used to establish traceability between those items. When an upstream item changes, you can check all downstream related items to make sure they are still accurate and verify that the requirements are intact.
A relationship (trace) between items indicates a direction of definition or abstraction from higher-level requirements or lower-level requirements, from requirements to verification, and from risks to mitigation.
Relationships help you analyze and identify gaps in coverage (such as a requirement lacking verification) and identify change impact. Filters and Trace View features use relationships in Jama Connect to support this analysis.
In Jama Connect, relationships between items have a “direction” indicated by upstream and downstream. These directional relationships are used to assess the impact of a change. For example, if an upstream item is changed, that change might impact how downstream items are defined. When an upstream item changes, the relationship between it and any downstream items is considered suspect.
Upstream/downstream relationships support the horizontal and vertical trace of a V-Model, a standard Systems Engineering approach to requirement definition. Lower-level requirements (downstream requirements) are defined based on their upstream requirements (vertical trace) while verification items are defined based on their related upstream requirement (horizontal trace). As a result, a change to the upstream requirement can potentially impact downstream requirements and verification.
With appropriate permissions, you can relate items within the same project or between multiple projects.
You can:
Find and view relationships | Add relationships |
|---|---|
Single Item View | Single Item View List View Reading View Trace View |