This section covers requirements and defects traceability. In addition to graphically reporting requirement and defect status as indicated by developers, Parasoft Development Testing Platform (DTP) traces requirements and defects back to test cases. At a glance, the team can gain an objective assessment of which requirements are actually working as expected, which defects are resolved, and which requirements and defects still need testing. This real-time visibility into true requirement and defect status helps you prevent late-cycle surprises that threaten to derail schedules and budgets.

Sections include:

Correlating Code During Implementation

When the team works with tasks, source code that is modified when a task is "active" will be correlated with that task—and any associated requirements or defects specified for that task in DTP.

Correlating Code and Tests via Test Case Execution

DTP can monitor source code that is exercised when a test executes and correlate that source code with the appropriate task, requirement, or defect. 

To do this, you need to:

• Enable reporting to Parasoft Report Center - see Connecting to Parasoft Development Testing Platform.
• Mark which task, requirement, or  defect each test is related to - see Indicating Code and Test Correlations.

You can also use the Application Coverage workflow for additional information.

Viewing Correlations in Project Center

When you edit a requirement or defect in Project Center, you can see stored correlations in the following tabs:

• Tasks: Shows the Project Center tasks associated with the given item.
• Requirements: Shows the requirements associated with the given item.
• Defect/Enhancements: Shows the defects or enhancements associated with the given item.
• Code: Shows which source code was touched when the tasks for this requirements were active.
• Automated Tests: Shows which automated tests (tests that can be run via Parasoft products (Jtest, SOAtest, etc.) were marked as being related to the given item.
• Scenarios: Shows  which manual test scenarios performed via Concerto were marked as being related to the given item.

For instance, here are correlations for a requirement:

The same type of correlation information is available for defects:

For both requirements and defect details pages, the tab labels provide a quick overview of the status of the available tests.

Moreover, on the page for the Requirement/Defect you are interested in, the Tasks tab’s Test Status column provides an at-a-glance look at the test status of the various tasks related to this requirement/defect.

Determining Which Requirements Require Retesting

See Determining Where Retesting is Needed.