D2.1 Requirements and Specification - CORBYS
D2.1 Requirements and Specification - CORBYS
D2.1 Requirements and Specification - CORBYS
Create successful ePaper yourself
Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.
<strong>D2.1</strong> <strong>Requirements</strong> <strong>and</strong> <strong>Specification</strong><br />
Description: The physical location where the system integration activity takes place must be decided.<br />
Reason / Comments: Alternatively, at least a plan for moving the system from one site to other must be fixed.<br />
Indicative priority M<strong>and</strong>atory<br />
Requirement No.: SIREF5<br />
Name: System integration process for installing new sub-components<br />
Description: New sub-system components cleared for system integration will be installed in a joint effort<br />
of the sub-system developer <strong>and</strong> the system integrator.<br />
Reason / Comments: From case to case, it will have to be decided what is the most practical. Examples of joint<br />
efforts can range from remote installation of software or physical face to face meetings to<br />
install physical components.<br />
Indicative priority M<strong>and</strong>atory<br />
Requirement No.: SIREF6<br />
Name: System integration functionality testing should be carried out when new components have<br />
been installed<br />
Description: Frequent testing of the system in the integration stages is important in order to verify that<br />
new components do not give rise to problems in or conflicts with other sub-systems<br />
Reason / Comments:<br />
Indicative priority M<strong>and</strong>atory<br />
Requirement No.: SIREF7<br />
Name: Fine-tuning <strong>and</strong> optimisation of functionality of the integrated system <strong>and</strong> Sub-system to<br />
sub-system optimisation<br />
Description: Many system features can only be implemented <strong>and</strong> tested when integrated as a complete<br />
system. This will be a combined effort of the system integrators <strong>and</strong> the developers of the<br />
sub-systems. System integrators must ensure that time <strong>and</strong> access are given for sub-system<br />
developers to meet <strong>and</strong> improve the combined, integrated system<br />
Reason / Comments:<br />
Indicative priority M<strong>and</strong>atory<br />
Requirement No.: SIREF8<br />
Name: Physical design process of integrated system<br />
Description: Physical design <strong>and</strong> construction shall be based on dimensionally correct models developed<br />
using 3D CAD tools such as SolidWorks or ProEngineeer.<br />
For moving components, the system shall be evaluated/inspected at all end points to detect<br />
potential physical conflicts<br />
Reason / Comments: Discuss with other partners which CAD system <strong>and</strong> exchange format to use<br />
Indicative priority M<strong>and</strong>atory<br />
Output<br />
Requirement No.: SIREF9<br />
Name: System integration final output<br />
Description: The System Integration activity shall have as an output an integrated system that passes the<br />
final conformance tests of Task 8.3<br />
Reason / Comments:<br />
Indicative priority M<strong>and</strong>atory<br />
8.2.1.2 Interfaces<br />
Requirement No.: SIREF10<br />
Name: System integration status <strong>and</strong> issues update<br />
Description: Status <strong>and</strong> issues in integration shall be made available to all project partners by<br />
91
Change language