Requirement Test Cases

Requirement Test Cases List

• UC14_TC_2 * Pre-conditions: Replication of embedded systems (CardioWheel and CardioGW) and implement code base using formal framework MARS.; System is running, requesting identification tasks when ECG is detected and monitoring its related cognitive state. * Inputs: Simulated/real-time ECG. * Expected outcome: Model representations and stored features are cryptographically secured. Data received and produced at transmission endpoints is encrypted and so impossible to interpret by third parties.
• UC14_TC_12 * Pre-conditions: Access CardioWheel - CardioGW communication channel. * Inputs/steps: Sniff data being transmitted. * Expected outcomes: retrieved data is useless, it is encrypted end-to-end and cannot be recovered by third parties.

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.