At a glance
| Input | Action | Output | Limit |
|---|---|---|---|
| Governed requirement | Use its stable node identity and recorded source | Versioned requirement evidence | The requirement must exist in the deposited graph |
| Imported or approved links | Follow forward relationships | Ordered evidence hops | Candidate and rejected links are excluded |
| Connected evidence nodes | Preserve type, version, approval, dates, and provenance | Documents, code, tests, deviations, or approvals | Results depend on recorded relationships |
| Traversal bounds | Apply hop and result limits | Bounded graph response | Coverage blockers identify incomplete expansion |
How it works
- Open Enterprise evidence workspace.
- Review Coverage blockers.
- If GRAPH_START_REQUIRED appears, the view has no starting evidence node.
- Once the requirement graph is loaded, select Forward impact in Trace graph.
- Read each relationship and connected evidence node.
- Open the evidence reference for any retained hop.
- Select Run verification before a formal handoff.
Example
A system requirement connects to a component requirement through a governed derives link. The component requirement has governed links to a controller code reference and its validation test. Forward impact shows that path as separate hops. A candidate link to another test stays outside governed evidence until its approval state changes.
What this does not mean
The graph reports recorded evidence. It does not infer a missing relationship. It does not convert a candidate into approved evidence. A visible path may stop at its configured hop or result bound. Without a stable start node, the workspace reports GRAPH_START_REQUIRED and returns no trace hops. Forward traceability does not certify compliance or approve a release.
Related questions
Next step
Open the requirement in the evidence workspace and review its governed forward path.
View on Atlassian Marketplace