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 |
|---|---|---|---|
| Test node | Link it with verifies or verified_by | Test-to-requirement, document, or code relationship | The endpoint pair must match the allowed relation |
| Deviation node | Link it with deviates_from or deviation_evidence | Deviation connected to a requirement, document, code reference, or test | The link records evidence; it does not close the deviation |
| Declared link | Another administrator selects Approve in Trace links awaiting approval | Governed forward and reverse hop | Candidate and rejected links do not count as evidence |
| Lifecycle fields | Record the declaration time as the start date | Time-bound relationship record | An end date, when present, must be later than the start date |
| Provenance | Keep the Evidence reference, declarer, and reviewer | Evidence reference shown on the hop | Provenance does not prove source correctness |
| Broken or moved endpoint | Report it instead of expanding it | Entry under Coverage blockers | The app does not infer a replacement |
How it works
- Open Terminology Baseline and scroll to Enterprise evidence workspace.
- In Trace graph, choose the requirement or implementation node in Start node.
- Select Show trace graph.
- Select Forward impact to see tests and deviations downstream.
- To follow a test or deviation back to its basis, choose it in Start node, select Show trace graph, then Reverse provenance.
- Review each hop's evidence reference and every Coverage blockers entry.
Example
A system requirement has an approved verified_by link to a safety test. That test has an approved deviation_evidence link to a recorded exception. Forward impact from the requirement shows the test and the deviation as one chain. A candidate replacement test stays outside that chain until another administrator approves it.
What this does not mean
The trace records relationships. It does not run tests. It does not approve deviations. It does not decide whether a test passed. It does not replace release approval or electronic signatures. Missing endpoints and traversal limits can make the visible result partial.
Related questions
Next step
Review the requirement-to-test-to-deviation chain before a release or audit handoff.
View on Atlassian Marketplace