D2.1 Requirements and Specification - CORBYS

Recommendations

Info

D2.1 Requirements and Specification control higher levels, the information that the system retrieves comes from both directions. Reason / Comments: Indicative priority Mandatory 7.8.1.2 Interfaces Requirement No. CAL7 Name: Adaptive parameters Description: From real-time control modules the sub-system will retrieve information about the status of the control units and their performance while from higher level cognitive control modules it will retrieve information about the interpreted sensory data, control requests, desired control behaviour and etc. Reason / Comments: Indicative priority Mandatory 7.8.1.3 Operating environment Requirement No. CAL8 Name: Real-time environment Description: Since the module has to be able to provide real-time update of low-level controllers with control parameters, referent values, actions and others it is necessary that the module operates in real time. A real time framework such as OROCOS or similar will be used. Reason / Comments: Indicative priority Mandatory 7.8.1.4 Resources Requirement No. CAL9 Name: Real time hardware Description: In order to achieve real-time functionality. Reason / Comments: Indicative priority Mandatory 7.8.2 Non Functional Requirements 7.8.2.1 Performance Requirement No. CAL10 Name: Hard real-time operation Description: Hard real time operation will be tested first in laboratory environment and later in evaluation phase. Reason / Comments: Indicative priority Mandatory 7.8.2.2 Safety and reliability Requirement No. CAL11 Name: Safety checking of control parameters Description: The layer will feed in control parameters to low-level control modules and therefore a safety 84
D2.1 Requirements and Specification checking of control values has to be implemented. This will be agreed with partners that are involved in this task. Reason / Comments: Indicative priority Mandatory 8 System Integration and Functional Testing (WP8, SINTEF) � Sub-System Conformance Testing (TASK 8.1, SCHUNK) � Integration of Sub-Systems (TASK 8.2, SINTEF) � Conformance Testing of integrated System (TASK 8.3, SINTEF) Work Package 8 deals with the integration of CORBYS hardware and software subsystem components into a complete, operational system that can eventually be evaluated in clinical trails in WP 9. System integration is the process of bringing together subsystem functionalities and ensuring that they work together as a system. A prerequisite in order to obtain a working system is obviously that the intended functionalities of all subsystem components have been successfully realised and verified (tested) before the integration with other subsystems takes place. Without such subsystem testing, many errors in the complete system must be anticipated: The origin can be hard to identify in a complex system, the debugging can be intricate, and also the subsystem responsibility easily becomes fragmented among the contributing partners. The Work Package is therefore defined to contain three main activities (tasks). First, it is verified through testing in Task 8.1 that the sub-system components have been developed according to the target specifications. Only sub-system components that are deemed to conform to the targets are then cleared for the next stage, the integration of sub-systems into an integrated system (Task 8.2). Finally, when the system has become as complete as time and the supply of sub-systems allows, the integrated system will be subject to system level conformance testing in Task 8.3 to verify the overall system functionality with respect to target specifications. 8.1 Conformance testing on subsystem and system level Relevant tasks: � Sub-System Conformance Testing (TASK 8.1, SCHUNK) � Conformance Testing of integrated System (TASK 8.3, SINTEF) 8.1.1 Functional Requirements 8.1.1.1 Processes Inputs Requirement No. CTREF1 Name: Functional target specification of all sub-system components Description: Functional target specifications will be established, and will define metrics and procedures to be used in the system integration stage Reason / Comments: Indicative priority Mandatory Requirement No. CTREF2 Name: Documentation of all sub-system components Description: The documentation required in order to integrate sub-system components into a complete system, such as: 85
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: D2.1 Requirements and Specification
Page 93: D2.1 Requirements and Specification
Page 145 and 146:
Page 147 and 148:
Page 149 and 150:
Page 151 and 152:
Page 153 and 154:
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

Create successful ePaper yourself

Delete template?

Save as template?