requirements_traceability

Build a traceability matrix by initializing a repository and adding trace links that connect business needs, requirements, components, and tests. You can then export the matrix for audits and stakeholder reporting.

Impact analysis in requirements traceability works by running a graph query across linked artefacts to propagate changes. It identifies which components and tests are affected when a business need or functional requirement changes.

Check test coverage by running a coverage check against the traceability graph to surface orphaned connections. This verifies that every functional requirement has corresponding test cases linked in the repository.

Yes, you can use this for change request impact assessment in software projects. It evaluates incoming change requests against the traceability graph to determine affected business needs, components, and test cases.

The best way to trace business needs to test cases end-to-end is by building a traceability graph linking BN, BR, FR, and TC artefacts. This ensures full provenance from initial stakeholder needs down to verification tests.

No external dependencies are required to run traceability analysis. The tool leverages internal MCP primitives to initialize repositories, add trace links, and execute impact analysis without additional setup.