Requirements

TPT can be used for requirements tracing according to safety norms like IEC61508 or ISO26262. To use requirements in TPT, the additional Requirements Management (RM) Supports Plug-In by PikeTec is needed. Requirements can be linked to test cases, state variants, and assesslets in TPT. Test cases inherit the links to requirements from state variants when those apply to the test case. Therefore, test cases can have links to requirements which are not necessarily directly linked to this test case.

Additionally to the linkage between requirements and test cases during modeling time, the plug-in provides a mechanism to evaluate requirements by assesslets.

Each requirement can achieve one of the following result categories in the report:

PASSED: requirement fulfilled
FAILED: requirement not fulfilled
INCONCLUSIVE: no results could be established
NOT COVERED: requirement not evaluated

To evaluate a requirement, use the REQUIREMENTS.checked() command in a Script assesslet. This command has the following syntax: REQUIREMENTS.checked ("Req-ID", Result). Where "Result" should be one of the following values: TPT.PASSED, TPT.INCONCLUSIVE, or TPT.FAILED. If the "Result" parameter is omitted, TPT.INCONCLUSIVE is assumed.

If several test cases are linked to a requirement and a few of them PASSED, the other FAILED, the requirement is regarded as being FAILED. The reason for this behavior is that the worst result of all linked test cases and assesslets is set as overall result of the requirement. Only if none of the linked elements establishes a result, the result of the requirement will be set to NOT COVERED.

Requirements Overview

To display all requirements and their evaluation in the report in an overview and to generate a Requirement Coverage Summary (only linked requirements) for each execution platform that is placed in the corresponding platform section of the report, select Execution | Execution Configuration, or press Ctrl+F11. Click the Report Settings tab and select the Generate "Requirements" report page check box, see Execution Configuration - Report Settings: Requirements.

The overview consists of a requirements summary displaying a pie chart and a results table showing the overall results of all evaluated requirements and partial results per executed platform and test case. If there are requirements inconclusive, failed, or linked to a test cases that caused an execution error, the IDs of these requirements are listed under die appropriate sub-heading. Click on an ID to jump to the requirement in the requirements result table.

Sub-sections for inconclusive and failed requirements and for those ended in an execution error

The overall result of a requirement is derived from all partial results accumulated during the test execution. Optionally you can restrict them to consider only results achieved while running linked test cases by selecting the check box Consider only linked requirements.

Additionally, requirement issues can be added to the report, see Requirements Issues.

Requirements summary in the HTML report

If multiple platforms are executed, the results are listed in a single table but separated per platform.

URIs

URIs are optional requirement attributes that can be enable or disabled when you import or update requirements. In the Requirement Results section, the requirement IDs are hyperlinks. The hyperlinks work in the report as well as in the TPT user interface.

Requirements hyperlinks imported from an Excel file

Imported URI

Requirements Issues

To show more concisely which requirements are linked to assesslets and test cases, or are not linked to these items, specify in the project-specific Preferences (Option | Preferences, or Ctrl+Shift+P) to insert the following information to the report:

Report unlinked requirements as issue

Use this option to check if every requirement is linked to an executed test case.

Report not checked requirements as issue

Choose this option if you want every requirement to be checked by an assesslet during test execution.

Report an issue if requirements are not checked while executing linked test cases

Enable this option to ensure that requirements are checked by an assesslet while executing linked test cases.

Report an issue if requirements are checked while executing unlinked test cases

If you want no requirement to be checked by an assesslet while executing test cases they are not linked with, choose this option.

Report an issue if requirements are not checked by assesslets they are linked with

Choose this option to assure that requirements are checked by every linked assesslet.

Report an issue if requirements are checked by unlinked assesslets

To check if no requirement is checked by an unlinked assesslet, use this option.

For each of these issues, a table is created in Requirement Issues section of the report. Issues do not affect the requirement results but will be shown summarized in the pie chart in Requirement Issues section.

Requirements issue tables in the report