D2.1 Requirements and Specification - CORBYS

Recommendations

Info

D2.1 Requirements and Specification � Depends on CORBYS Functional Specification � Depends on CORBYS overall output 9 Evaluation (WP9, IRSZR) � Specification of evaluation methodology, benchmarking, metrics, procedures and ethical assurance (TASK 9.1, UR) � Training on CORBYS system (TASK 9.2, IRSZR) � Continuous assessment of the technology under the development (TASK 9.3, IRSZR) � Evaluation of the researched methods on autonomous robotic system (TASK 9.4, UB) � Evaluation and feedback to development (TASK 9.5, NRZ) 9.1 Evaluation methodology, benchmarking, metrics, procedures and ethical assurance (Task 9.1, UR) Relevant task: � Specification of evaluation methodology, benchmarking, metrics, procedures and ethical assurance (Task 9.1) 9.1.1 Functional Requirements 9.1.1.1 Processes Inputs Requirement No. UIREF1 Name: Functional Specification of CORBYS Description: This will inform the identification of metrics and procedures to be used in the evaluation methodology Reason / Comments: Indicative priority Mandatory Requirement No. UIREF2 Name: Overall output of CORBYS project Description: The outcomes of the project will be used in the identification of appropriate existing systems to be used as benchmarks Reason / Comments: Indicative priority Mandatory Processing Requirement No.: UIREF3 Name: Formulation of evaluation methodology Description: To follow established methodologies (e.g. UI-REF, Badii 2008) for identification of evaluation metrics and procedures i.e. requirements UIREF4, UIREF5 and UIREF6 Reason / Comments: 94
D2.1 Requirements and Specification Indicative priority Mandatory Requirement No.: UIREF4 Name: Identification of benchmarks Description: For the purpose of the benchmarking exercise, the CORBYS system viewed generically as a meta-controller controlling semi-autonomous sub-systems can be specified with respect to the identified terms of reference so as to be able to conduct comparative studies with existing meta-controllers that can be identified as comparable with respect to the established terms of reference. Thus the work entails the establishment of meta-controller comparators so that the performance of the CORBYS controller can be evaluated and compared with other comparable meta-controllers within a formal benchmarking framework. Reason / Comments: Indicative priority Mandatory Requirement No.: UIREF5 Name: Identification of evaluation metrics and procedures Description: To identify the evaluation metrics and specify the evaluation procedures to be followed in CORBYS. Reason / Comments: Indicative priority Mandatory Requirement No.: UIREF6 Name: Ethical assurance Description: To identify the evaluation metrics and specify the evaluation procedures to be followed in CORBYS in the context of ethical assurance and user involvement. Reason / Comments: Indicative priority Mandatory Output Requirement No.: UIREF7 Name: Set of metrics, procedures, benchmarks, ethical assurance and evaluation methodology Description: Comprehensive list of identified evaluation metrics and procedures to be followed in CORBYS. For benchmarking, the terms of reference by referring to generic properties of the required control performance: 1. Dynamicity: typical real-time response (e.g. in ms) 2. Complexity of Control: Number of states of each sub-system and number of states of control transition dynamics between the two systems 3. Required Control Envelope: Number of spatio-temporal dimensions of required control, e.g. linear motion, rotational motion, 2D, 3D, etc 4. Delivered Performance Envelope: Dynamicity, complexity and dimensionality levels of the controller Reason / Comments: Indicative priority Mandatory 9.1.1.2 Interfaces Requirement No.: UIREF8 Name: Evaluation of CORBYS outcomes Description: The formulated evaluation methodology, identified benchmarks, metrics and procedures will be used in the Evaluation WP 95
Page 1 and 2:
CORBYS Cognitive Control Framework
Page 3 and 4:
D2.1 Requirements and Specification
Page 5 and 6:
Page 7 and 8:
Page 9 and 10:
Page 11 and 12:
Page 13 and 14:
Page 15 and 16:
Page 17 and 18:
Page 19 and 20:
Page 21 and 22:
Page 23 and 24:
Page 25 and 26:
Page 27 and 28:
Page 29 and 30:
Page 31 and 32:
Page 33 and 34:
Page 35 and 36:
Page 37 and 38:
Page 39 and 40:
Page 41 and 42:
Page 43 and 44:
Page 45 and 46:
Page 47 and 48:
Page 49 and 50:
Page 51 and 52:
Page 53 and 54: D2.1 Requirements and Specification
Page 103: D2.1 Requirements and Specification
Page 155 and 156:
Page 157 and 158:
Page 159 and 160:
Page 161 and 162:
Page 163 and 164:
Page 165 and 166:
Page 167 and 168:
Page 169 and 170:
Page 171 and 172:
Page 173 and 174:
Page 175 and 176:
Page 177 and 178:
Page 179 and 180:
Page 181 and 182:
Page 183 and 184:
Page 185 and 186:
Page 187 and 188:
Page 189 and 190:
Page 191 and 192:
Page 193 and 194:
Page 195 and 196:
Page 197 and 198:
Page 199 and 200:
Page 201 and 202:
Page 203 and 204:
Page 205 and 206:
Page 207 and 208:
Page 209:
show all

D2.1 Requirements and Specification - CORBYS

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?