Medspiration â System Requirements Document - Data User Element
Medspiration â System Requirements Document - Data User Element
Medspiration â System Requirements Document - Data User Element
Create successful ePaper yourself
Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.
<strong>Medspiration</strong><br />
<strong>System</strong> <strong>Requirements</strong> <strong>Document</strong><br />
3.3.5 <strong>System</strong> controller at Ifremer<br />
MED-SOC-RS-001_1<br />
Issue F<br />
<strong>System</strong><br />
controller<br />
operation log<br />
system<br />
Control<br />
processing flow<br />
Control<br />
data flow<br />
<strong>System</strong><br />
monitoring<br />
Synchronize<br />
with<br />
GHRSST-PP<br />
Trigger<br />
Chain<br />
Exchange<br />
data<br />
Exchange<br />
MMR-FR<br />
Exchange<br />
error messages<br />
Figure 3-9. The controller for the <strong>Medspiration</strong> processor at IFREMER<br />
3.3.5.1 <strong>Data</strong>flow control<br />
SR.CTR.0110/I The system controller shall ensure that all data and messages are<br />
correctly transmitted and received within the overall system.<br />
The <strong>Medspiration</strong> team recommends that the requirements listed below are applied on<br />
each site receiving or transmitting data. We also suggest these requirements to be<br />
extended at the GHRSST-PP level to ensure overall consistency of the global system.<br />
SR.CTR.0120/I The system shall control the integrity of all binary data received from a<br />
remote site using appropriate error control code (md5 or crc checksum) when available.<br />
An error control code shall be associated with all the L2P files sent from CMS to<br />
IFREMER.<br />
SR.CTR.0130/I The system shall control the validity of each XML formatted message<br />
(Operation or error log entry) received from a remote site. The DTD associated with each<br />
XML file will be used to validate the messages.<br />
This requirement may be extended at GHRSST-PP level to MDB and MMR messages.<br />
SR.CTR.0140/I Retransmission shall be requested to the sender for each rejected<br />
datafile or message on integrity or format control.<br />
SR.CTR.0150/I Acknowledgement shall be transmitted by the receiver to the sender for<br />
data files.<br />
This may be very useful for the sender to clean its sending spooler.<br />
© 2004 SOC Page 53 of 193
Change language