D2.1 Requirements and Specification - CORBYS
D2.1 Requirements and Specification - CORBYS
D2.1 Requirements and Specification - CORBYS
You also want an ePaper? Increase the reach of your titles
YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.
<strong>D2.1</strong> <strong>Requirements</strong> <strong>and</strong> <strong>Specification</strong><br />
<strong>and</strong> test protocols<br />
Reason / Comments:<br />
Indicative priority M<strong>and</strong>atory<br />
8.1.1.2 Interfaces<br />
Requirement No.: CTREF9<br />
Name: Evaluation of sub-system conformance testing outcomes<br />
Description: For sub-system conformance testing, the outcomes will be determined as a result of<br />
conformance testing involving the partners delivering (technology development work<br />
packages) <strong>and</strong> receiving technology (system integrators)<br />
Reason / Comments:<br />
Indicative priority M<strong>and</strong>atory<br />
Requirement No.: CTREF10<br />
Name: Sub-system components not meeting all conformance testing requirements<br />
Description: It must be anticipated that not all sub-systems will meet all conformance test requirements.<br />
In these cases, there will have to be a discussion about the severity of the failed items, the<br />
possibility to correct these items at a later stage (during integration stages), <strong>and</strong> the overall<br />
system consequences of not integrating the component in question.<br />
Reason / Comments:<br />
Indicative priority M<strong>and</strong>atory<br />
Requirement No.: CTREF11<br />
Name: Evaluation of integrated system conformance testing outcomes<br />
Description: For integrated system conformance testing, the outcomes will be determined as a result of<br />
conformance testing involving WP 8 (system integrators) on one side <strong>and</strong> WP 9 (clinical<br />
evaluation) partners<br />
Reason / Comments:<br />
Indicative priority M<strong>and</strong>atory<br />
8.1.1.3 Roles <strong>and</strong> responsibilities<br />
Requirement No.: CTREF12<br />
Name: Sub-system responsibility<br />
Description: The sub-system functionality <strong>and</strong> performance is the responsibility of the partner(s)<br />
developing the sub-system during all testing <strong>and</strong> integration stages.<br />
Reason / Comments: After the integration stage, the responsibility will have to be shared with all partners, but all<br />
partners have responsibility to offer <strong>and</strong> provide guidance, service <strong>and</strong> other assistance<br />
during the integration <strong>and</strong> evaluation stages<br />
Indicative priority M<strong>and</strong>atory<br />
8.1.1.4 Operating environment<br />
Requirement No.: CTREF13<br />
Name: <strong>CORBYS</strong> gait system target operating environment<br />
Description: The <strong>CORBYS</strong> gait rehabilitation system will be designed to work in typical health<br />
institution environments.<br />
Reason / Comments: The <strong>CORBYS</strong> gait rehabilitation system will not be suitable for outdoor all-weather usage.<br />
Indicative priority M<strong>and</strong>atory<br />
Requirement No.: CTREF14<br />
Name: <strong>CORBYS</strong> gait system target operating mode (ambulatory/not ambulatory)<br />
88
Change language