D2.1 Requirements and Specification - CORBYS

Recommendations

Info

D2.1 Requirements and Specification � Functional specification � Mechanical design drawings � User manual � Source code � Interface definitions � Installation guidelines Reason / Comments: Indicative priority Mandatory Requirement No. CTREF3 Name: Hand-over of components from sub-system developers to system integrators Description: The hardware and software components must be made available for the system integration partners Reason / Comments: Must plan for a component hand-over to WP 8 partner. Typically, this can be a visit of the sub-component partner to perform the installation and to verify that the system works as expected in the new environment Indicative priority Mandatory Requirement No. CONF1 Name: Definition of test parameters and test rig setups. Description: The finalised robotic system including mobile platform and the powered orthosis demonstrator need to be tested according to the specifications. A scenario and use case profile with a specialised test rig design is to be detailed. Reason / Comments: Indicative priority Mandatory Processing Requirement No.: CTREF4 Name: Conformance testing requirements must be established Description: Predefined test methodologies based on predefined test metrics must be established. Reason / Comments: Indicative priority Mandatory Requirement No.: CTREF5 Name: Identification of test metrics and procedures for conformance testing Description: Shared metrics for approving that a system or sub-system conforms to target specifications must be established. Typically, these standards will be defined between the partners handing over and receiving sub-systems, and will vary and be adapted to the nature of the system or sub-system in question. Reason / Comments: Indicative priority Mandatory Requirement No.: CTREF6 Name: Conformance testing parameters – minimum requirements for all testing Description: Test plans shall as a minimum contain the following test items: � Definition of test environment (site) and test personnel (partners) � Conformance to interface definitions � Conformance to functional requirements � Conformance to performance related requirements (these might preferably be carried out by the sub-system developer before the integration stages) � Conformance to safety/ hasard requirements � Conformance to documentation requirements Reason / Comments: 86
D2.1 Requirements and Specification Indicative priority Mandatory Requirement No.: CTREF7 Name: Conformance testing test protocol design Description: Test plans shall have unique definition of test objects (physical components shall be uniquely marked and software shall have correct version numbering). It shall further contain information about test site, test date and test personnel The test protocol when feasible will be designed with the following information for each test item: � Unique test item number � Description of test activity � Description of expected test result (which should be in accordance with target specifications) � Check box field for entering test result with the following alternatives: Passed/Failed � Field for entering test observation (in particular observations when the “Failed” box was checked. Reason / Comments: Indicative priority Mandatory Requirement No.: CONF2 Name: Mechanical and electrical design of necessary test rigs. Description: Rigs and setups to test actuators of orthosis through and mobile manipulator need mechanical design, bill of materials, electrical design and software structure. Reason / Comments: Indicative priority Mandatory Requirement No.: CONF3 Name: Production of test rigs Description: Manufacturing and assembly, cabling, functional test, software design for test procedures. Reason / Comments: Indicative priority Mandatory Requirement No.: CONF4 Name: Sensor verification Description: Sensor function will be verified with third party measurement techniques and third party sensors. Options for calibration and necessary maintenance intervals will be presented. Reason / Comments: Indicative priority Mandatory Output Requirement No.: CTREF8 Name: Sub-system test reports from conformance testing Description: For CORBYS sub-systems, the results of conformance testing will be stored as project internal development documentation. Reason / Comments: Indicative priority Mandatory Requirement No.: CONF5 Name: Data sheet and measurement/test protocols Description: Conformance with requirements and specifications has been proven with a final data sheet 87
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: D2.1 Requirements and Specification
Page 95: D2.1 Requirements and Specification
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?