Requirements Traceability
Build explicit directed links from a requirement to an implementation artifact and test, from an artifact to a test, and from a test to evidence. Record each test result with the requirement and artifact revisions that were current at that run. The matrix flags absent links, missing passing results or evidence, stale revision snapshots and artifacts not covered by a linked test. A changed artifact can be traced through its dependents to affected tests and requirements. These user-entered records are a planning aid, not proof that software or evidence actually satisfies a requirement.
Key features
- Stable IDs and revision counters for requirements and implementation artifacts
- Typed, directed requirement–artifact–test–evidence and artifact-dependency links
- Append-only test-result entries with requirement/artifact revision snapshots
- Unlinked, unverified, stale and orphan records in a traceability matrix
- Reverse dependency impact traversal from a selected changed artifact
- Strict versioned JSON restoration and formula-safe CSV report
How to use
- Load the fictional checkout example or start a blank project; add requirements with acceptance criteria, artifacts with references, tests with expected results and evidence with locators.
- Create directed links: requirement implements-by artifact, requirement verified-by test, artifact exercised-by test and test supported-by evidence. Add artifact dependencies where relevant.
- Select a test, result and linked evidence, then record a run. The run snapshots the currently linked requirement and artifact revision numbers.
- Inspect matrix gaps, orphan tests and orphan evidence. Revise an artifact or requirement and see prior passing runs become stale until retested.
- Select a changed artifact to trace dependent artifacts, affected tests and requirements. Download JSON for later editing or CSV for review.
Use cases
- Track checkout acceptance criteria to UI files and end-to-end tests
- Find passed tests with no linked run evidence
- Plan retesting after a shared component changes
- Expose orphan tests that cover no recorded requirement
Frequently asked questions
When is a requirement marked verified?
It needs at least one linked implementation artifact and test. Every linked test needs a latest passing run with active linked evidence and the current requirement revision. Every linked artifact must be exercised by a linked test whose latest passing run captured its current revision. This is this tool's conservative rule, not a formal compliance standard.
Why did a passing test become stale?
A test run stores the revisions of requirements and artifacts linked when it was recorded. Revising a requirement or artifact increments its revision. An older passing run can no longer verify the new revision; record a new test run after review.
What does changed-artifact impact show?
It walks reverse artifact dependencies: an artifact that depends on the changed one is included, recursively. It then lists tests exercising affected artifacts, requirements linked to those artifacts or tests, and evidence linked to those tests. It reports possible review scope; it does not analyze source code or prove a defect.
Can a pass be recorded without evidence?
Yes, to preserve the observer's statement, but a requirement remains unverified until the latest passing run includes at least one currently linked evidence record. Evidence locators are user-entered and never fetched or authenticated by this page.
What are orphan tests and evidence?
An orphan test has no requirement-to-test verification link. Orphan evidence has no test-to-evidence support link. They remain visible in the project and CSV rather than being silently dropped.
Where is the project saved?
It stays only in this browser tab, with no automatic upload or save. Download the strict version 1 JSON before leaving; invalid imports preserve the current project. CSV is a review report, not an import format. User-editable JSON is not a tamper-proof audit log.
Privacy
Requirements, paths, test notes and evidence locators remain in this browser tab. There is no remote collection or automatic save. Avoid secrets in references and review downloaded files before sharing.
Comments & questions