Medspiration â System Requirements Document - Data User Element

More documents

Recommendations

Info

Medspiration MED-SOC-RS-001_1 System Requirements Document Issue F SR.CTR.0160/I Corrupted L2P files by the receiver shall be deleted with all their related information (error control code) before retransmission is requested. SR.CTR.0170/I When transmitting files by ftp, the error control code (md5 or crc checksum, having a fixed size) delivered with a datafile shall be used as a flag by the sender indicating the transfer is completed. The receiver shall assume the transmission is completed when reading the related error control code. Consequently, the error control codes shall be sent after the related data file transmission is completed. SR.CTR.0180/I The selected on-the-shelf ftp tools used by Medspiration shall feature resume facilities in order to optimize the bandwidth and the delivery time in case of interrupted transmission. SR.CTR.0190/I On-the-shelf dissemination systems such as DODS or Live Access Server are out of the scope of these requirements. 3.3.5.2 Processing flow control SR.CTR.0210/I The system controller shall trigger, schedule and sequence all the processes runned on its own site and generate appropriate error and operation messages. SR.CTR.0220/I The scope of the processing flow control shall be limited to IFREMER site processing. Other production sites (CMS, SOC) shall rely on their own local practices and facilities for the control and the sequencing of their processes. 3.3.5.3 Triggering the processing SR.CTR.0230/I The system controller shall provide a poll mechanism to trigger the relevant processing – referred to as ‘data-driven tasks’ - on new incoming data. Data-driven tasks include : • L2P archiving • L2P delivery (ftp push) to operational users (GHRSST or EU) • L4 delivery (ftp push) to operational users (EU) • MMR generation and delivery SR.CTR.0240/I The system controller shall provide a scheduling mechanism to trigger processing on a periodic basis, referred to as ‘time driven’ tasks. © 2004 SOC Page 54 of 193
Medspiration System Requirements Document Time-driven tasks include : • UHR/L4 product generation MED-SOC-RS-001_1 Issue F • MDB records generation • Backup operations SR.CTR.0250/I Some system operation shall be manually triggered by the system operators. This addresses mainly the offline storage or restoration of the historical data. 3.3.5.4 Chaining the processes SR.CTR.0260/I The system controller shall appropriately chain the processes when sequencing is required. 3.3.5.5 Operation log system SR.CTR.0310/I The system controller shall centralize, in a system log, all relevant operations and errors occurring within the Medspiration system (SOC, IFREMER, CMS). SR.CTR.0320/I The log information shall be archived in an appropriate way to extract relevant operation statistics about the Medspiration system operations. These statistics shall then be used in the monthly operation reports delivered to ESA. 3.3.5.6 System monitoring SR.CTR.0410/I The system controller shall report to the staff in charge of the system operations all relevant events or error occurring within the Medspiration system through a graphical user interface. SR.CTR.0420/I The log information shall be easily readable by the technicians in charge of the system monitoring. SR.CTR.0430/I Failures requiring human intervention shall be highlighted. 3.3.5.7 Synchronization with GHRSST-PP SR.CTR.0510/I The system controller shall ensure all synchronization procedures with © 2004 SOC Page 55 of 193
Page 1 and 2:
Medspiration System Requirements Do
Page 3 and 4: Medspiration System Requirements Do
Page 5 and 6: Medspiration MED-SOC-RS-001_1 Syste
Page 53: Medspiration System Requirements Do
Page 105 and 106:
Medspiration MED-SOC-RS-001_1 Syste
Page 107 and 108:
Page 109 and 110:
Page 111 and 112:
Page 113 and 114:
Page 115 and 116:
Page 117 and 118:
Page 119 and 120:
Page 121 and 122:
Page 123 and 124:
Page 125 and 126:
Page 127 and 128:
Page 129 and 130:
Page 131 and 132:
Page 133 and 134:
Page 135 and 136:
Page 137 and 138:
Page 139 and 140:
Page 141 and 142:
Page 143 and 144:
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:
show all

Medspiration â System Requirements Document - Data User Element

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?

Medspiration â System Requirements Document - Data User Element