UC11_R_52 https://repo.valu3s.eu/use-cases/uc11-automated-robot-inspection-cell-for-quality-control-of-automotive-body-in-white/requirements/uc11_r_52 https://repo.valu3s.eu/@@site-logo/logo_valu3s_green_transparent.png UC11_R_52 Requirement ID 52 Requirement Textual Description Monitoring and inspection of dense/sparse traffic flow than expected in the middleware Requirement Type Cybersecurity Requirement Test Cases Requirement Test Cases List UC11_TC_8 *Precondition: This system follows a predefined trajectory. *Input Condition/steps: At runtime, a certain traffic flow occurs in the system depending on the workload. During the attack, this data flow is increased and due to this the expected data is lost or this data flow is decreased and due to this the unexpected data flood. *Expected Results: The traffic flow in the system is controlled according to the reference interval and control mechanism catches the abnormality. 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.
