Watch: Trace a Test Back to the Regulation Behind It (Four-Eyes Approved)
The embedded player uses YouTube’s privacy-enhanced domain. You can also watch the video on YouTube.
Transcript
After an incident, the hardest question is: why was it built this way? Which regulation, which decision, which requirement led to this code and this test? Compliance Glossary keeps that chain in Confluence. Declare what matters: a regulation, a requirement, a piece of code, and a test. Then link them. The requirement derives from the regulation, the code implements the requirement, and the test verifies it. Links are not trusted on one person's word. A second reviewer approves each one, with the same four-eyes rule your glossary uses. Now start from the test and run reverse provenance. The app walks the approved links back to the root: test, code, requirement, regulation. Download the trace chain and send it to your auditor, or to your customer. From any artifact back to the reason it exists. Compliance Glossary for Confluence.
At a glance
| Input | Action | Output | Limit |
|---|---|---|---|
| Approved document or code_reference node | Choose it in Start node and select Show trace graph | Graph expanded from the implementation | Nodes come from Declare trace node and need another administrator's approval |
| Approved implements link | Select Reverse provenance | Hop from the implementation to its requirement | Candidate and rejected links are excluded |
| Approved derives links | Follow the hops in Trace graph | Element, system, and business requirement chain | Only allowed node and relation pairs are accepted |
| Approved authorizes link | Reached as the upstream end of a requirement | The business decision behind the requirement | No decision appears unless someone declared and approved the link |
| Missing, moved, or unapproved endpoint | Review Coverage blockers | An explicit gap instead of a silent omission | The app does not reconstruct undocumented reasons |
How it works
- Open Terminology Baseline and scroll to Enterprise evidence workspace.
- In Trace graph, choose the implementation node in Start node.
- Select Show trace graph.
- Select Reverse provenance.
- Follow the hop from the implementation to its requirement.
- Continue through higher-level requirements to the business decision.
- Review the evidence reference on each hop.
- Check Coverage blockers, then select Download trace chain to keep the result.
Example
A safety-control change raises a motor stop threshold. Reverse provenance from the code node reaches its element requirement. The next hop reaches the system safety requirement. An authorizes link reaches the recorded business decision. Leadership can review why the change exists, and see missing evidence before an incident review.
What this does not mean
The trace proves only the relationships people declared and approved, or that were imported. It does not infer intent, validate the implementation, or approve the business decision. An absent root can mean no governed link exists. A path with Coverage blockers is partial.
Related questions
Next step
Run Reverse provenance from one critical implementation. Confirm that every requirement and decision hop has evidence.
View on Atlassian Marketplace