Evaluation Scenario Requirements

Evaluation Scenario Requirements List

• UC5_R_1 Under sensor faults, while tracking pilot commands, control objectives shall be satisfied.
• UC5_R_2 Under sensor faults, during regulation of nominal system operation, control objectives shall be satisfied.
• UC5_R_3 Under sensor faults, while tracking pilot commands, operating limit objectives shall be satisfied.
• UC5_R_4 Under sensor faults, during regulation of nominal system operation, operating limit objectives shall be satisfied.

V&V Methods

V&V Methods List of the methods used in this evaluation scenario

• Model-Implemented Attack Injection In this method, the attacks (which are special types of faults) are injected in the model of the system under test (SUT). MATLAB and LabVIEW are examples of tools used to build such system models. This method is used to verify and validate the system’s capability to handle attacks. The attack handling includes mechanisms to detect and prevent intrusions. This type of attack injection method is used for the system’s evaluation in the early design stages.
• Model-Implemented Fault Injection In this method, the faults are injected in the model of the system under test (SUT). MATLAB and LabVIEW are examples of tools used to build such system models. This method is used to verify and validate the system’s capability to handle faults. The fault handling includes attributes such as fault detection, correction, or fallback with or without the fault handling mechanisms implemented. This type of fault injection method is used for the system’s evaluation in the early design stages.
• Simulation-Based Verification Simulation-based verification is the transfer of systems from the real environment to the simulation environment for secure and low cost verification of autonomous systems. Given spesific inputs, it allows the execution of meaningful scenarios designed to check that the system complies with the standards. It enables a test environment to be created to functionally validate the system.
• Virtual Architecture Development and Simulated Evaluation of Software Concepts The approach with its corresponding simulation and virtual validation framework FERAL (Framework for fast Evaluation on Requirements and Architecture Level) is a solution for virtual architecture development and simulated evaluation of software concepts. FERAL allows the design of virtual prototypes, which replace real prototypes by means of simulation and evaluate the impact of new architecture concepts in a cost-efficient manner. The solution enables simulation-based validation and the systematic assessment of design decisions at an early stage by coupling simulation models and simulators, existing code, and virtual hardware platforms.
• Software Component Testing
• Runtime Verification Based on Formal Specification
• Deductive Verification
• Formal Requirements Validation Requirements are formalized in a formal language, typically a temporal logic, and analyzed to find defects in the specification such as inconsistencies, incompleteness, errors, unrealizability.
• Model Checking Given a formal model of the system and a formal specification of the properties, model checking provides automated procedures to prove or disprove that the system satisfies the property. This is achieved via an exhaustive examination of the state space.
• Theorem Proving and SMT Solving
• Model-Based Design Verification Model-Based Design (MBD) provides a basis for machine-assisted verification of the system under development by the definition of models, supporting initial design decisions as well as enabling early discovering of errors. Models can be analysed with different MBD Verification methods.

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

There are currently no items in this folder.