Requirement Test Cases

Requirement Test Cases List

• UC4_TC_3 Turn of air pressure (physical manipulation) "Test case: Handling and gripping of product/parts: "Turn of air pressure" (physical manipulation) # Preconditions: All components turned on # Input conditions / steps: turn off compressor before and during gripping # Expected results: before = part will not be gripped, recognizede by prox. sensor / during gripping = part will stay gripped due to decoupled pressure line (security mechanism) but cannot gripp next part"
• UC4_TC_4 Don't activate gripper in program (physical manipulation) "Test case: Handling and gripping of product/parts: "Don't activate gripper in program" (physical manipulation) # Preconditions: All components turned on # Input conditions / steps: deactivate gripper in program # Expected results: Gripper can not pic part, failed gripping is recognized by proximity sensor"
• UC4_TC_5 Remove product / part before gripping (physical manipulation) "Test case: Handling and gripping of product/parts: "Remove product / part before gripping" (physical manipulation) # Preconditions: All components turned on # Input conditions / steps: Remove product / part before gripping # Expected results: Gripper can not pic part, missing part is recognized by proximity sensor"
• UC4_TC_6 Manipulate proximity sensor (data manipulation) "Test case: Handling and gripping of product/parts: "Manipulate proximity sensor" (data manipulation) # Preconditions: All components turned on # Input conditions / steps: Change proximity sensor settings to ""no approximation detected"" though part has been gripped # Expected results: ... ??? not yet implemented"
• UC4_TC_7 Remove product from simulation (failure simulation) "Test case: Handling and gripping of product/parts: "Remove product from simulation" (failure simulation) # Preconditions: Running simulation with all components # Input conditions / steps: Manipulate / remove parts in simulation # Expected results: … ??? (robot should stop immediately)"
• UC4_TC_8 Do not grip in simulation (failure simulation) "Test case: Handling and gripping of product/parts: ""Do not grip in simulation"" (failure simulation) # Preconditions: Running simulation with all components # Input conditions / steps: Manipulate / turn off gripper in simulation # Expected results: … ??? (robot should stop immediately)"
• UC4_TC_9 Unintentionelly by human worker (physical manipulation) "Test case: Knocking off product/part: ""Unintentionelly by human worker"" (physical manipulation) # Preconditions: Gripper pics part # Input conditions / steps: Human knocks off the product/part from magnetic gripper # Expected results: Robot stops due to proximity sensor recognize missing part"
• UC4_TC_10 Manipulate proximity sensor (data manipulation) "Test case: Knocking off product/part: ""Manipulate proximity sensor"" (data manipulation) # Preconditions: Gripper pics part # Input conditions / steps: Change proximity sensor settings to ""no approximation detected"" after gripping # Expected results: Robot stops due to proximity sensor recognize missing part"
• UC4_TC_11 Manipulate proximity sensor (failure simulation) "Test case: Knocking off product/part: ""Manipulate proximity sensor"" (failure simulation) # Preconditions: Gripper pics part in simulation # Input conditions / steps: Remove product from simulation during handling process # Expected results: … ??? (robot should stop immediately)"
• UC4_TC_14 IoT-Gateway manipulation "Test case: Data manipulation during data collection / transfer: ""IoT-Gateway manipulation"" # Preconditions: Data connection working # Input conditions / steps: IoT-gateway: interrupt data transfer / signal transfer a/o manipulate value e.g. through multiplicaton with random factor # Expected results: … ??? (still to be elaborated and decided)
• UC4_TC_15 HTTP-Server manipulation "Test case: Data manipulation in human-robot-interaction: ""HTTP-Server manipulation"" # Preconditions: Data connection working # Input conditions / steps: HTTP-Server (REST): interrupt data transfer / signal transfer a/o manipulate value e.g. through multiplicaton with random factor # Expected results: … ??? (not yet elaborated)"
• UC4_TC_16 HTTP-Client manipulation "Test case: Data manipulation in human-robot-interaction: ""HTTP-Client manipulation"" # Preconditions: Data connection working # Input conditions / steps: HTTP-Client (REST): interrupt data transfer / signal transfer a/o manipulate value e.g. through multiplicaton with random factor # Expected results: … ??? (not yet elaborated)"

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.