UC1_R_18

Software should not contain critical CWEs.

Requirement ID

Requirement Textual Description

Requirement Type

Requirement Test Cases

Requirement Test Cases List

VALU3S Framework

Evaluation Environment Type Type of environment where the method is applied. It can be more than one type of environment.(Dimension 1)

Evaluation Type Type of evaluation performed with that method. If a method is hybrid, more than one type can be selected.(Dimension 2)

Type of Component Under Evaluation Type of components that can be evaluated with that method. It can be more than one type.(Dimension 3)

Evaluation Stage The evaluation stage where the method is used.(Dimension 5)

Purpose of the Component Under Evaluation The type of purpose that can be evaluated by a method. It can be more than one type.(Dimension 6)

Type of Requirement Under Evaluation The type of requirements that a method is able to evaluate. It can be more than one type.(Dimension 7)

Evaluation Performance Indicator The type of evaluation criteria or KPI that a method is able to improve. It can be more than one type.(Dimension 8)

Contents

UC1_TC_23

* Preconditions: Applicable to different components under test involved in the scenario. Monitored code being instrumented (possibly configured with noise configuration). Complete source code with testbed available. * Input conditions / steps: Different simulated radar data and camera inputs to be processed by detection algorithm. * Expected result: No data-race and data inconsisteny should be notified.

UC1_TC_24

* Preconditions: C/C++ source code with rules for compilation. * Input conditions / steps: Execute static analysis focused on specific type of software bugs. * Expected result: True-positives or false-positives should be notified.