Process Requirements#

Linking Requirements to Tests
status: valid
tags: prio_1_automation, verification, verification
version: 1
contained by: wf__verification_comp_int_test, wf__verification_feat_int_test, wf__verification_platform_int_test, wf__verification_unit_test
complies: std_req__iso26262__support_6432
satisfies: wf__verification_comp_int_test, wf__verification_feat_int_test, wf__verification_platform_int_test, wf__verification_unit_test

For linking test suites to requirements following metadata shall be used:

  • Verifies

    • PartiallyVerifies

    • FullyVerifies

  • Description

  • TestType

    • Fault Injection (fault-injection)

    • Interface Test (interface-test)

    • Requirements-based Test (requirements-based)

    • Resource Usage Evaluation (resource-usage)

  • DerivationTechnique

    • Analysis of requirements (requirements-analysis)

    • Analysis of design (design-analysis)

    • Analysis of boundary values (boundary-values)

    • Analysis of equivalence classes (equivalence-classes)

    • Fuzzy testing (fuzz-testing)

    • Error guessing based on knowledge or experience (error-guessing)

    • Explorative testing (explorative-testing)

More information can be found in the Verification Guideline, Verification Concept, and Test Specification Guideline .
gd_req__verification_link_tests
Process Requirements
Linking Requirements to Tests (C++)
status: valid
tags: prio_1_automation, verification, verification
version: 1
contained by: wf__verification_comp_int_test, wf__verification_feat_int_test, wf__verification_platform_int_test, wf__verification_unit_test
complies: std_req__aspice_40__SWE-4-BP4, std_req__aspice_40__SWE-5-BP6, std_req__aspice_40__SWE-6-BP4, std_req__iso26262__support_6432
satisfies: wf__verification_comp_int_test, wf__verification_feat_int_test, wf__verification_platform_int_test, wf__verification_unit_test

For linking C++ tests to requirements record properties shall be used. Attributes which are common for all test cases can be specified in the Setup Function (SetUp()), the other attributes which are specific for each test case need to be specified within the test case:

A more detailed description of how to link code to requirements looks like is available in the C++ Properties Template
gd_req__verification_link_tests_cpp
Process Requirements
Linking Requirements to Tests (Python)
status: valid
tags: prio_1_automation, verification, verification
version: 1
contained by: wf__verification_comp_int_test, wf__verification_feat_int_test, wf__verification_platform_int_test, wf__verification_unit_test
complies: std_req__aspice_40__SWE-4-BP4, std_req__aspice_40__SWE-5-BP6, std_req__aspice_40__SWE-6-BP4, std_req__iso26262__support_6432
satisfies: wf__verification_comp_int_test, wf__verification_feat_int_test, wf__verification_platform_int_test, wf__verification_unit_test

For linking python tests to requirements metadata shall be used. For this the ‘add_test_properties’ decorator has been provided. You need to add it to the test and fill out:

  • partially_verifies OR fully_verifies

  • test_type

  • derivation_technique

For allowed values for test_type & derivation_technique please check Linking Requirements to Tests Further more, this decorator will also check if your test has a docstring which should act as the description of the test.

A more detailed description of how to link code to requirements looks like is available in the Python Properties Template
gd_req__verification_link_tests_python
Process Requirements
Linking Requirements to Tests (Rust)
status: valid
tags: prio_1_automation, verification, verification
version: 1
contained by: wf__verification_comp_int_test, wf__verification_feat_int_test, wf__verification_platform_int_test, wf__verification_unit_test
complies: std_req__aspice_40__SWE-4-BP4, std_req__aspice_40__SWE-5-BP6, std_req__aspice_40__SWE-6-BP4, std_req__iso26262__support_6432
satisfies: wf__verification_comp_int_test, wf__verification_feat_int_test, wf__verification_platform_int_test, wf__verification_unit_test

For linking Rust tests to requirements #[record_property] shall be used:

A more detailed description of how to link code to requirements looks like is available in the Rust Properties Template
gd_req__verification_link_tests_rust
Process Requirements
Multiple derivation techniques in testing
status: valid
tags: prio_1_automation, verification, verification
version: 1
complies: std_req__aspice_40__SWE-4-BP4, std_req__aspice_40__SWE-5-BP6, std_req__aspice_40__SWE-6-BP4, std_req__iso26262__support_6432
satisfies: wf__verification_comp_int_test, wf__verification_feat_int_test, wf__verification_platform_int_test, wf__verification_unit_test

It shall be possible to use multiple derivation techniques as one property within a single test case
gd_req__verification_methods_multiple
Process Requirements
Independence
status: valid
tags: done_automation, verification, verification
version: 1
contained by: wf__verification_comp_int_test, wf__verification_feat_int_test, wf__verification_platform_int_test, wf__verification_unit_test
complies: std_req__aspice_40__SWE-4-BP4, std_req__aspice_40__SWE-5-BP6, std_req__aspice_40__SWE-6-BP4
satisfies: wf__verification_comp_int_test, wf__verification_feat_int_test, wf__verification_platform_int_test, wf__verification_unit_test

The approver of a pull request shall differ from the author(s) of the pull request in all pull requests.
gd_req__verification_independence
Process Requirements
Verification Reporting
status: valid
tags: prio_1_automation, verification, verification
version: 1
satisfies: wf__verification_mod_ver_report

The tool automation shall automatically generate the Verification reports. These may be independent documents (i.e. not integrated into docs-as-code based repositories). The reports shall use Platform Verification Repor... and Module Verification Report .... The content of the reports is specified in Platform Verification Report and Module Verification Report. The execution results of test cases are marked with a clear pass/fail result.
gd_req__verification_reporting
Process Requirements
Verification Report Archiving
status: valid
tags: prio_1_automation, verification, verification
version: 1
satisfies: wf__verification_mod_ver_report

The tool automation shall automatically archive the Verification reports for releases. The reports are generated according to Verification Reporting.
gd_req__verification_report_archiving
Process Requirements
Verification Documentation Checks
status: valid
tags: prio_1_automation, verification, verification
version: 1
satisfies: wf__verification_comp_int_test, wf__verification_feat_int_test, wf__verification_platform_int_test, wf__verification_unit_test

The following checks shall be implemented on test metadata:

  • TestType and DerivationTechnique shall be set

  • Description shall not be empty

  • In a Platform Integration Test Partially/FullyVerifies shall be set to at least one Platform Requirement

  • If Partially/FullyVerifies are set in Feature Integration Test these shall link to at least one Feature Requirement

  • If Partially/FullyVerifies are set in Component Integration Test these shall link to at least one Component Requirement

  • If Partially/FullyVerifies are set in Unit Test these shall link to at least one Component Requirement
gd_req__verification_checks
Process Requirements
Verification Documentation Checks Extended
status: valid
tags: verification, verification
version: 1
satisfies: wf__verification_comp_int_test, wf__verification_feat_int_test, wf__verification_platform_int_test, wf__verification_unit_test

The following checks shall be implemented on test metadata:

  • If TestType is set to requirements-based then PartiallyVerifies or FullyVerifies shall contain a link to at least one requirement

  • If TestType is set to interface-test then PartiallyVerifies or FullyVerifies shall contain a link to at least one interface
gd_req__verification_checks_extended
Process Requirements
Verification of External Components AoUs
status: valid
tags: prio_2_automation, verification, verification
version: 1
satisfies: wf__verification_comp_int_test, wf__verification_feat_int_test

External components AoUs shall be verified by integration tests or static analysis tooling.

Note1: These external components AoU need to be checked generally for the complete platform, so we create a process automation requirement for this.

Note2: One example would be the checking if safety components are only using “safe” functions of the operating system.
gd_req__verification_external_aou
Process Requirements
Static Code Analysis Classification
status: valid
tags: prio_2_automation, verification, verification
version: 1
satisfies: wf__verification_comp_int_test, wf__verification_feat_int_test, wf__verification_platform_int_test, wf__verification_unit_test

Static code analysis findings shall be classified according to the following categories:

  • Critical

  • High

  • Medium

  • Low

The actual classification shall be either provided by the tool as a suggestion or defined manually by Quality Manager together with Committer.

Alternative rating like class A, B, C, D or 1, 2, 3, 4 can be used as well, but the principle mapping to the above categories shall be preserved and documented.
gd_req__verification_sca_classification
Process Requirements
CI reference integration execution
status: valid
tags: prio_2_automation, verification, verification
version: 1
satisfies: wf__verification_comp_int_test, wf__verification_feat_int_test, wf__verification_platform_int_test, wf__verification_unit_test

The CI reference integration execution shall be triggered on regular basis to guarantee the inter-operation of all integrated components when a new component is added to the system or an existing component is updated via a PR.

TODO: Align this to the ongoing work in `PR #190 <https://github.com/eclipse-score/reference_integration/pull/190>`_ which reworks the CI reference integration execution.
gd_req__verification_ci_reference_execution
Process Requirements