Ngenaire Docs
Log inSign up free

Network View

The Network View is an interactive graph of a single object and everything linked to it. It is the fastest way to answer "what is connected to this?" — which verifications close a requirement, which requirements a risk impacts, or which artifacts trace to a Statement of Work.

The Network View is a modal, not a page. There is no /network-view route — you open it from wherever an object's code appears.

How to open it

The Network View opens from an object's ID link — the highlighted object code (for example REQ-000001, RISK-000004, SOW_GPC_000001) that appears throughout the app.

  1. Click an object's ID link. By default this opens the Network View modal centered on that object.
  2. Alternatively, right-click an object ID for its menu and choose Open network view (the menu also offers Open details page).

Object IDs appear on requirements, risks, test cases, test procedures, issues, tasks, ConOps objects, Statements of Work, and SOW objects — so you can reach the Network View from almost anywhere those artifacts are listed.

What you see

  • The object you opened it from is the focal node at the center.
  • Around it are the artifacts it links to, with each edge representing a link between two artifacts.
  • Nodes are styled by type — requirement, risk, issue, task, test plan, test procedure, test case, ConOps object, SOW, and SOW object.

A SOW node appears on a requirement whenever a Statement of Work references that requirement's code, so you can see which SOWs cite it. A SOW object (a linked span of SOW text) appears edged to each artifact it traces to and to its parent SOW document.

Walkthrough

1. Inspect a node

  1. Click a node to open its details and read its metadata and links without leaving the graph.

2. Expand the graph

  1. Click a node with linked neighbors to expand it and pull in its own neighbors.
  2. Repeat to walk the traceability web outward, following links from one artifact to the next.

3. Create a verification link (where supported)

  1. From a requirement, test plan, test procedure, or test case node, you can create a verification link directly in the modal — pick the target and confirm.

Using it to spot problems

  • Find orphans. Expand around a requirement to see whether anything verifies it; a node with no expected neighbors is a coverage gap.
  • Understand impact. Before changing an artifact, expand its graph to see what depends on it.
  • Trace across artifact types. Follow links from requirement to risk to test case to SOW to understand the full chain.

Tips

  • Use it to diagnose, not to author. Most links are created from the individual artifact pages; the Network View is for seeing and traversing them.
  • Combine with the RVTM. The Network View shows the local graph; the RVTM gives the full row-and-column trace report.

Related