UC11_R_31 https://repo.valu3s.eu/use-cases/uc11-automated-robot-inspection-cell-for-quality-control-of-automotive-body-in-white/requirements/uc11_r_31 https://repo.valu3s.eu/@@site-logo/logo_valu3s_green_transparent.png UC11_R_31 Requirement ID 31 Requirement Textual Description Fault types as labels must be defined. e.g., 0:non-fault; 1: sensor fault; 2: motor fault; 3: SW fault; 4: PLC fault; 5: planning fault; 6: model fault. Requirement Type Safety Requirement Test Cases Requirement Test Cases List UC11_TC_31 - ML Techniques Preprocessing & Training: * Pre-condition: The system is up and running in operational mode. * Input conditions / steps: Data from the system is continuously collected and fed into ML process block. * Expected outcome: Pre-determined ML techniques and models are executed, output networks are generated and made available for inference step." 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.
