Run Time Verification Based on Formal Specification

Method Purpose Short description of the method's purpose and main benefits

Method description A detailed description of the method

-Robot trajectory test
* preconditions: Digital twin of the system should be modelled in Gazebo environment.
* input conditions / steps: Trajectory created in digital twin which can control vehicle parts without collision and virtualpictures(2D) should be present.
* expected results: Existence control of minimum %95 parts of vehicle in less than 25 minutes and in each trajectory point minimum %15 of each part must be visible.

-Human presence test
* preconditions: Two cameras enabling to capture view from both sides of each robot.
* input conditions / steps: Human's presence in robots' work area.
* expected results: Adjustment of robot speed depending on human distance from robot.

Method Strengths A listof the strengths of the method

Verification, during execution time, of properties of the target system that are hard or impossible to capture during design time
Lightweight scalable application of formal methods
Rigorous specification of monitoring properties
Possibility of increasing of the overall system reliability without compromising security and safety aspects, via a correct generation of monitors

Method Limitations The limitations of the method

The use of runtime monitoring solutions inevitably implies extra overheads in the target system
It is not always easy to define formal specifications (need specialized expertise from users)
A black box specification requires to know how an internal condition (e.g., a fault) manifests itself on the observable interface of the system/component. Assumption-based RV requires a formal specification of the assumption.

Method References Bibliography references to papers about the method.

Method Dimensions

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)

Relations

Related Methods A method could be related to other methods.

Tools A method can use zero or more tools.

Part Method A method (when it is a combination: Combination of method artefact that is a specialization of a V&V Method) could be composed of a set of V&V Methods.

Test Case or Verification and Validation activity Test Case or V&V activity performed in a Use Case. We will link to the method to the test cases where the method is used.

Standards A method can be linked with standards.

Context

Workflow

Contents

There are currently no items in this folder.