NexusRM / Traceability

Every link has a type. And a direction.

Connect system requirements to the software requirements that decompose them and the test cases that verify them, then follow the chain in either direction.

01 / Links

Links you can reason about.

Each link has a type, such as Decomposes, Verifies or Impacts, and a direction. The Links tab on an object shows its parents and children with their modules, and the same links can be queried from either end.

Duplicate links and links from an object to itself are rejected, so the trace stays clean. Links can also cross module and project boundaries.

  • Typed, directional links
  • Duplicate and self-link rejection
  • Cross-module and cross-project links
Object editor for SWR-022 showing its Links tab with a Decomposes parent, an Impacts link from the ICD and a Verifies link from a test case
02 / Graph

See the chain, not a list.

The object graph puts the selected object in the centre, higher-level items to the left and lower-level items to the right, up to five levels deep on each side. It answers "where did this come from?" and "what depends on it?" in one picture.

  • Ancestors left, descendants right
  • Depth from one to five
  • Deep link to any object by number
Object graph for SYS-006 at depth three, tracing system requirement to software requirements and test cases
Access

Need-to-know filtering

Links and graph nodes in projects you cannot see are hidden, with a notice that some results were withheld.

Coverage

Gaps in a matrix

Turn the links into a coverage matrix that highlights everything left unlinked.

History

Every link change audited

Creating or removing a link is recorded in the hash-chained audit log like any other change.