DTP enables you to demonstrate traceability between requirements managed in your application lifecycle management (ALM) or requirements management system (RMS) and software quality artifacts, including:

• Test test cases that test the requirements,
• files that implement the requirements,
• static analysis violations detected in the implemented source code files, and
• code change reviews, and
• review findings associated with the implementation files (see Change Explorer).

You can access traceability information either programmatically (see About Traceability Reporting), or by deploying the Requirements Traceability Report extension (see Traceability Pack). 

Prerequisites

• Test, code analysis, and or change review data from C/C++test, dotTEST, Jtest, Selenic, of or SOAtest.
• A connection to an external system should be configured (see ALM Tool Integration Overview). 
• Existing requirements or work items in your third-party system (e.g., Jira stories) 

About Associating Requirement with Files

You can view violation, change review, and The requirement details report shows test results data per requirement in requirement details reports. These reports can be generated and viewed using a special workflow. on the report requires a special workflow. See for each requirement. The report can also show information about static analysis violations and code reviews if requirements are associated with files as described in the Associating Requirements with Files for instructions section.

About Associating Requirements with Tests

...

You can view traceability information after associating requirements with files and associating requirements with tests in a few ways:

• By implementing the JIRA Requirements the Traceability DTP Enterprise Pack extension.
• By calling the DTP REST API endpoints for traceability data.