Relationships

Relationships define the kinds of links records can have, and the rules for which records may link to which. They’re the configuration behind the trace thread: traceability is only as sound as the relationship types that structure it.

Relationship types and direction

You define each relationship type with an upstream and a downstream side, giving the link a clear direction — a requirement is verified by a test, a test verifies a requirement. A type can be bidirectional so it reads correctly from either end. Naming the direction is what makes a trace meaningful rather than a vague association: you can tell what a link means, not just that two records are connected.

Relationship rules

Beyond naming the type, you set rules for which item types may participate — so a “verifies” link can be allowed between a test and a requirement but not between two unrelated types. These rules keep the thread valid: people can only create links that make sense, which prevents the trace data from filling with meaningless or contradictory connections.

Why it governs traceability

Because every trace link is an instance of a relationship type defined here, this is where the integrity of traceability is set. Define the types and rules well and the trace matrix, coverage analysis, and impact analysis all rest on solid ground. The user-facing side of creating and following links is covered in the Traceability section.