Page tree

Skip to end of metadata
Go to start of metadata

DTP enables you to demonstrate traceability between requirements managed in your requirements management system (RMS) and:

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

Requirements traceability is facilitated by DTP, but it also requires data from a test and analysis tool (e.g., SOAtest or DTP engine). You can also deploy the JIRA Traceability Report to readily view the requirement traceability information. You can download the Traceability Report and the JIRA Traceability Report extensions from the Parasoft Marketplace and deploy them to your DTP system using Extension Designer.

About Associating Requirement with Files

You can view violation, change review, and 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 Associating Requirements with Files for instructions.

About Associating Requirements with Tests

How to associate requirements with tests is described in the documentation for the test and analysis tool used. See the documentation for the following tools:

  • SOAtest
  • Jtest DTP Engine
  • C/C++test DTP Engine
  • C/C++test Desktop
  • dotTest DTP Engine

About Traceability Reporting

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

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