System Requirement Document (SRD) - H-SAF

H-SAFSystem Requirement DocumentDoc. No: SAF/HSAF/SRD/2.1Issue: Version 2.1Date: 20/06/2008Page: 1/102Hydrology SAFSystem Requirement DocumentReference Number:SAF/HSAF/SRD/2.1Issue/Revision Index: Issue 2.1Last Change: 20/06/2008

H-SAFSystem Requirement DocumentDoc. No: SAF/HSAF/SRD/2.1Issue: Version 2.1Date: 20/06/2008Page: 3/102Version 1.1 14/06/2007 Updated Release prepared for V1CP:Correction of pagination and editorial adjustment asacknowledgement of RID 102 and RID 111Review of Applicable Documents list and Reference Documentslist as acknowledgement of RID 114: transfer of items to thesecond list as [RD 25] and [RD 26]Insertion of missing verification method for requirement SR-00010-FUN-GEN (acknowledgement of RID 115)Insertion of a clarification on hydrological models inputresolution. This acknowledges RID 116Modification of requirement SR-11010-FUN-ACQ for the localacquisition of ERS 1/2 data to Soil Moisture subsystem,described in Table 6 but not still present as a requirement. (thisacknowledges RID 117 and RID 29).Insertion of a clarification about source data and auxiliary data inthe Functional Requirements section, to avoid misunderstandingin the comprehension of Table 6. (Acknowledgement of RID118).Version 2.0 08/02/2008 New baseline for CDR. Document preparation includes the followingupdates:Modification of SR-10020-FUN-ACQ with insertion of aclarification about erroneous data and its management, asacknowledgement of RID 27.Modification of SR-10030-FUN-ACQ for a better specification ofarchived satellite data description, as acknowledgement of RID28Completion of Product Output format list for dissemination (thisacknowledge RID 32).Update and further details addition on timeliness fordissemination to NRT users is provided (this acknowledge RID112).

H-SAFSystem Requirement DocumentDoc. No: SAF/HSAF/SRD/2.1Issue: Version 2.1Date: 20/06/2008Page: 4/102Version 2.1 20/06/2008 Acknowledgements of CDR RIDs:Clarifications and corrections on satellite data interfaces, inSection 2.5 (RID 2)Drop of requirement SR-91010-PER-ACQ (RID 5)Modification of Table 4 : completion of interface descriptionand specification of baseline interface for satellite dataresources (RID 3 and RID 32)Correction of Section 1.4.1 “Applicable Documents” (RID30)Completion of Table 1 with missing roles of project partners(RID 31)Completion of glossary (RID33)Reformulation of requirements SR-13070-FUN-ACQ andSR-54150-FUN-DIS; drop of requirement SR-91010;editorial revision of all requirements (RID 34)Modification of Table 19 and insertion of necessaryexplanations (RID 35)

H-SAFSystem Requirement DocumentDoc. No: SAF/HSAF/SRD/2.1Issue: Version 2.1Date: 20/06/2008Page: 5/102DISTRIBUTION LISTCountry Organization Name ContactAustria ZAMG Veronika Zwatz-Meise zwatz-meise@zamg.ac.atZAMG Alexander Jann alexander.jann@zamg.ac.atTU-Wien / IPF Wolfgang Wagner ww@ipf.tuwien.ac.atTU-Wien / IPF Stefan Hasenauer sh@ipf.tuwien.ac.atBelgium IRM Emmanuel Roulin emmanuel.roulin@oma.beIRM Gaston Demaree gaston.demaree@oma.beECMWF Philippe Bougeault philippe.bougeault@ecmwf.intMatthias DruschKlaus Scipalmatthias.drusch@ecmwf.intklaus.scipal@ecmwf.intFinland FMI Pirkko Pylkko pirkko.pylkko@fmi.fiFMI Jarkko Koskinen jarkko.koskinen@fmi.fiFMI Jouni Pulliainen jouni.pulliainen@fmi.fiFMI Panu Lahtinen panu.lahtinen@fmi.fiTKK Juha-Petri Karna juha-petri.karna@tkk.fiSYKE Sari Metsämäki sari.metsamaki@ymparisto.fiFrance Météo France Jean-Christophe Calvet jean-christophe.calvet@meteo.frMétéo France Laurent Franchisteguy laurent.franchisteguy@meteo.frCNRS-CETP Mehrez Zribi mehrez.zribi@cetp.ipsl.frCNRS-CESBIO Patricia de Rosnay derosnay@cesbio.cnes.frGermany BfG Thomas Maurer thomas.maurer@bafg.deHungary OMSZ Eszter Lábó labo.e@met.huItaly USAM Massimo Capaldo m.capaldo@meteoam.itCNMCA Luigi De Leonibus l.deleonibus@meteoam.itCNMCA Costante De Simone c.desimone@meteoam.itCNMCA Francesco Zauli f.zauli@meteoam.itCNMCA Daniele Biron d.biron@meteoam.it

H-SAFSystem Requirement DocumentDoc. No: SAF/HSAF/SRD/2.1Issue: Version 2.1Date: 20/06/2008Page: 6/102Country Organization Name ContactCNMCA Davide Melfi d.melfi@meteoam.itCNMCA Attilio Di Diodato a.didiodato@meteoam.itCNMCA Lucio Torrisi l.torrisi@meteoam.itCNMCA Massimo Bonavita m.bonavita@meteoam.itCNMCA Adriano Raspanti a.raspanti@meteoam.itCNMCA Alessandro Galliani a.galliani@meteoam.itDPC Roberto Sorani hsaf.management@protezionecivile.itDPC Luca Rossi luca.rossi@protezionecivile.itDPC Silvia Puca silvia.puca@protezionecivile.itDPC Angela Corina angela.corina@protezionecivile.itDPC William Nardin william.nardin@protezionecivile.itCNR-ISAC Franco Prodi f.prodi@isac.cnr.itCNR-ISAC Bizzarro Bizzarri bibizzar@tin.itCNR-ISAC Alberto Mugnai a.mugnai@isac.cnr.itCNR-ISAC Vincenzo Levizzani v.levizzani@isac.cnr.itCNR-ISAC Francesca Torricella f.torricella@isac.cnr.itCNR-ISAC Stefano Dietrich s.dietrich@isac.cnr.itCNR-ISAC Francesco Di Paola francesco.dipaola@ifa.rm.cnr.itFerrara University Federico Porcu’ porcu@fe.infn.itFerrara University Davide Capacci capacci@fe.infn.itELSAG DATAMAT Flavio Gattari flavio.gattari@datamat.itELSAG DATAMAT Emiliano Agosta emiliano.agosta@datamat.itPoland IMWM Piotr Struzik piotr.struzik@imgw.plIMWM Bozena Lapeta bozena.lapeta@imgw.plIMWM Jerzy Niedbala jerzy.niedbala@imgw.plIMWM Jaga Niedbala jaga.niedbala@imgw.plIMWM Monika Pajek monika.pajek@imgw.plIMWM Jakub Walawender jakub.walawender@imgw.plIMWM Jan Szturc jan.szturc@imgw.pl

H-SAFSystem Requirement DocumentDoc. No: SAF/HSAF/SRD/2.1Issue: Version 2.1Date: 20/06/2008Page: 7/102Country Organization Name ContactRomania NMA Andrei Diamandi diamandi@meteo.inmh.roNMA Simona Oancea simona.oancea@meteo.inmh.roSlovakia SHMÚ Ján Kaňák jan.kanak@shmu.skSHMÚ Marián Jurašek marian.jurasek@shmu.skSHMÚ Marcel Zvolenský marcel.zvolensky@shmu.skTurkey TSMS Fatih Demýr fdemir@meteor.gov.trTSMS Ali Umran Komuscu aukomuscu@meteor.gov.trTSMS Ibrahim Sonmez isonmez@meteor.gov.trTSMS Aydın Erturk agerturk@meteor.gov.trMETU Ali Unal Sorman sorman@metu.edu.trMETU Zuhal Akyurek zakyurek@metu.edu.trMETU Orhan Gokdemir orhan.gokdemir@gmail.comMETU Ozgur Beser beser@metu.edu.trITU Ahmet Oztopal oztopal@itu.edu.trAnadolu University Aynur Sensoy asensoy@anadolu.edu.trEUMETSAT Lorenzo Sarlo lorenzo.sarlo@eumetsat.intFrédéric GasigliaDominique FaucherJochen GrandellLothar Schüllerfrederic.gasiglia@eumetsat.intdominique.faucher@eumetsat.intjochen.grandell@eumetsat.intlothar.schueller@eumetsat.int

H-SAFSystem Requirement DocumentDoc. No: SAF/HSAF/SRD/2.1Issue: Version 2.1Date: 20/06/2008Page: 8/102TABLE OF CONTENTS1 Introduction .............................................................................................................. 111.1 Purpose of the Document .................................................................................... 111.2 Document Overview ............................................................................................ 111.3 Glossary .............................................................................................................. 121.4 References .......................................................................................................... 181.4.1 Applicable documents .................................................................................. 181.4.2 Reference documents .................................................................................. 182 General Description ................................................................................................. 192.1 Purpose of the H-SAF ......................................................................................... 192.2 Outlines of the H-SAF consortium ....................................................................... 202.3 Products / Deliveries of the H-SAF ...................................................................... 212.4 System Overview ................................................................................................ 242.5 General Constraints ............................................................................................ 263 Specific Requirements ............................................................................................. 293.1 Functional requirements ...................................................................................... 323.1.1 General Requirements ................................................................................. 323.1.2 Data Acquisition Requirements .................................................................... 373.1.3 Pre-Processing Requirements ..................................................................... 483.1.4 Product Generation Requirements ............................................................... 493.1.5 Hydrovalidation Processing Requirements .................................................. 603.1.6 Hydrovalidation Reporting Requirements ..................................................... 633.1.7 Archival Requirements ................................................................................. 653.1.8 Dissemination Requirements ....................................................................... 673.2 Reliability, Availability and Maintenance Requirements ...................................... 703.3 Operational Requirements .................................................................................. 713.4 Performance Requirements ................................................................................ 723.5 Portability Requirements ..................................................................................... 743.6 Resources Requirements .................................................................................... 763.7 Safety Requirements ........................................................................................... 773.8 Security Requirements ........................................................................................ 783.9 Documentation Requirements ............................................................................. 79

H-SAFSystem Requirement DocumentDoc. No: SAF/HSAF/SRD/2.1Issue: Version 2.1Date: 20/06/2008Page: 9/1024 TBDs/TBCs list ......................................................................................................... 795 Requirements traceability ........................................................................................ 795.1 System Requirements traceability to H-SAF Subsystems ................................... 795.2 System Requirements traceability to User Requirements ................................... 86

H-SAFLIST OF TABLESSystem Requirement DocumentDoc. No: SAF/HSAF/SRD/2.1Issue: Version 2.1Date: 20/06/2008Page: 10/102Table 1 Outlines of H-SAF Consortium ............................................................................. 21Table 2 Satellite-derived H-SAF products and satellite data sources ................................ 23Table 3 Backup products generated by a NWP model ...................................................... 23Table 4 H-SAF External Interfaces for Data Acquisition .................................................... 29Table 5 Classes of messages ............................................................................................ 33Table 6 H-SAF Data sources ............................................................................................. 36Table 7 Information related to satellite data ....................................................................... 38Table 8 Elements for soil moisture consistency control ..................................................... 55Table 9 Formats for Hydrovalidation processing ............................................................... 61Table 10 Timings for Hydrovalidation processing .............................................................. 62Table 11 Input data and parameters used by selected operational hydrological models ... 63Table 12 Payload information for Hydrovalidation reports ................................................. 64Table 13 Header information for Hydrovalidation reports .................................................. 64Table 14 Output data formats for Hydrovalidation reports ................................................. 65Table 15 Formats for data dissemination to Hydro Validation Subsystem ......................... 69Table 16 Time limits in products generation/dissemination ............................................... 74Table 17 Software coding languages ................................................................................ 76Table 18 System Requirements traceability vs H-SAF subsystems .................................. 85Table 19 System Requirements traceability vs User Requirements ................................ 101LIST OF FIGURESFigure 1: H-SAF system decomposition ............................................................................ 25

H-SAFSystem Requirement DocumentDoc. No: SAF/HSAF/SRD/2.1Issue: Version 2.1Date: 20/06/2008Page: 11/1021 Introduction1.1 Purpose of the DocumentThis document specifies the system requirements for the Hydrology SAF (H-SAF). Itfocuses mainly on product generation features, as the main objective of H-SAF system isto provide new satellite derived products in order to satisfy the needs of operationalhydrology. It identifies the requirements regarding products, functions, components andinterfaces as they have been described in the Project Plan [AD 2] and in the UserRequirement Document [AD 4]. It is the input for the architectural specification of thesystem, describedI in the System Design Document.In accordance with the project phasing depicted in the Project Plan, the SystemRequirements Document (SRD) has to be released in a preliminary version at theRequirement Review and in baseline version at the Preliminary Design Review.An updating of SRD (current document) has been made necessary as consequence ofURD and PP modifications. So this document should be considered as the new SRDbaseline version.1.2 Document OverviewThe H-SAF System Requirement Document is structured as follows:Chapter 1: Introduces the purpose of the document, provide the references and a list ofacronymsChapter 2: Gives a general description of H-SAF system in terms of purpose, outlines ofconsortium, products to be generated, system overview and general constraints.Chapter 3: Defines the system requirements classified in categories.Chapter 4: summarizes the TBDs and TBCs items, providing the responsible of each itemand a planned date for resolution.Chapter 5: Presents the traceability of the System Requirements versus the UserRequirements and the subsystems identified in the system design.The design methods here used are the UML 2.0 [RD 19], [RD 20], [RD 21], [RD 22]; alldiagrams and engineering notations intend to be compliant with standard there depicted.H-SAF System Engineering is compliant to the latest ECSS standards [RD 15], [RD 16],[RD 17], [RD 18] tailored to the H-SAF peculiarity.Most of ECSS standard founding principles have been adopted into H-SAF Engineering,such as the tailoring concept and the strict relationship between Software Engineering andSystem Engineering.

H-SAFSystem Requirement DocumentDoc. No: SAF/HSAF/SRD/2.1Issue: Version 2.1Date: 20/06/2008Page: 12/102These principles are particularly meaningful in the H-SAF context, since H-SAF is acomplex system into which the software layer is just one of many different layers buildingup the heterogeneous set-up.1.3 GlossaryAAPPADEOSALOSAMIRAMSRAMSR-EAMSU-AAMSU-BAPIASARASCATASIATDDATMSATOVSAUAVHRRBAMPRBfGBRDFBVACASECBACBSDCDACDDCDRCESBIOCETPCICMISCMPAVHRR and ATOVS Processing PackageAdvanced Earth Observation Satellite (I and II)Advanced Land Observing SatelliteAdvanced Microwave Imaging RadiometerAdvanced Microwave Scanning Radiometer (on ADEOS-II)Advanced Microwave Scanning Radiometer–- E (on EOS-Aqua)Advanced Microwave Sounding Unit–- A (on NOAA satellites and EOS-Aqua)Advanced Microwave Sounding Unit–- B (on NOAA satellites up to NOAA-17)Application Program(ming) InterfaceAdvanced SAR (on ENVISAT)Advanced Scatterometer (on MetOp)Agenzia Spaziale ItalianaAlgorithms Theoretical Definition DocumentAdvanced Technology Microwave Sounder (on NPP and NPOESS)Advanced TIROS Operational Vertical Sounder (on NOAA and MetOp)Anatolian UniversityAdvanced Very High Resolution Radiometer (on NOAA and MetOp)Bayesian Algorithm for Microwave Precipitation RetrievalBundesanstalt für GewässerkundeBi-directional Reflectance Distribution FunctionBoundary Value AnalysisComputer Aided System EngineeringComponent-Based ArchitectureComponent-based Software DevelopmentCommand and Data Acquisition (EUMETSAT station at Svalbard)Component Design DocumentCritical Design ReviewCentre ’'Etudes Spatiales de la BIOsphere (of CNRS)Centre d’études des Environnements Terrestres et Planétaires (of CNRS)Configuration ItemConical-scanning Microwave Imager/Sounder (on NPOESS)Configuration Management Plan

H-SAFSystem Requirement DocumentDoc. No: SAF/HSAF/SRD/2.1Issue: Version 2.1Date: 20/06/2008Page: 13/102CNMCA Centro Nazionale di Meteorologia e Climatologia AeronauticaCNR Consiglio Nazionale delle RicercheCNRM Centre Nationale de la Recherche Météorologique (of Météo-France)CNRS Centre Nationale de la Recherche ScientifiqueCOM Component Object ModelCORBA Common Object Request Broker ArchitectureCOTS Commercial-off-the-shelfCPU Central Processing UnitCR Component RequirementCRD Component Requirement DocumentCVERF Component Verification FileCVS Concurrent Versions SystemDCOM Distributed Component Object ModelDEM Digital Elevation ModelDFD Data Flow DiagramDMSP Defense Meteorological Satellite ProgramDOF Data Output FormatDPC Dipartimento della Protezione CivileDWD Deutscher WetterdienstE&T Education and TrainingEARS EUMETSAT Advanced Retransmission Service (station)ECMWF European Centre for Medium-range Weather ForecastsECSS European Cooperation on Space StandardizationEGPM European contribution to the GPM missionEOS Earth Observing SystemEPS EUMETSAT Polar SystemERS European Remote-sensing Satellite (1 and 2)ESA European Space AgencyEUR End-User RequirementsFMI Finnish Meteorological InstituteFOC Full Operational ChainFTP File Transfer ProtocolGEO Geostationary Earth OrbitGIS Geographical Information SystemGMES Global Monitoring for Environment and SecurityGOMAS Geostationary Observatory for Microwave Atmospheric SoundingGOS Global Observing SystemGPM Global Precipitation Measurement missionGPROF Goddard Profiling algorithm

H-SAFSystem Requirement DocumentDoc. No: SAF/HSAF/SRD/2.1Issue: Version 2.1Date: 20/06/2008Page: 14/102GTSGUIHMSHRUH-SAFHSBHTMLHTTPHUT/LSTHVHVRHYDROHYDROSHWICDICTIEEEIFSINFINWMIPFISACISOITITUJPSJ2EEKIDSKLOCKOMLAILANLEOLISLLSLOCLRITLSTMARSGlobal Telecommunication SystemGraphical User InterfaceHungarian Meteorological ServiceHydrological Response UnitSAF on support to Operational Hydrology and Water ManagementHumidity Sounder for Brazil (on EOS-Aqua)Hyper Text Markup LanguageHyper Text Transfer ProtocolHelsinki University of Technology / Laboratory of Space TechnologyHydrovalidation (referred to Hydro Validation Subsystem items, e.g.: reports, componentsetc.)Hydrological Validation ReviewPreliminary results of Hydrological validationHydrosphere State MissionHardwareInterface Control DocumentInformation and Communication TechnologyInstitute of Electrical and Electronics EngineersIntegrated Forecast SystemProgress reports in between meetingsInstitute of Meteorology and Water Management (of Poland)Institut für Photogrammetrie und FernerkundungIstituto di Scienze dell’Atmosfera e del Clima (of CNR)International Standards OrganizationInformation TechnologyIstanbul Technical UniversityJoint Polar System (MetOp + NOAA/NPOESS)Java 2 Enterprise EditionKestrel Interactive Development SystemThousand (Kilo) Lines Of CodeKick-Off MeetingLeaf Area IndexLocal Area NetworkLow Earth OrbitLightning Imaging Sensor (on TRMM)Lower Level SpecificationsLines Of CodeLow-Resolution Information TransmissionSolar Local Time (of a sun-synchronous satellite)Meteorological Archive and Retrieval System

H-SAFSystem Requirement DocumentDoc. No: SAF/HSAF/SRD/2.1Issue: Version 2.1Date: 20/06/2008Page: 15/102MetOp Meteorological Operational satelliteMETU Middle East Technical University (of Turkey)MHS Microwave Humidity Sounder (on NOAA N/N’ and MetOp)MIMR Multi-frequency Imaging Microwave RadiometerMIN Minutes of Meetings/ReviewsMODIS Moderate-resolution Imaging Spectro-radiometer (on EOS Terra and Aqua)MSG Meteosat Second GenerationMTBF Mean Time Between FailureMTG Meteosat Third GenerationMTTR Mean Time To RepairMVIRI Meteosat Visible Infra-Red Imager (on Meteosat 1 to 7)N/A Not AvailableN.A. Not ApplicableNASA National Aeronautics and Space AdministrationNATO North Atlantic Treaty OrganisationNDI Non-developmental ItemsNIMH National Institute for Meteorology and Hydrology (of Hungary)NMS National Meteorological ServiceNOAA National Oceanic and Atmospheric Organisation (intended as a satellite series)NPOESS National Polar-orbiting Operational Environmental Satellite SystemNPP NPOESS Preparatory ProgrammeNRT Near-Real TimeNWP Numerical Weather PredictionOAR Options Analysis for ReengineeringOFL Off-lineOM Offline Monitoring (referred to Offline Monitoring Subsystem items, e.g.: components)OMG Object Management GroupOO Object OrientedOP Proposal for H-SAF Operational phaseOPS Operational Product SegmentORB Object Request BrokerORR Operations Readiness ReviewOWL Web Ontology LanguagePAC Prototype Algorithm CodePALSAR Phased Array L-band Synthetic Aperture Radar (on ALOS)PAW Plant Available WaterPDR Preliminary Design ReviewPOP Precipitation Observation ProductionPP Project Plan

H-SAFSystem Requirement DocumentDoc. No: SAF/HSAF/SRD/2.1Issue: Version 2.1Date: 20/06/2008Page: 16/102PPR Products Prototyping ReportsPR Precipitation (referred to Precipitation Subsystem items, e.g.: products, components etc.)PRB Problem Review BoardQoS Quality of ServiceR&D Research and DevelopmentRCS Revision Control SystemREP ReportRMI Royal Meteorological Institute (of Belgium)RR Requirements ReviewRT Real TimeSAAM Simulation, Analysis and ModelingSAF Satellite Application FacilitySAG Science Advisory GroupSAOCOM Argentinean Satellite for Observation and CommunicationSAR Synthetic Aperture RadarSA/SD Structured Analysis / Structured DesignSCA Snow Covered AreaSCAT Scatterometer (on ERS-1 and 2)SCM Source Configuration ManagementSD Snow depthSDAS Surface Data Assimilation SystemSDD System Design DocumentSDP Software Development PlanSEI Software Engineering InstituteSEVIRI Spinning Enhanced Visible Infra-Red Imager (on MSG)SHW State Hydraulic Works of TurkeySHFWG SAF Hydrology Framework Working GroupSHMI Slovakian Hydrological and Meteorological InstituteSIRR System Integration Readiness ReviewSIVVP System Integration, Verification & Validation PlanSLAs Service-Level AgreementsSM Soil Moisture (referred to Soil Moisture Subsystem items, e.g.: products, components etc.)SMART Service Migration and Reuse TechniqueSMMR Scanning Multichannel Microwave Radiometer (on SeaSat and Nimbus VII)SMOS Soil Moisture and Ocean SalinitySN Snow Parameters (referred to Snow Parameters Subsystem products)SOA Service-Oriented ArchitectureSoS System of SystemsSP Snow Parameters (referred to Snow Parameters Subsystem items, e.g.: components)

H-SAFSystem Requirement DocumentDoc. No: SAF/HSAF/SRD/2.1Issue: Version 2.1Date: 20/06/2008Page: 17/102SQLSRSRDSSM/ISSMISSSVDSTRRSVALFSVERFSVRRSWSWESYKETBCTBDTCTKK/LSTTLETMITPTRTRMMTSMSTU WienUMU-MARFUMLURURDVIIRSVSWBSWMOWPWPDWSW3CXMIXMLStructured Query LanguageSystem RequirementSystem Requirements DocumentSpecial Sensor Microwave / Imager (on DMSP up to F-15)Special Sensor Microwave Imager/Sounder (on DMSP starting with F-16)System/Software Version DocumentSystem Test Results ReviewSystem Validation FileSystem Verification FileSystem Validation Results ReviewSoftwareSnow Water EquivalentFinnish Environment InstituteTo be confirmedTo be definedTest CaseHelsinki University of Technology / Laboratory of Space TechnologyTwo-line-element (telemetry data format)TRMM Microwave Imager (on TRMM)Test ProcedureTest ReportTropical Rainfall Measuring MissionTurkish State Meteorological ServiceTechnische Universität WienUser ManualUnified Meteorological Archive and Retrieval FacilityUnified Modelling LanguageUser RequirementUser Requirements DocumentVisible/Infrared Imager Radiometer Suite (on NPP and NPOESS)Visiting ScientistWork Breakdown StructureWorld Meteorological OrganizationWork PackageWork Package DescriptionWorkshopWorld Wide Web ConsortiumXML (eXtensible Markup Language ) Metadata InterchangeeXtensible Markup Language

H-SAFSystem Requirement DocumentDoc. No: SAF/HSAF/SRD/2.1Issue: Version 2.1Date: 20/06/2008Page: 18/102ZAMGZentral Anstalt für Meteorologie und Geodynamik1.4 References1.4.1 Applicable documents[AD 1] H-SAF Development Proposal - Issue 2.1, 15 May 2005[AD 2][AD 3][AD 4][AD 5][AD 6][AD 7][AD 8][AD 9][AD 10][AD 11][AD 12][AD 13][AD 14]H-SAF Project Plan (PP). Ref.: SAF/HSAF/PP/2.1H-SAF Configuration Management Plan (CMP). Ref.: SAF/HSAF/CMP/1.0H-SAF Users Requirement Document (URD). Ref.: SAF/HSAF/URD/2.1H-SAF SAF Preliminary Design Review Organization Note. Ref.:EUM/PPS/PRC/06/0125H-SAF System Requirements Document (SRD). Ref.: SAF/HSAF/SRD/2.0Algorithmic Software Development Guidelines Document (ASDGD). Ref.:SAF/HSAF/ASDGD/0.1System Integration, Verification & Validation Plan (SIVVP). Ref.: SAF/HSAF/SIVVP/1.0Guide to Software Configuration Management. Ref.: ESA PSS-05-09 Issue 1 Revision1SAF Software Development Guidelines. Ref.: SAF/NET/EUM/SW/GD/MTR/01H-SAF Algorithmic Software Development Guidelines Document (ASDGD) – internalissue – Ref.: SAF/HSAF/ASDGD/0.5Algorithms Theoretical Definition Document (ATDD) - Ref.: SAF/HSAF/ATDD/1.1H-SAF System Verification File (SVERF). Ref.: SAF/HSAF/SVERF/0.5H-SAF System/Software Version Document (SSVD). Ref.: SAF/HSAF/SSVD/0.51.4.2 Reference documents[RD 1][RD 2][RD 3][RD 4][RD 5][RD 6]EUM.TD.08 MSG - Image Data Dissemination ServiceEPS AMSU-A L1 Product Generation SpecificationEPS AMSU-A L1 Product Format SpecificationEPS MHS L1 Product Generation SpecificationEPS MHS L1 Product Format SpecificationMetOp-AVHRR documentation VCS Engineering website (http://rst.vcs.de/)[RD 7] NASA-MODIS documentation at NASA website(http://directreadout.gsfc.nasa.gov/index.cfm)[RD 8] Meteosat-SEVIRI documentation at EUMETSAT website(http://www.eumetsat.int/Home/Main/What_We_Do/Satellites/Meteosat_Second_Generation/index.html=en)

H-SAFSystem Requirement DocumentDoc. No: SAF/HSAF/SRD/2.1Issue: Version 2.1Date: 20/06/2008Page: 19/102[RD 9] EUMETSAT-EUMETCast documentation at EUMETSAT website(http://www.eumetsat.int/Home/Main/What_We_Do/EUMETCast/index.html=en)[RD 10][RD 11][RD 12][RD 13][RD 14][RD 15][RD 16][RD 17][RD 18][RD 19][RD 20][RD 21][RD 22][RD 23][RD 24]EPS NRT User Interface Specification. Ref.: EPS-ASPI-IR-0648National Oceanic and Atmospheric Administration (NOAA) Low-Rate InformationTransmission (LRIT) System. Ref.: http://noaasis.noaa.gov/LRIT/WMO–WWWDM specifications. Ref.: http://www.wmo.ch/web/www/WDM/wdm.htmlMARS – Meteorological Archive and Retrieval System, MARS User Guide (for DataRetrieval), Revision 11 – September 1995, Meteorological Bulletin B6.7/3, ECMWFReading, England. Ref.: http://www.wmo.ch/web/www/WDM/wdm.htmlMSG Level 1.5 Image Data Format Description. Ref.: ESA PSS-05-09 Issue 1 Revision1ECSS Standard on Space engineering. Verification. Ref.: ECSS-E-10-02AECSS Standard on Space engineering. Testing. Ref.: ECSS-E-10-03AECSS Standard on Space engineering. Software - Part 1: Principles and requirements.Ref.: ECSS-E-40 Part 1BECSS Standard on Space engineering. Software - Part 2: Document requirementsdefinitions (DRDs). Ref.: ECSS-E-40 Part 2BObject Management Group, Inc. (OMG), “Unified Modelling Language: Infrastructure”Version 2.0 – 05/072005Object Management Group, Inc. (OMG), “Unified Modelling Language: Superstructure”Version 2.0 – 05/072005Object Management Group, Inc. (OMG), “Unified Modelling Language: DiagramInterchange” Version 2.0 – 05/072005Object Management Group, Inc. (OMG), “Unified Modelling Language: BusinessModelling” Version 2.0 – 05/072005Brown, Alan W. & Wallnau, Kurt C. "Engineering of Component-Based Systems".Component-Based Software Engineering: Selected Papers from the SoftwareEngineering Institute. Los Alamitos, CA: IEEE Computer Society Press, 1996.Jim Rumbaugh, Ivar Jacobson, Grady Booch. “The Unified Modeling LanguageReference Manual (2nd edition)”2 General Description2.1 Purpose of the H-SAFThe main objectives of H-SAF are:a. to provide new satellite-derived products from existing and futuresatellites with sufficient time and space resolution to satisfy the needs of

H-SAFSystem Requirement DocumentDoc. No: SAF/HSAF/SRD/2.1Issue: Version 2.1Date: 20/06/2008Page: 20/102operational hydrology, by generating, centralizing, archiving anddisseminating the identified products:precipitation (liquid, solid, rate, accumulated);soil moisture (at large-scale, at local-scale, at surface, in the rootsregion);snow parameters (detection, cover, melting conditions, waterequivalent);b. to perform independent validation of the usefulness of the newproducts for fighting against floods, landslides, avalanches, and evaluatingwater resources; the activity includes:downscaling/upscaling modelling from observed/predicted fields tobasin level;fusion of satellite-derived measurements with data from radar andraingauge networks;assimilation of satellite-derived products in hydrological models;assessment of the impact of the new satellite-derived products onhydrological applications.2.2 Outlines of the H-SAF consortiumThe H-SAF participants and their roles are reported as follows (see also [AD 2]:No. Country Units in the Country Role in the Project01 AustriaZentralanstalt für Meteorologie undGeodynamikVienna University of Technology, Inst. ofPhotogram. & Remote SensingLeader for soil moisture02 BelgiumRoyal Meteorological Institute of Belgium Contributor for validation ofPR, SM and SP products andfor Hydro validation03 ECMWF04 FinlandEuropean Centre for Medium-rangeWeather ForecastsFinnish Meteorological Institute (FMI)Helsinki University of Technology,Laboratory of Space TechnologyFinnish Environment InstituteContributor for “core” soilmoistureLeader for snow parameters.Contributor for developmentand validation of SN productsand for Hydro validation

H-SAFSystem Requirement DocumentDoc. No: SAF/HSAF/SRD/2.1Issue: Version 2.1Date: 20/06/2008Page: 21/10205 France06 Germany07 Hungary08 Italy09 Poland10 Romania11 Slovakia12 TurkeyMétéo-FranceCNRS Centre d'Etudes Spatiales de laBIOsphereCNRS Centre d’études des Environnem.Terrestres et PlanétairesBundesanstalt für GewässerkundeHungarian Meteorological ServiceServizio Meteorologico dell’AeronauticaDipartimento Protezione Civile,Presidenza Consiglio MinistriCNR Istituto di Scienze dell’Atmosfera edel ClimaFerrara University, Department ofPhysicsInstitute of Meteorology and WaterManagementNational Institute for Meteorology andHydrologySlovakia Hydro-Meteorological InstituteTurkish State Meteorological ServiceMiddle East Technical University, CivilEngineering DepartmentIstanbul Technical University,Meteorological DepartmentContributor for developmentand validation of SM productsand for Hydro validationContributor for validation ofPR and SP products and forHydro validationContributor for validation ofPR productsHost + Leader for precipitationLeader for HydrologyContributor for development ofSP productsContributor for validation ofPR products and for HydrovalidationContributor for “core” snowparametersTable 1 Outlines of H-SAF Consortium2.3 Products / Deliveries of the H-SAFThe following table lists the targeted satellite-derived H-SAF products.

H-SAFSystem Requirement DocumentDoc. No: SAF/HSAF/SRD/2.1Issue: Version 2.1Date: 20/06/2008Page: 22/102The Table lists the satellites to be used pre-operationally and experimentally during theDevelopment Phase and those to be available during the Operational Phase (> 2010).Precipitation Anticipated product quality in the operational phase Satellites / Sensorsproducts Resolution Accuracy Cycle Delay Development OperationsPrecipitationrate (by MWonly) with flagfor phase10 km (MIS)15 km (additional GPMsatellites)10-20 % (> 10 mm/h)20-40 % (1-10 mm/h)40-80 % (< 1 mm/h)9 h (MISonly)3 h (fullGPM)20 minMeteosat(MVIRI, SEVIRI)+DMSP(SSM/I, SSMIS)Meteosat(SEVIRI)+NPPPrecipitationrate (by MW +IR) with flagfor phase10 kmRanging from that ofMW to one degradedby an extent15 min 10 min+NOAA + MetOp(AMSU-A,AMSU-B/MHS)+(ATMS)+NPOESS(CMIS, ATMS)EOS/Aqua+Cumulateprecipitation(by MW + IR)on 3, 6, 12, 24 h10 kmTentative:10 % over 24 h30 % over 3 h3 h 20 min(AMSR-E,AMSU-A, HSB)+TRMM(TMI, PR, LIS)Further satellitesof the GPM(all equipped atleast with a MWradiometer, onealso with radar)Soil moisture Anticipated product quality in the operational phase Satellites / Sensorsproducts Resolution Accuracy Cycle Delay Development OperationsSoil moisture inthe surfacelayerSoil moisture inthe roots region25 km (from ASCAT)50 km (from MIS)25 km (from ASCAT)50 km (from MIS)0.05 m 3 m -3 (dependingon vegetation)To be assessed(model-dependent).Tentative: 0.05 m 3 m -336 h (fromASCAT)9 h (fromMIS)36 h (fromASCAT)9 h (fromMIS)2 h2 hERS 1 / 2(AMI-SCAT)+MetOp(ASCAT)+EOS/Aqua(AMSR-E)MetOp(ASCAT)+NPOESS(MIS)Snow Anticipated product quality in the operational phase Satellites / Sensorsproducts Resolution Accuracy Cycle Delay Development Operations

H-SAFSystem Requirement DocumentDoc. No: SAF/HSAF/SRD/2.1Issue: Version 2.1Date: 20/06/2008Page: 23/102Snow detectionby opticalbands2 km95 % probability ofcorrect classification6 h(dependingon latitude)2 hNOAA(AVHRR)+MetOpEffective coverby optical andMW bands, withflag for wet/dry10 km (in MW)5 km (inVIS/SWIR/TIR)15 % (depending ontarget size andcomplexity)6 h(dependingon latitude)2 h(AVHRR, ASCAT)+Meteosat(SEVIRI)+EOS-Terra/AquaMetOp(AVHRR, ASCAT)+Meteosat(SEVIRI)(MODIS)++NPOESSDMSP(VIIRS, MIS)Snow WaterEquivalent byMW radiometer+ scatterometer10–25 km ~ 20 mm6 h(dependingon latitude)2h(SSM/I, SSMIS)+EOS-Aqua(AMSR-E)++MW radiometersof the GPMconstellationQuickSCAT(SeaWinds)Table 2 Satellite-derived H-SAF products and satellite data sourcesIn addition to satellite-derived products, H-SAF will make available forecast productsderived by a NWP limited-area model, so that end-users have available a back-up productat any time. The targeted forecast products are shown as follows (Table 3).Forecast products Resolution Accuracy (long term > 2010) Cycle DelayInstantaneousprecipitation rateat the groundAccumulatedprecipitationMid-project: 7 km,end-project: 2.5 km10-20 % (> 10 mm/h)20-40 % (1-10 mm/h)40-80 % (< 1 mm/h)10 % over 24 h, 30 % over 3 h.Mid-project: 3-6h,end-project: 1 hFixed timesof the dayTable 3 Backup products generated by a NWP modelThe Development Phase, in addition to including the activities for developing andgenerating new satellite-derived products, includes a Hydrology validation programme,performed by “Cluster-4”, lead by Poland; this aim shall be achieved through a complexset of activities and working programs, fully explained in details in the Project Plan [AD 2]

H-SAFSystem Requirement DocumentDoc. No: SAF/HSAF/SRD/2.1Issue: Version 2.1Date: 20/06/2008Page: 24/1022.4 System OverviewThe H-SAF architecture is based on:data production centres (in Italy, Austria + ECMWF, Finland + Turkey), that:1. acquire satellite data, mainly via direct reception (RT) or EUMETCast (NRT);2. generate the H-SAF products also with support of:local databasesother SAF’s productslocally available auxiliary/ancillary dataNWP model and climatology data.a structure for hydrological validation of all products and for generation of validationreports, physically distributed among seven countries and centrally managed andcoordinated by Poland as stated in [AD 2]existing dedicated communication networks (regional branches of the WMO GlobalTelecommunication System, dissemination system based on connection withEUMETSAT for re-distribution via EUMETCast) for immediate dissemination ofproducts versus operational end-users that are:o Meteorological services;o Hydrological services;o Civil Protection units.a structure, sited in Italy (CNMCA), for product centralization and archiving of allgenerated products and for their dissemination to scientific end-users based on a H-SAF archive connected to the EUMETSAT U-MARF via a U-MARF client.The UML Composite Structure Diagram of H-SAF system decomposition is here reported(Figure 1)

H -SAFSystem Requirement DocumentDoc. No: SAF/HSAF/SRD/2.1Issue: Version 2.1Date: 20/06/2008Page: 25/102id System Decomposition«system»HSAFWMO::GTS«subsystem»Hydro ValidationSCIENTIFIC USERS (R&D Institutes)request HSAF product via UMARFsystemEUMETSAT::EUMETCast«subsystem»Precipitation«subsystem»Snow Parameters«subsystem»Offline MonitoringUMARFclientEUMETSAT::UMARFData Source(from Data Sources)«subsystem»Soil MoistureRepresentativ e EndUser(from Representative End-Users)EUMETSAT::PPFFigure 1: H-SAF system decomposition

H -SAFSystem Requirement DocumentDoc. No: SAF/HSAF/SRD/2.1Issue: Version 2.1Date: 20/06/2008Page: 26/102In this architecture, as detailed in the System Design Document, five main subsystemshave been identified:1. Precipitation Subsystem: in charge of acquiring and pre-processing input data,generating Precipitation (Observation and Assimilation) products, performingquality control processes and activities and disseminating products to end users;2. Soil Moisture Subsystem, in charge of acquiring and pre-processing inputdata, generating Soil Moisture (Observation and Assimilation) products,performing quality control processes and activities and disseminating productsto end users;3. Snow Parameter Subsystem, in charge of acquiring and pre-processing inputdata, generating Snow Parameters (flat/forested, mountainous and merged)products, performing quality control activities and disseminating products to endusers;4. Hydro Validation Subsystem, in charge of providing independent assessmentof the usefulness of H-SAF products in operational hydrology and watermanagement, performing near-real-time acquisition of all products and carryingout hydrological validation activities using available tools and consolidatedmethods and models. It also provides valuable output for cal/val and validationreports used by production subsystems for possible products qualityimprovements;5. Offline Monitoring Subsystem, in charge of acquiring products and validationreports from the other subsystems, storing them in a central online/offlinearchive, disseminating the archived data in OFL to scientific users via U-MARFinterface and performing a monitoring on dissemination results.2.5 General ConstraintsThe availability of envisaged satellite data (current and planned) is a constraint both for thedevelopment and for the operational phase of H-SAF. For this reason it is relevant todepict some details about the situation at the time being (i.e. to be used pre-operationallyand experimentally in development phase). The following table summarises this situationand states, for each data sources, which of the specified access means is the oneconsiderd baseline:Data SourceInterface

H -SAFSystem Requirement DocumentDoc. No: SAF/HSAF/SRD/2.1Issue: Version 2.1Date: 20/06/2008Page: 27/102Data Source Description Baseline for operationsSEVIRI Meteosat 8LRITNRT via EUMETCastBackupBaselineAMSU-ANOAADirect read-outNRT via EUMETCastBaselineBackupAMSU-B NOAA 17SSM/I DMSP 15SSMIS DMSP 16Direct read-outNRT via EUMETCastNRT via EUMETCastFTP from UKMONRT via EUMETCastFTP from UKMOBaselineBackupBaseline if implementedCurrent baselineBaseline if implementedCurrent baselineMHSMetOpDirect read-outNRT via EUMETCastBaseline if implementedCurrent baselineAMSU-AMetOpDirect read-outNRT via EUMETCastBaseline if implementedCurrent baselineNWP ECMWF Dedicated linkSynopticObservationAuxiliary/AncillaryDataWMO-GOS(various)GTSOFLMHS NOAA 18MVIRI (2) Meteosat 7Direct read-outNRT via EUMETCastU-MARFBaselineBackupAMSR-E (forprecipitation)EOS-AquaFTPATMS (1) NPP NRT via EUMETCast If implementedLIS (1) TRMM FTP and other NASA

H -SAFSystem Requirement DocumentDoc. No: SAF/HSAF/SRD/2.1Issue: Version 2.1Date: 20/06/2008Page: 28/102Data SourceInterfaceData Source Description Baseline for operationsinterfacesPR (1)TMI (1)TRMMTRMMFTP and other NASAinterfacesFTP and other NASAinterfacesASCAT MetOp NRT via EUMETCast Backup (Level-1 data)AMI-SCAT (5) ERS 1/2 OFLASAR (6) Envisat OFLLevel-2processedMetOp/ ASCATEUMETSAT-PPF NRT via EUMETCastdata (7)AVHRRNOAADirect read-outNRT via EUMETCastBaselineBackupAVHRRMetOpDirect read-outNRT via EUMETCastBaseline if implementedCurrent baselineMODISEOS-AquaDirect read-outFTPBaseline if implementedCurrent baselineAMSR-E forsnowEOS-AquaDirect read-outFTPBaseline if implementedCurrent baselineMODISEOS-TerraDirect read-outFTPBaseline if implementedCurrent baselineNASADataArchivedNASAFTPNOAADataArchivedNOAAFTPECMWF ECMWF FTP

H -SAFSystem Requirement DocumentDoc. No: SAF/HSAF/SRD/2.1Issue: Version 2.1Date: 20/06/2008Page: 29/102Data SourceInterfaceData Source Description Baseline for operationsArchived DataTable 4 H-SAF External Interfaces for Data Acquisition(1)only used experimentally in the Development Phase(2) MVIRI only used for initial development (see ATDD v2 [AD 12] )(3) availability of instrument on NOAA-N’(19) is not certain (managed in Project Plan riskanalysis, see [AD 2])(4) availability of instrument is not certain (managed in Project Plan risk analysis, see [AD2])(5) only used initially for tuning algorithms and for early delivery of SM-ASS-1 product (see[AD 2])(6)only used for building the database supporting SM-OBS-2 products generation(7)Level-2 MetOp/ASCAT product corresponds to SM-OBS-1(8)shows problem with direct read-out(9)might not be actually used, at least until EOS-Aqua/AMSR-E is availableNote: Direct read-out data acquisition from NOAA-17, NOAA-18, MetOp and Meteosat-9shall be replaced in case of acquisition failure by NRT acquisition via EUMETCastAll these aspects are highly detailed in the risk analysis section of the Project Plan [AD 2];here, it is assumed that all data sources defined in the Detailed Proposal, in the UserRequirement Document and in the Project Plan will be available in the envisaged timing.Anyway, instruments-related requirements are here adequately flagged, and thisdocument will take into account of their evolution.3 Specific RequirementsIn this section the H-SAF System Requirements are presented, following someconventions described next.1 – Requirement CompositionEach requirement is composed of:Requirement Identifier: univocally identifies the requirement throughout the documentfollowing the naming convention described hereinafter.

H -SAFSystem Requirement DocumentDoc. No: SAF/HSAF/SRD/2.1Issue: Version 2.1Date: 20/06/2008Page: 30/102: optional, is a short requirement description.: optional, describes the peculiarity in compliance with the requirement.The following values are used in this document:o O: Optional: the requirement implementation is optional (desirablerequirement);o R: Instrument-related: the requirement is related to the availability of a specificinstrument which is not certain at the time being; this aspect is described in ProjectPlan risk analysis [AD 2].o When not appropriately filled, the related requirement is considered as mandatoryand not instrument-related.Subsystem identifier: identifies the H-SAF subsystem specifically related to therequirement; if missing, the requirement is mapped to the whole system.Verification Method: describes the method to be used for verifying the requirementcompliance. The following values can be used:o Analysis [A]o When verification is achieved by performing theoretical or empirical evaluation byaccepted techniques, the method shall be referred to as Analysiso Review of Design [R]o When verification is achieved by validation of records or by evidence of validateddesign documents or when approved design reports, technical descriptions,engineering drawings unambiguously show the requirement is met, the method shallbe referred as Review-of-designo Inspection [I]o When verification is achieved by visual determination of physical characteristics(such as construction features, hardware conformance to document drawing orworkmanship requirements) the method shall be referred to as Inspection.o Demonstration [D]o This verification method may be used when actual conduct can verify achievementof requirements such as service and access, transportability, human engineeringfeatures and qualitative features. A requirement which is of an operational orfunctional nature and is not quantified by a specific measurable parameter may beverified by demonstration.o Test [T]o When requirements have to be verified by measuring product performance andfunction under various simulated environments, the method shall be referred to asTest; these measurements may require the use of special equipment,instrumentation and simulation techniques; the analysis of data derived from Testshall be considered an integral part of the test. When relevant, Test also givesevidence of qualitative operational performance and requirements. Theperformance, as proved, shall be observed and recorded.Requirement Description: full description of the requirement.: optional, applicable document the requirement derives from.

H -SAFSystem Requirement DocumentDoc. No: SAF/HSAF/SRD/2.1Issue: Version 2.1Date: 20/06/2008Page: 31/102: optional field which intends to provide additional information, justification, orexplanation of the requirement. Comment is for information only and is not considered part ofthe requirement.2- Requirement IdentifierThe requirement identifier has been coded in this document as follows:where:SR-NNNNN-XXX-YYYSRSystem RequirementNNNNN Progressive number, unique for each requirement.XXXYYYOne of the following requirement classes:FUNPEROPEINTDESQUAFunctionalPerformanceOperationalInterfaceDesignQualityRAM Reliability, Availability, MaintenancePORRESTVAPortabilityResourcesTest, Verification and AcceptanceDOC DocumentationSAFSECSafetySecurityOne of the following functional areasGENACQPPRPRGVPRREPARCDISGeneralData acquisitionPre-processingProduct generationHydroValidation ProcessingReportingArchivingDistribution/DisseminationVMQ Validation, Monitoring and Quality ControlIn order to improve the document readability, the requirements have been groupedtogether following a two levels decomposition structure:

H -SAFSystem Requirement DocumentDoc. No: SAF/HSAF/SRD/2.1Issue: Version 2.1Date: 20/06/2008Page: 32/102First level: by requirement classSecond level: by functional area.Note: the second decomposition level can be missing when not applicable or when alimited number of requirements are present within the class.3.1 Functional requirementsFor a better comprehension of the below list and in particular of the Table 6, a clarificationhas to be made here about the main difference between auxiliary data and data souces:auxilary data are intended to be used as a support data during the product processing inorder to improve quality/accuracy; data sources, instead, are intended as the input dataflows which act as the fundamental starting point in production processes.3.1.1 General RequirementsSR-00010-FUN-GEN Level Component PR, SM, SPDescriptionCommentProducts shall be automatically generated by operational chainsVerification TSR-00020-FUN-GEN Level Component PR, SM, SPDescriptionCommentThe geographical region of product appliance shall be Europe (includingTurkey) and North AfricaVerification TSR-00021-FUN-GEN Level Component HVDescriptionCommentThe geographical region of hydrovalidation appliance shall be Europe(including Turkey) and North AfricaVerification TSR-00030-FUN-GEN Level Component ALL

H -SAFSystem Requirement DocumentDoc. No: SAF/HSAF/SRD/2.1Issue: Version 2.1Date: 20/06/2008Page: 33/102DescriptionCommentThe system shall be able to identify classes of error conditions within theones listed in Table 5Verification TClassINFODescription of the notification messageNon-threatening information to the user.E.g.: a simple splash screen to notify an alertWARNINGERRORALARMCONFIRMATIONPotential dangerous operation in advance.E.g.: "Warning: this operation will erase your data."Critical situation.E.g.: "There is not enough memory to install theapplication."Notification about something in progress or to bedoneE.g.: "Staff meeting in five minutes."Non-threatening information to the user.E.g.: "The file has been saved."Table 5 Classes of messagesSR-00040-FUN-GEN Level Component ALLDescriptionCommentError codes shall be identified by a unique identifier codeVerification TSR-00050-FUN-GEN Level Component ALLDescriptionCommentThe system shall handle system warnings or alarms messages on thebasis of error classesVerification TSR-00060-FUN-GEN Level Component ALL

H -SAFSystem Requirement DocumentDoc. No: SAF/HSAF/SRD/2.1Issue: Version 2.1Date: 20/06/2008Page: 34/102DescriptionCommentUTC time reference shall be used throughout all manual activities andautomatic processesVerification ISR-00070-FUN-GEN Level Component PR, SM, SPDescriptionCommentSystem shall be able to receive data listed in Table 6 via the interfacesthere specified.Verification IDataData SourceSourceInterface DescriptionSEVIRI Meteosat 8AMSU-A NOAA 17AMSU-A NOAA 18AMSU-B NOAA 17SSM/I DMSP 15SSMIS DMSP 16Direct read-out (only for 9)NRT via EUMETCastDirect read-outNRT via EUMETCastDirect read-outNRT via EUMETCastDirect read-outNRT via EUMETCastNRT via EUMETCastFTP from UKMONRT via EUMETCastFTP from UKMOMHS (4)AMSU-A (4)MetOpMetOpDirect read-outNRT via EUMETCastDirect read-outNRT via EUMETCastNWP UKMO FTP

H -SAFSystem Requirement DocumentDoc. No: SAF/HSAF/SRD/2.1Issue: Version 2.1Date: 20/06/2008Page: 35/102DataData SourceSourceInterface DescriptionSynoptic / Observation WMO-GTS RTAuxiliary/Ancillary Data (various) OFLMHS (3) NOAA 18MVIRI (2) Meteosat 7Direct read-outNRT via EUMETCastDirect read-outNRT via EUMETCastAMSR-E (1) EOS-Aqua FTPATMS (1)Gras (1)NPPMetOp(1)(1)LIS (1) TRMM FTP and other NASA interfacesPR (1) TRMM FTP and other NASA interfacesTMI (1) TRMM FTP and other NASA interfacesASCAT MetOp Direct read-outAMI-SCAT (5) ERS 1/2 OFLASAR (6) Envisat OFLLevel-1 and 2processed MetOp/ EUMETSAT-PPF NRT via EUMETCastASCAT data (7)Synoptic / Observation WMO-GTS RTAuxiliary Data (various) OFLAVHRRAVHRRModisNOAAMetOpEOS-AquaDirect read-outNRT via EUMETCastDirect read-outNRT via EUMETCastDirect read-outFTP

H -SAFSystem Requirement DocumentDoc. No: SAF/HSAF/SRD/2.1Issue: Version 2.1Date: 20/06/2008Page: 36/102DataData SourceSourceInterface DescriptionAMSR-E (8) EOS-Aqua FTPModisEOS-TerraDirect read-outFTPSEVIRI Meteosat NRT via EUMETCastSSM/I (9) DMSP FTPSSMIS (9) DMSP FTPSynoptic / ObservationDataWMO-GTSRTNASA Archived Data NASA FTPNOAA Archived Data NOAA FTPECMWF Archived Data ECMWF FTPTable 6 H-SAF Data sources(1)only used experimentally in the Development Phase(2) MVIRI only used for initial development (see ATDD v2 part1 [AD 18])(3) availability of instrument on NOAA-N’(19) is not certain (managed in Project Plan riskanalysis, see [AD 2] )(4) availability of instrument is not certain (managed in Project Plan risk analysis, see [AD2])(5) only used initially for tuning algorithms and for early delivery of SM-ASS-1 product (see[AD 2])(6)only used for building the database supporting SM-OBS-2 products generation(7)Level-2 MetOp/ASCAT product corresponds to SM-OBS-1(8)shows problem with direct read-out(9)might not be actually used, at least until EOS-Aqua/AMSR-E is availableNote: Direct read-out data acquisition from NOAA-17, NOAA-18, MetOp and Meteosat-9shall be replaced in case of acquisition failure by NRT acquisition via EUMETCast

H -SAFSystem Requirement DocumentDoc. No: SAF/HSAF/SRD/2.1Issue: Version 2.1Date: 20/06/2008Page: 37/1023.1.2 Data Acquisition RequirementsSR-10010-FUN-ACQ Level O Component ALLDescriptionCommentData input listed in Table 6 should be archived locally (either physically orvirtually) and made accessible to the H-SAF central archiveIt should be made in order to enablereconstruction of time series, or recalibrationand/or re-processing byadvanced algorithms. Re-processingactivity shall be carried out upondecision by Project Team and SteeringGroupVerification TSR-10020-FUN-ACQ Level Component ALLDescriptionCommentInput filters shall reject automatically erroneous dataAs a matter of principle, whereaspossible data correction and/or warningis preferred to automatical rejection.Rejection is achieved only when data isunambiguously recognized as erroneousdata type by the involved algorithmfacilityVerification TSR-10030-FUN-ACQ Level O Component ALLDescriptionCommentArchival of satellite data should allow identification of information listed inTable 7Verification TSatellite data informationSatellite identifierSatellite coordinatesSatellite time information

H -SAFSystem Requirement DocumentDoc. No: SAF/HSAF/SRD/2.1Issue: Version 2.1Date: 20/06/2008Page: 38/102Satellite data informationChannel availabilitySensor IdentifierData versionTable 7 Information related to satellite dataSR-10090-FUN-ACQ Level Component ALLDescriptionCommentSource of auxiliary data shall be identifiedVerification TSR-10100-FUN-ACQ Level Component ALLDescriptionCommentTime information of time-related auxiliary data shall be identifiedVerification TSR-10110-FUN-ACQ Level Component ALLDescriptionCommentFailure in acquiring mandatory data shall not cause abnormal interruptionof operational chain of product generationVerification TSR-10120-FUN-ACQ Level Component ALLDescriptionCommentFailure in acquiring mandatory data shall cause an error rising andloggingVerification TSR-10130-FUN-ACQ Level Component PR, SM, SPDescriptionCommentSystem shall be able to acquire synoptic observation data through WMO-GTSVerification T

H -SAFSystem Requirement DocumentDoc. No: SAF/HSAF/SRD/2.1Issue: Version 2.1Date: 20/06/2008Page: 39/1023.1.2.1 Precipitation subsystemSR-12010-FUN-ACQ Level Component PRDescriptionCommentSystem shall acquire AMSU-A data from NOAA-17 through direct-readoutinterfaceVerification TSR-12011-FUN-ACQ Level Component PRDescriptionCommentSystem shall acquire AMSU-A data from NOAA-17 through NRT interfacevia EUMETCastVerification TSR-12020-FUN-ACQ Level Component PRDescriptionCommentSystem shall acquire AMSU-B data from NOAA-17 through direct-readoutinterfaceVerification TSR-12021-FUN-ACQ Level Component PRDescriptionCommentSystem shall acquire AMSU-B data from NOAA-17 through NRT interfacevia EUMETCastVerification TSR-12030-FUN-ACQ Level Component PRDescriptionCommentSystem shall acquire AMSU-A data from NOAA-18 through direct-readoutinterfaceVerification TSR-12031-FUN-ACQ Level Component PRDescriptionSystem shall acquire AMSU-A data from NOAA-18 through NRT interfacevia EUMETCast

H -SAFSystem Requirement DocumentDoc. No: SAF/HSAF/SRD/2.1Issue: Version 2.1Date: 20/06/2008Page: 40/102CommentVerification TSR-12040-FUN-ACQ Level Component PRDescriptionCommentSystem shall acquire MHS data from NOAA-18 through direct-read-outinterfaceVerification TSR-12041-FUN-ACQ Level Component PRDescriptionCommentSystem shall acquire MHS data from NOAA-18 through NRT interface viaEUMETCastVerification TSR-12050-FUN-ACQ Level R Component PRDescriptionSystem shall acquire AMSU-A data from NOAA-N’(19) through directread-outinterfaceComment instrument related requirement:availability of instrument is not certain(managed in Project Plan risk analysis[AD 2])Verification TSR-12051-FUN-ACQ Level R Component PRDescriptionSystem shall acquire AMSU-A data from NOAA-N’(19) through NRTinterface via EUMETCastComment instrument related requirement:availability of instrument is not certain(managed in Project Plan risk analysis[AD 2])Verification TSR-12060-FUN-ACQ Level R Component PR

H -SAFSystem Requirement DocumentDoc. No: SAF/HSAF/SRD/2.1Issue: Version 2.1Date: 20/06/2008Page: 41/102DescriptionSystem shall acquire MHS data from NOAA-N’(19) through direct-readoutinterfaceComment Instrument related requirement:availability of instrument is not certain(managed in Project Plan risk analysis[AD 2])Verification TSR-12061-FUN-ACQ Level R Component PRDescriptionSystem shall acquire MHS data from NOAA-N’(19) through NRT interfacevia EUMETCastComment instrument related requirement:availability of instrument is not certain(managed in Project Plan risk analysis[AD 2])Verification TSR-12070-FUN-ACQ Level R Component PRDescriptionSystem shall acquire AMSU-A data from MetOp through direct-read-outinterfaceComment instrument related requirement:availability of instrument is not certain(managed in Project Plan risk analysis[AD 2])Verification TSR-12071-FUN-ACQ Level R Component PRDescriptionSystem shall acquire AMSU-A data from MetOp through NRT interfacevia EUMETCastComment instrument related requirement:availability of instrument is not certain(managed in Project Plan risk analysis[AD 2])Verification TSR-12080-FUN-ACQ Level R Component PR

H -SAFSystem Requirement DocumentDoc. No: SAF/HSAF/SRD/2.1Issue: Version 2.1Date: 20/06/2008Page: 42/102DescriptionSystem shall acquire MHS data from MetOp through direct-read-outinterfaceComment instrument related requirement:availability of instrument is not certain(managed in Project Plan risk analysis[AD 2])Verification TSR-12081-FUN-ACQ Level R Component PRDescriptionSystem shall acquire MHS data from MetOp through NRT interface viaEUMETCastComment instrument related requirement:availability of instrument is not certain(managed in Project Plan risk analysis[AD 2])Verification TSR-12100-FUN-ACQ Level Component PRDescriptionCommentSystem shall acquire SEVIRI data from Meteosat8 through NRT interfacevia EUMETCastVerification TSR-12110-FUN-ACQ Level Component PRDescriptionCommentSystem shall acquire SEVIRI data from Meteosat 9 through direct-readoutinterfaceVerification TSR-12111-FUN-ACQ Level Component PRDescriptionCommentSystem shall acquire SEVIRI data from Meteosat 9 through NRT interfacevia EUMETCastVerification T

H -SAFSystem Requirement DocumentDoc. No: SAF/HSAF/SRD/2.1Issue: Version 2.1Date: 20/06/2008Page: 43/102SR-12120-FUN-ACQ Level Component PRDescriptionCommentSystem shall acquire SSM/I data from DMSP-15 through NRT interfaceactually, for most of the HSAFDevelopment Phase these data shall beacquired from FTP from UKMOVerification TSR-12130-FUN-ACQ Level Component PRDescriptionCommentSystem shall acquire SSMIS data from DMSP-16 through NRT interfaceactually, for most of the HSAFDevelopment Phase these data shall beacquired from FTP from UKMOVerification TSR-12140-FUN-ACQ Level Component PRDescriptionCommentSystem shall acquire SSMIS data from DMSP-17 through NRT interfaceactually, for most of the HSAFDevelopment Phase these data shall beacquired through FTP from UKMOVerification TSR-12150-FUN-ACQ Level ComponentDescriptionCommentSystem shall acquire SSMIS data from DMSP-18 through NRT interfaceactually, for most of the HSAFDevelopment Phase these data shall beacquired from FTP from UKMOVerification TSR-12160-FUN-ACQ Level Component PRDescriptionCommentSystem shall acquire SSMIS data from DMSP-19 through NRT interfaceactually, for most of the HSAFDevelopment Phase these data shall beacquired from FTP from UKMOVerification TSR-12220-FUN-ACQ Level Component PR

H -SAFSystem Requirement DocumentDoc. No: SAF/HSAF/SRD/2.1Issue: Version 2.1Date: 20/06/2008Page: 44/102DescriptionCommentDirect acquisition of NOAA-17, NOAA-18, MetOp, Meteosat-9 data shallbe replaced in case of acquisition failure by NRT acquisition viaEUMETCastVerification TSR-12240-FUN-ACQ Level O Component PRDescriptionSystem should be able to acquire lightning data as auxiliary data inprecipitation chainComment data is needed for quality control Verification TSR-12250-FUN-ACQ Level O Component PRDescriptionSystem should be able to acquire VIS/IR/MW image data as auxiliary datain precipitation chainComment data is needed for quality control Verification TSR-12260-FUN-ACQ Level O Component PRDescriptionSystem should be able to acquire meteorological analysis data asauxiliary data in precipitation chainComment data is needed for quality control Verification TSR-12270-FUN-ACQ Level O Component PRDescriptionSystem should be able to acquire data from raingauge networks asauxiliary data in precipitation chainComment data is needed for quality control Verification TSR-12280-FUN-ACQ Level O Component PRDescriptionSystem should be able to acquire rain data images as auxiliary data inprecipitation chainComment data is needed for quality control Verification T

H -SAFSystem Requirement DocumentDoc. No: SAF/HSAF/SRD/2.1Issue: Version 2.1Date: 20/06/2008Page: 45/102SR-12300-FUN-ACQ Level Component PRDescriptionCommentSystem shall be able to acquire boundary conditions data from ECMWFVerification T3.1.2.2 Soil moisture subsystemSR-11010-FUN-ACQ Level Component SMDescriptionCommentSystem shall be able to acquire through NRT interface via EUMETCastthe level II processed MetOp ASCAT data at 25 km resolution (SM-OBS-1) and level I one, generated by EUMETSAT-PPFLevel I ASCAT product shall be used forproducing the SM-OBS-1 backupproduct. Moreover ERS-1&2 AMI-SCATarchived data (only in absence ofASCAT data and for testing the surfacesoil moisture products generation chain)from TU-Wien H-SAF componentVerification TSR-11030-FUN-ACQ Level Component SMDescriptionCommentSystem shall be able to access European Parameter database, dataabout land cover, operational snow cover maps, freeze/thaw cycles, waterbodies, and topography as auxiliary datadata is needed for the disaggregation ofthe surface soil moisture productVerification TSR-11040-FUN-ACQ Level Component SMDescriptionCommentSystem shall be able to access modelled root zone soil moisture (firstguess) coming from IFS as auxiliary datadata is needed for the assimilation ofsatellite-derived product in hydrologicalmodelVerification T

H -SAFSystem Requirement DocumentDoc. No: SAF/HSAF/SRD/2.1Issue: Version 2.1Date: 20/06/2008Page: 46/1023.1.2.3 Snow Parameters subsystemSR-13010-FUN-ACQ Level Component SPDescriptionCommentsystem shall be able to acquire data from EOS-aqua and terra data fromMODIS through direct-read-out interfaceVerification TSR-13015-FUN-ACQ Level Component SPDescriptionCommentsystem shall be able to acquire data from EOS-aqua and terra data fromMODIS through FTP interfaceVerification TSR-13020-FUN-ACQ Level Component SPDescriptionCommentsystem shall be able to acquire AVHRR data from NOAA through directread-outinterfaceVerification TSR-13030-FUN-ACQ Level Component SPDescriptionCommentSystem shall acquire AMSR-E data from EOS-Aqua through FTPinterfaceat the time being there is a problem withdirect read-outVerification TSR-13040-FUN-ACQ Level Component SPDescriptionCommentSystem shall acquire SSM/I data from DMSP through FTP from UKMOmight not be actually used, at least untilEOS-Aqua/AMSR-E is availableVerification TSR-13050-FUN-ACQ Level Component SP

H -SAFSystem Requirement DocumentDoc. No: SAF/HSAF/SRD/2.1Issue: Version 2.1Date: 20/06/2008Page: 47/102DescriptionCommentSystem shall acquire SSMIS data from DMSP through FTP from UKMOmight not be actually used, at least untilEOS-Aqua/AMSR-E is availableVerification TSR-13060-FUN-ACQ Level Component SPDescriptionCommentSystem shall access to synoptic/observation data in RT through WMO-GTSVerification TSR-13070-FUN-ACQ Level Component SPDescriptionCommentSystem shall be able to access, through FTP, NOAA and NASA archiveddataVerification DSR-13080-FUN-ACQ Level O Component SPDescriptionCommentSystem should be able to access, through FTP, ECMWF archived dataVerification DSR-13090-FUN-ACQ Level Component SPDescriptionCommentsystem shall be able to acquire AVHRR data from MetOp through directread-outinterfaceVerification TSR-13100-FUN-ACQ Level Component SPDescriptionCommentsystem shall be able to acquire AVHRR data from NOAA through NRTinterface via EUMETCastVerification T

H -SAFSystem Requirement DocumentDoc. No: SAF/HSAF/SRD/2.1Issue: Version 2.1Date: 20/06/2008Page: 48/1023.1.2.4 Hydro Validation subsystemSR-14010-FUN-ACQ Level Component HVDescriptionCommentHydrological validation subsystem shall acquire H-SAF products as aninput data for hydrological modelsVerification TSR-14020-FUN-ACQ Level Component HVDescriptionCommentHydrological validation subsystem shall be able to acquire H-SAFproducts through FTP interface via InternetVerification TSR-14030-FUN-ACQ Level Component HVDescriptionCommentHydrological validation subsystem shall be able to acquire H-SAFproducts in NRT through EUMETCastVerification TSR-14040-FUN-ACQ Level R Component HVDescriptionCommentHydrological validation subsystem shall be able to acquire H-SAFproducts in RT through WMO GTSVerification T3.1.3 Pre-Processing RequirementsSR-20010-FUN-PPR Level Component ALLDescriptionCommentSatellite data pre-processing and local archiving shall not be affected by afailure in reception of data from channels not listed in Table 6Verification T

H -SAFSystem Requirement DocumentDoc. No: SAF/HSAF/SRD/2.1Issue: Version 2.1Date: 20/06/2008Page: 49/102SR-20020-FUN-PPR Level Component PR, SM, SPDescriptionCommentSatellite raw data from sources described in Table 6 shall be prepared(pre-processed) as structured data files suitable for processingVerification T3.1.4 Product Generation RequirementsSR-30010-FUN-PRG Level Component PR, SM, SPDescriptionCommentProducts generated within a subsystem shall be archived locally and thensent to the central archiveVerification TSR-30020-FUN-PRG Level Component PR, SM, SPDescriptionCommentProducts shall be submitted to automatic quality controlVerification TSR-30030-FUN-PRG Level Component PR, SM, SPDescriptionCommentQuality flags shall be associated to productsVerification TSR-30040-FUN-PRG Level Component PR, SM, SPDescriptionGeneration chains shall be able to receive Hydrovalidation reports fromcentral archiveComment central archive is part of OfflineMonitoring subsystemVerification T

H -SAFSystem Requirement DocumentDoc. No: SAF/HSAF/SRD/2.1Issue: Version 2.1Date: 20/06/2008Page: 50/1023.1.4.1 Precipitation subsystemSR-32010-FUN-PRG Level Component PRDescriptionCommentThe system shall produce the “Precipitation rate at ground by MW conicalscanners (with indication of phase)” product (PR-OBS-1)Verification TSR-32011-FUN-PRG Level Component PRDescriptionCommentThe system shall produce the “Precipitation rate at ground by MW crosstrackscanners (with indication of phase)” product (PR-OBS-2)Verification TSR-32020-FUN-PRG Level Component PRDescriptionCommentResolution of PR-OBS-1 product shall be 10 km (with MIS) or 15 km(with additional GPM)Verification TSR-32021-FUN-PRG Level Component PRDescriptionCommentResolution of PR-OBS-2 product shall be 10 km (with MIS) or 15 km (withother GPM)Verification TSR-32030-FUN-PRG Level Component PRDescriptionCommentAccuracy of PR-OBS-1 product shall be 10-20% (for a rate > 10 mm/h),20-40% (for a rate from 1 to 10 mm/h), 40-80% (for a rate < 1 mm/h)Verification TSR-32031-FUN-PRG Level Component PRDescriptionAccuracy of PR-OBS-2 product shall be 10-20% (for a rate > 10 mm/h),20-40% (for a rate from 1 to 10 mm/h), 40-80% (for a rate < 1 mm/h)

H -SAFSystem Requirement DocumentDoc. No: SAF/HSAF/SRD/2.1Issue: Version 2.1Date: 20/06/2008Page: 51/102CommentVerification TSR-32040-FUN-PRG Level Component PRDescriptionCommentFrequency of PR-OBS-1 product shall be 9 h (with MIS) or 3 h (with fullGPM)Verification TSR-32041-FUN-PRG Level Component PRDescriptionCommentFrequency of PR-OBS-2 product shall be 9 h (with CMIS) or 3 h (with fullGPM)Verification TSR-32060-FUN-PRG Level Component PRDescriptionCommentThe system shall produce the “Precipitation rate at ground by GEO/IRsupported by LEO/MW” product (PR-OBS-3)Verification TSR-32061-FUN-PRG Level Component PRDescriptionCommentThe system shall produce the “Precipitation rate at ground by LEO/MWsupported by GEO/IR (with flag for phase)” product (PR-OBS-4)Verification TSR-32062-FUN-PRG Level Component PRDescriptionCommentThe system shall produce the “Accumulated precipitation at ground byMW+IR and MW only” product (PR-OBS-5)Verification TSR-32063-FUN-PRG Level Component PR

H -SAFSystem Requirement DocumentDoc. No: SAF/HSAF/SRD/2.1Issue: Version 2.1Date: 20/06/2008Page: 52/102DescriptionCommentThe system shall produce the “Instantaneous and accumulatedprecipitation at the ground computed by a NWP model” product (PR-ASS-1)Verification TSR-32070-FUN-PRG Level O Component PRDescriptionCommentSystem should allow clouds classifications, by mean of SAFNWC/MSGsoftware packageVerification ISR-32080-FUN-PRG Level O Component PRDescriptionCommentSystem should provide spatial/time derivative informations on IR and WVcell pixels, by means of NEFODINA software packageVerification ISR-32090-FUN-PRG Level O Component PRDescriptionCommentSystem should provide space/time continuised field by assimilatingoriginal precipitation data in LAMI NWP modelVerification ISR-32230-FUN-PRG Level Component PRDescriptionCommentA database of regular observation of 1-hour cumulated precipitationparameter shall be locally set upVerification ISR-32240-FUN-PRG Level Component PRDescriptionCommentSystem shall be able to access to datasets for calibration and validationVerification I

H -SAFSystem Requirement DocumentDoc. No: SAF/HSAF/SRD/2.1Issue: Version 2.1Date: 20/06/2008Page: 53/1023.1.4.2 Soil Moisture subsystemSR-31010-FUN-PRG Level Component SMDescriptionCommentThe system shall produce the “Global surface soil moisture by radarscatterometer” product (SM-OBS-1)Verification TSR-31020-FUN-PRG Level Component SMDescriptionCommentResolution of SM-OBS-1 product shall be 25 km (from ASCAT) or 50 km(from MIS)Verification TSR-31030-FUN-PRG Level Component SMDescription Accuracy of SM-OBS-1 product shall be 0.05 m 3 m -3CommentVerification TSR-31040-FUN-PRG Level Component SMDescriptionCommentFrequency of SM-OBS-1 product shall be 36 h (from ASCAT) or 9 h (fromMIS)Verification TSR-31060-FUN-PRG Level Component SMDescriptionComment“Regional surface soil moisture by radar scatterometer” product (SM-OBS-2) shall be derived from SM-OBS-1 one, re-sampling it at 1 kmintervalsVerification TSR-31061-FUN-PRG Level Component SMDescriptionSM-OBS-2 product shall be corrected in topography and projected touser-defined coordinate systems

H -SAFSystem Requirement DocumentDoc. No: SAF/HSAF/SRD/2.1Issue: Version 2.1Date: 20/06/2008Page: 54/102CommentVerification TSR-31070-FUN-PRG Level Component SMDescriptionCommentThe system shall produce the “Volumetric soil moisture (roots region) byscatterometer assimilation in NWP model” product (SM-ASS-1)Verification TSR-31080-FUN-PRG Level Component SMDescriptionCommentResolution of SM-ASS-1 product shall be 25 km (from ASCAT) and 50 km(from MIS)Verification TSR-31090-FUN-PRG Level O Component SMDescription Accuracy of SM-ASS-1 product should be 0.05 m 3 m -3Comment it is an attempt only (model dependent) Verification TSR-31100-FUN-PRG Level Component SMDescriptionCommentFrequency of SM-ASS-1 product shall be 36 h (from ASCAT) and 9h(from MIS)Verification TSR-31150-FUN-PRG Level Component SMDescriptionCommentSoil moisture operational chain shall be triggered by the reception oflevel-II processed ASCAT data filesVerification TSR-31270-FUN-PRG Level Component SM

H -SAFSystem Requirement DocumentDoc. No: SAF/HSAF/SRD/2.1Issue: Version 2.1Date: 20/06/2008Page: 55/102DescriptionCommentA reference database for cal/val, which shall archive elements describedin Table 8, shall be set upVerification DElement for SM consistency controlIn-situ data (e.g. Global Soil Moisture Data Bank, time domain reflectometry)Related space-based soil moisture missions (e.g. SMOS)Global water datasets (e.g. Global Lakes and Wetlands Database GLWD)Global snow datasets (e.g. Daily Northern Hemi-sphere Snow and Ice Analysisfrom United States National Snow and Ice Data Center NSIDC, Snow mapsbeing produced by H-SAF consortium)Global topography datasets (e.g. United States Geological Survey GlobalTopographic Data GTOPO30)Global freeze/thaw datasets (e.g. NCEP/NCAR Global Tropospheric Analyses,ECMWF’s 40-year Re-Analysis ERA-40)Table 8 Elements for soil moisture consistency control3.1.4.3 Snow Parameter subsystemSR-33040-FUN-PRG Level Component SPDescriptionCommentThe system shall produce at FMI the “snow detection (snow mask) byVIS/IR radiometry” (SN-OBS-1a) observation product in flat/forested areaVerification TSR-33050-FUN-PRG Level Component SPDescriptionCommentThe system shall produce at FMI the “snow status (dry/wet) by MWradiometry” (SN-OBS-2) observation product in flat/forested areaVerification TSR-33051-FUN-PRG Level Component SP

H -SAFSystem Requirement DocumentDoc. No: SAF/HSAF/SRD/2.1Issue: Version 2.1Date: 20/06/2008Page: 56/102DescriptionCommentProduct SN-OBS-2 shall provide a flag reporting snow status parameter(dry/wet)This product shall not be merged with ananalogous product on mountainousareas, as instead foreseen for the otherthree flat/forested productsVerification TSR-33060-FUN-PRG Level Component SPDescriptionCommentThe system shall produce at FMI the “effective snow cover by VIS/IRradiometry” (SN-OBS-3a) observation product in flat/forested areaVerification TSR-33065-FUN-PRG Level Component SPDescriptionCommentThe system shall produce at FMI the “snow water equivalent by MWradiometry” (SN-OBS-4a) observation product in flat/forested areaVerification TSR-33070-FUN-PRG Level Component SPDescriptionCommentResolution of SN-OBS-1a product shall be 2 kmVerification TSR-33080-FUN-PRG Level Component SPDescriptionCommentResolution of SN-OBS-2 product shall be 10 kmVerification TSR-33090-FUN-PRG Level Component SPDescriptionCommentResolution of SN-OBS-3a product shall be 5 KmVerification T

H -SAFSystem Requirement DocumentDoc. No: SAF/HSAF/SRD/2.1Issue: Version 2.1Date: 20/06/2008Page: 57/102SR-33100-FUN-PRG Level Component SPDescriptionCommentResolution of SN-OBS-4a product shall be 10 kmVerification TSR-33110-FUN-PRG Level Component SPDescriptionCommentAccuracy of SN-OBS-1a product shall be 95 % probability of correctclassificationVerification TSR-33120-FUN-PRG Level Component SPDescriptionCommentAccuracy of SN-OBS-2 product shall be 15 % (depending on basin sizeand complexity)Verification TSR-33125-FUN-PRG Level Component SPDescriptionCommentAccuracy of SN-OBS-3a product shall be 15 % (depending on basin sizeand complexity)Verification TSR-33130-FUN-PRG Level Component SPDescriptionCommentAccuracy of SN-OBS-4a product shall be about 20 mmVerification TSR-33140-FUN-PRG Level Component SPDescriptionCommentFrequency SN-OBS-1a product shall be 6 h (depending on latitude)Verification TSR-33150-FUN-PRG Level Component SP

H -SAFSystem Requirement DocumentDoc. No: SAF/HSAF/SRD/2.1Issue: Version 2.1Date: 20/06/2008Page: 58/102DescriptionCommentFrequency of SN-OBS-2 product shall be 6 h (depending on latitude)Verification TSR-33160-FUN-PRG Level Component SPDescriptionCommentFrequency SN-OBS-3a product shall be 6 h (depending on latitude)Verification TSR-33170-FUN-PRG Level Component SPDescriptionCommentFrequency SN-OBS-4a product shall be 6 h (depending on latitude)Verification TSR-33200-FUN-PRG Level Component SPDescriptionCommentThe system shall produce at TSMS the “snow detection (snow mask) byVIS/IR radiometry” (SN-OBS-1b) observation product in mountainousareaVerification TSR-33210-FUN-PRG Level Component SPDescriptionCommentThe system shall produce at TSMS the “effective snow cover by VIS/IRradiometry” (SN-OBS-3b) observation product in mountainous areaVerification TSR-33220-FUN-PRG Level Component SPDescriptionCommentThe system shall produce at TSMS the “snow water equivalent by MWradiometry” (SN-OBS-4b) observation product in mountainous areaVerification TSR-33230-FUN-PRG Level Component SP

H -SAFSystem Requirement DocumentDoc. No: SAF/HSAF/SRD/2.1Issue: Version 2.1Date: 20/06/2008Page: 59/102DescriptionCommentResolution of SN-OBS-1b product shall be 2 kmVerification TSR-33240-FUN-PRG Level Component SPDescriptionCommentResolution of SN-OBS-3b product shall be 5 kmVerification TSR-33250-FUN-PRG Level Component SPDescriptionCommentResolution of SN-OBS-4b product shall be 10 kmVerification TSR-33260-FUN-PRG Level Component SPDescriptionCommentAccuracy of SN-OBS-1b product shall be 95 % probability of correctclassificationVerification TSR-33270-FUN-PRG Level Component SPDescriptionCommentAccuracy of SN-OBS-3b product shall be 15 % (depending on basin sizeand complexity)Verification TSR-33280-FUN-PRG Level Component SPDescriptionCommentAccuracy of SN-OBS-4b product shall be about 20 mmVerification TSR-33290-FUN-PRG Level Component SPDescriptionCommentFrequency SN-OBS-1b product shall be 6 h (depending on latitude)Verification T

H -SAFSystem Requirement DocumentDoc. No: SAF/HSAF/SRD/2.1Issue: Version 2.1Date: 20/06/2008Page: 60/102SR-33300-FUN-PRG Level Component SPDescriptionCommentFrequency SN-OBS-3b product shall be 6 h (depending on latitude)Verification TSR-33310-FUN-PRG Level Component SPDescriptionCommentFrequency SN-OBS-4b product shall be 6 h (depending on latitude)Verification TSR-33320-FUN-PRG Level Component SPDescriptionCommentThe system shall merge at FMI SN-OBS-1a and SN-OBS-1b observationproducts generating SN-OBS-1 combined productVerification TSR-33330-FUN-PRG Level Component SPDescriptionCommentThe system shall merge at FMI SN-OBS-3a and SN-OBS-3b observationproducts generating SN-OBS-3 combined productVerification TSR-33340-FUN-PRG Level Component SPDescriptionCommentThe system shall merge at FMI SN-OBS-4a and SN-OBS-4b observationproducts generating SN-OBS-4 combined productVerification T3.1.5 Hydrovalidation Processing RequirementsSR-34010-FUN-VPR Level Component HV

H -SAFSystem Requirement DocumentDoc. No: SAF/HSAF/SRD/2.1Issue: Version 2.1Date: 20/06/2008Page: 61/102DescriptionHydro validation subsystem shall be able to process H-SAF products inthe formats listed in Table 9Comment JPEG or similar used for a quick look Verification TProduct format for HV processingGRIB ver. 1BUFR ver. 3HDF-5ASCIIJPEG or similarTable 9 Formats for Hydrovalidation processingSR-34020-FUN-VPR Level Component HVDescriptionCommentHydro validation process in development phase shall be performed dailyat fixed time of the day, except for SN-OBS-4 that shall be performed onthe orbital basisVerification TSR-34030-FUN-VPR Level Component HVDescriptionCommentHydro validation process in operational phase shall be performedaccording to timing listed in Table 10Verification TProductTimingPR-OBS-1 and PR-OBS-2,PR-OBS-3, PR-OBS-4 and PR-ASS-1On the orbital basis / near-real-timeHourlyPR-OBS-5 At standard synoptic time (every 3hours)SN-OBS-1a, SN-OBS-1b, SN-OBS-1, On the orbital basis

H -SAFSystem Requirement DocumentDoc. No: SAF/HSAF/SRD/2.1Issue: Version 2.1Date: 20/06/2008Page: 62/102ProductSN-OBS-2, SN-OBS-3a, SN-OBS-3b,SN-OBS-3, SN-OBS-4a, SN-OBS-4b,SN-OBS-4, SM-OBS-1, SM-OBS-2 andSM-ASS-1TimingTable 10 Timings for Hydrovalidation processingSR-34040-FUN-VPR Level Component HVDescriptionCommentHydro validation process shall be able to use digital terrain models, landcover maps, river network data as ancillary dataVerification TSR-34050-FUN-VPR Level Component HVDescriptionCommentHydro validation subsystem shall achieve preprocessing of input data inorder to fit input variables to model resolutionVerification TSR-34060-FUN-VPR Level Component HVDescriptionCommentHydrological models shall be able to process input parameters withspatial and temporal resolution as presented in Table 11Verification TParameterPrecipitationRequired spatial resolutionRegular grid 50, 100, 500 m: 1, 7, 8km, HRU, subcatchmentRequired temporalresolution10 min, 15 min, 1h, 3h, 6h,dailySnowfall Regular grid 1 km, 8 km, HRU 6 h – dailyAir temperature8 km, 25 km, point, HRU10 min, 15 min, 1h, 2h,dailySoil moisture point, catchment daily

H -SAFSystem Requirement DocumentDoc. No: SAF/HSAF/SRD/2.1Issue: Version 2.1Date: 20/06/2008Page: 63/102Snow coveredareaFrom 50 meter to the full catchmentareadailySolar radiation 8 km, 50 km, point 15 min,1h, 6h, dailySnow waterequivalentFrom 50 meter to the full catchmentareadailyLong waveradiation8 km 1hSun duration 50 km 6hLand use,vegetation type30m, 250 m, 1km 10 days, seasonWind speed 7 km, 8 km, 25 km 10 min, 1h, 2hHumidity 8 km, 50 km, point 1h, 2h, 6 hTable 11 Input data and parameters used by selected operational hydrological models3.1.6 Hydrovalidation Reporting RequirementsSR-34110-FUN-REP Level Component HVDescriptionCommentHydrological Validation shall provide structured results to be retro-fitted tothe product generation chains.Verification ISR-34120-FUN-REP Level Component HVDescriptionCommentHydrological Validation subsystem shall be able to generate reports in anautomatic way.Verification ISR-34130-FUN-REP Level Component HVDescriptionCommentHydrological Validation reports shall include at least payload informationlisted in Table 12Verification I

H -SAFSystem Requirement DocumentDoc. No: SAF/HSAF/SRD/2.1Issue: Version 2.1Date: 20/06/2008Page: 64/102Payload information for HV reportsinformation on what was the objective of the impact study (e.g., floodforecasting);main basin characteristics (size, hydrological regime, …);description of the meteorological event;assessment of the benefit of satellite versus no-satellitejudgement whether the result was occasional or structural;advice on how the results could have been better.Table 12 Payload information for Hydrovalidation reportsSR-34140-FUN-REP Level Component HVDescriptionCommentHydrological Validation reports shall include at least header informationlisted in Table 13Verification IHeader information for HV reportsDate/period/location (catchment name)Hydrological event occurred: type of floods (flash, snowmelt, ice-jam), drought,low/high discharge events.Reason for the studies: discrepancies between operationally used hydrologicalmodel results and the real situation; possibility of replacement of non-functionalparts of standard measurement network by satellite products.Satellite products used for impact study.Hydrological model used for the impact studyTable 13 Header information for Hydrovalidation reportsSR-34150-FUN-REP Level Component HVDescriptionReports produced by Hydrological Validation subsystem shall be archived

H -SAFSystem Requirement DocumentDoc. No: SAF/HSAF/SRD/2.1Issue: Version 2.1Date: 20/06/2008Page: 65/102CommentVerification ISR-34160-FUN-REP Level Component HVDescriptionCommentArchive of Hydrological Validation reports shall be accessible throughstandard FTP and HTTP browsersVerification ISR-34170-FUN-REP Level Component HVDescriptionCommentHydrological Validation reports shall be automatically distributed to theproduct generation chainsVerification ISR-34180-FUN-REP Level Component HVDescriptionCommentHydrological Validation reports shall be generated in the formats listed inTable 14Verification IOutput data format for HV reportsMicrosoft Word documents (.doc)Microsoft Excel documents (.xls)Portable Document Format (.pdf)Table 14 Output data formats for Hydrovalidation reports3.1.7 Archival RequirementsSR-44010-FUN-ARC Level Component OMDescriptionCommentCentral archival shall be guaranteed in an online/offline archiveVerification I

H -SAFSystem Requirement DocumentDoc. No: SAF/HSAF/SRD/2.1Issue: Version 2.1Date: 20/06/2008Page: 66/102SR-44020-FUN-ARC Level Component OMDescriptionCommentArchive shall maintain logging of archival-relevant dataVerification DSR-44021-FUN-ARC Level Component OMDescriptionCommentDuration of archival-relevant data logging shall be not less than onemonthVerification TSR-44030-FUN-ARC Level Component OMDescriptionCommentH-SAF central archive shall be set upVerification ISR-44040-FUN-ARC Level Component OMDescriptionCommentH-SAF central archive shall ingest all products outputs from SnowParameter chain, Precipitation chain and Soil Moisture chainVerification TSR-44041-FUN-ARC Level Component OMDescriptionCommentHydro Validation reports shall be collected in H-SAF central archiveVerification TSR-44050-FUN-ARC Level Component OMDescriptionCommentPerformance reports of online-offline dissemination to users shall becollected in H-SAF central archiveVerification T

H -SAFSystem Requirement DocumentDoc. No: SAF/HSAF/SRD/2.1Issue: Version 2.1Date: 20/06/2008Page: 67/102SR-44060-FUN-ARC Level Component OMDescriptionCommentAnalysis of reports from the addressed users shall be performed, toassess compliance with system performance requirements such astimeliness and reliabilityVerification TSR-44070-FUN-ARC Level Component OMDescriptionCommentContent of performance report regarding time of reception, format check,message soundness shall be automatically detectedVerification TSR-44080-FUN-ARC Level Component OMDescriptionCommentData transfer from online to offline archive shall be automatedVerification TSR-44090-FUN-ARC Level Component OMDescriptionCommentSystem shall be able to restore offline data to online archiveVerification T3.1.8 Dissemination RequirementsSR-54010-FUN-DIS Level Component OMDescriptionCommentSystem shall be able to receive orders from users through UMARFVerification TSR-54020-FUN-DIS Level Component OMDescriptionSystem shall be able to process orders from users by disseminatingproducts through UMARF

H -SAFSystem Requirement DocumentDoc. No: SAF/HSAF/SRD/2.1Issue: Version 2.1Date: 20/06/2008Page: 68/102CommentVerification TSR-54030-FUN-DIS Level Component OMDescriptionCommentSystem shall provide a catalogue to UMARFVerification TSR-54040-FUN-DIS Level Component OMDescriptionCommentValidation of orders received through UMARF shall be performedVerification TSR-54050-FUN-DIS Level Component OMDescriptionCommentOrders acceptance/rejection shall be notified to UMARFVerification TSR-54060-FUN-DIS Level Component OMDescriptionCommentUpdated information about orders progress status shall be guaranteed toUMARFVerification TSR-54070-FUN-DIS Level Component PR,SM,SPDescriptionCommentSystem shall disseminate products to meteorological services throughWMO-GTSVerification TSR-54080-FUN-DIS Level Component PR, SM, SPDescriptionCommentGTS disseminated products shall respond to WMO standard encodingVerification D

H -SAFSystem Requirement DocumentDoc. No: SAF/HSAF/SRD/2.1Issue: Version 2.1Date: 20/06/2008Page: 69/102SR-54091-FUN-DIS Level Component PR, SM, SP, OMDescriptionProducts shall be disseminated to Hydro Validation Subsystem usingformats listed in Table 15Comment JPEG or similar used for a quick look Verification TProducts file formatGRIB ver. 1BUFR ver. 3HDF-5ASCIIJPEG or similarTable 15 Formats for data dissemination to Hydro Validation SubsystemSR-54120-FUN-DIS Level Component OMDescriptionCommentSystem shall archive records of disseminated productsVerification TSR-54130-FUN-DIS Level Component OMDescriptionCommentConnection to U-MARF shall be established via a client installed locallyVerification ISR-54150-FUN-DIS Level Component PR, SM, SP, OMDescriptionCommentCommunication links via EUMETCast shall guarantee dissemination timecompatible with time limits as addressed in Table 16Timeliness for dissemination to NRTusers is defined as acquisition time +generation time + dissemination timeVerification T

H -SAFSystem Requirement DocumentDoc. No: SAF/HSAF/SRD/2.1Issue: Version 2.1Date: 20/06/2008Page: 70/102SR-54160-FUN-DIS Level Component OMDescriptionCommentSystem shall disseminate products to operational users other thanmeteorological services through EUMETCastVerification TSR-54170-FUN-DIS Level Component PR, SM, SPDescriptionCommentH-SAF products shall be disseminated to H-SAF central archive in realtimeVerification TSR-54180-FUN-DIS Level Component OMDescriptionCommentHydro Validation Reports shall be retro-fitted from the central archive tothe generation chainsVerification T3.2 Reliability, Availability and Maintenance RequirementsSR-70010-RAM-GEN Level O Component ALLDescriptionCommentSoftware should be under configuration control, following what is definedin Configuration Management PlanVerification DSR-70020-RAM-GEN Level Component ALLDescriptionCommentLogging messages shall permit identification of the event-related itemsVerification DSR-70030-RAM-GEN Level Component ALL

H -SAFSystem Requirement DocumentDoc. No: SAF/HSAF/SRD/2.1Issue: Version 2.1Date: 20/06/2008Page: 71/102DescriptionCommentFreely available or cots software packages shall be used only with writtensupport guarantee by the developer during the whole programme lifetimeVerification ISR-70040-RAM-GEN Level O Component ALLDescriptionCommentFreely available or cots software packages should be encapsulated in amodular access interfaceVerification DSR-70050-RAM-GEN Level Component ALLDescription Systems availability shall be of 99%CommentVerification TSR-70060-RAM-GEN Level O Component ALLDescriptionCommentSystem failure should be fail-silentVerification TSR-70070-RAM-GEN Level Component ALLDescriptionCommentSystem functions shall be available 24 hours a day 7 days a weekVerification T3.3 Operational RequirementsSR-80010-OPE-GEN Level Component ALLDescriptionCommentBackup of operational software configuration items shall be performed,with regular frequency, following indications reported in the ConfigurationManagement PlanVerification D

H -SAFSystem Requirement DocumentDoc. No: SAF/HSAF/SRD/2.1Issue: Version 2.1Date: 20/06/2008Page: 72/102SR-80020-OPE-GEN Level O Component ALLDescriptionCommentSystem should need human specific operations only in offline operations(such as backing-up operations or offline archiving), system configuration,and mainteinanceVerification DSR-80040-OPE-GEN Level Component ALLDescriptionCommentHuman-Machine-Interface shall provide user authentication functionsVerification TSR-80050-OPE-GEN Level ComponentDescriptionCommentThe system shall be able to manage missing real time production(because of missed acquisitions, corrupted input data, unavailability of theonline products generation facilities and/or of the dissemination means)using a specific recovery planA recovery plan should be foreseen onlyfor the reconstructing time series. If therecovery is impossible or not sufficientlycost effective (the Project Team todecide) the gap shall be accepted as itisVerification R3.4 Performance RequirementsSR-91000-PER-GEN Level O Component ALLDescriptionCommentDuring operational phase 95% of products reported in Table 2 withenvisaged quality level, should be guaranteed in case of availability ofrelated input dataVerification T

H -SAFSystem Requirement DocumentDoc. No: SAF/HSAF/SRD/2.1Issue: Version 2.1Date: 20/06/2008Page: 73/102SR-91020-FUN-PRG Level Component ALLDescriptionCommentProduct processing shall be completed (from the end of reception) inaccordance to production timeliness described in Table 16Timeliness for dissemination to NRTusers is defined as acquisition time +generation time + dissemination timeVerification TSubsystem Product Product description TimelimessPR-OBS-1Precipitation rate at ground byMW conical scanners (withindication of phase)Demonstrational status, First release:within 90 min from the end ofacquisitionOperational status. Final release: within15 min from the end of reception ifwithin the acquisition range of Rome;otherwise 90 minPR-OBS-2Precipitation rate at ground byMW cross-track scanners (withindication of phase)15 min from the end of reception ifwithin the acquisition range of Rome;otherwise 30 minPrecipitationPR-OBS-3Precipitation rate at ground byGEO/IR supported by LEO/MWWithin 5 min from the end of (real time)acquisitionPR-OBS-4Precipitation rate at ground byLEO/MW supported by GEO/IR(with flag for phase)20 min after acquisition of a new MWimage (5 min after availability of newMW retrievals requiring 15 miinprocess)PR-OBS-5Accumulated precipitation atground by MW+IR and MW onlyAt fixed times of the day, within 15 minafter synoptic hours (00, 03, 06, 09, 12,15, 18 and 21 UTC)PR-ASS-1Instantaneous and accumulatedprecipitation at the groundcomputed by a NWP modelAt fixed times of the day, 4 h afternominal time of analysis (00, 06, 12, 18and, in Operational status and finalrelease, 03, 09, 15, 21 UTC)SoilMoistureSM-OBS-1Global surface soil moisture byradar scatterometer130 min (potentially 30 min using theEARS service)

H -SAFSystem Requirement DocumentDoc. No: SAF/HSAF/SRD/2.1Issue: Version 2.1Date: 20/06/2008Page: 74/102SM-OBS-2Regional surface soil moisture byradar scatterometer135 min (potentially 35 min using theEARS service)SM-ASS-1Volumetric soil moisture (rootsregion) by scatterometerassimilation in NWP model36 h (due to the need to assimilate dataobserved in the 6-30 hours precedingstart of the operational run)SN-OBS-1Snow detection (snow mask) byVIS/IR radiometryFixed time of the day, product updatedto account for data available until 1 hbefore deliverySnowParametersSN-OBS-2SN-OBS-3Snow status (dry/wet) by MWradiometryEffective snow cover by VIS/IRradiometryFixed time of the day, product updatedto account for data available until 1 hbefore deliveryFixed time of the day, product updatedto account for data available until 1 hbefore deliverySN-OBS-4Snow water equivalent by MWradiometryFixed time of the day, product updatedto account for data available until 1 hbefore deliveryTable 16 Time limits in products generation/dissemination3.5 Portability RequirementsH-SAF does not fit compulsory portability requirements, for the reason that (as stated evenat proposal stage) each of the production centres will use as far as possible its ownSW/HW environment.Anyway, the compliance with standards acts as a desirable requirement in order toaccomplish to both credibility and updating capabilities; standard criteria shall be issued byengineering task (see Project Plan [AD 2]), to be applied, when the case, to all participantsin charge of products generation.SR-92010-POR-GEN Level O Component ALLDescriptionSystem software should be platform independent (by using open standardenvironment and/or tools)

H -SAFSystem Requirement DocumentDoc. No: SAF/HSAF/SRD/2.1Issue: Version 2.1Date: 20/06/2008Page: 75/102CommentCompliance with standards act as adesired requirement in order toaccomplish to both credibility andupdating capabilities; standard criteriashall be issued by engineering task, tobe applied when the case to allparticipants in charge of productsgeneration.Verification DSR-92020-POR-GEN Level O Component ALLDescriptionCommentSoftware should run in unix compliant environmentCompliance with standards act as adesired requirement in order toaccomplish to both credibility andupdating capabilities; standard criteriashall be issued by engineering task, tobe applied when the case to allparticipants in charge of productsgeneration.Verification ISR-92030-POR-GEN Level O Component ALLDescriptionCommentSoftware of product generation chains should be written in programminglanguages such those described in Table 17Compliance with standards act as adesired requirement in order toaccomplish to both credibility andupdating capabilities; standard criteriashall be issued by engineering task, tobe applied when the case to allparticipants in charge of productsgenerationVerification I

H -SAFSystem Requirement DocumentDoc. No: SAF/HSAF/SRD/2.1Issue: Version 2.1Date: 20/06/2008Page: 76/102SW LanguageISO/IEC 9899 CISO/IEC 14882 C++Fortran 90/95Bourne/Korn/C-shell scriptsISO/IEC std script languages (PERL, PYTHON; PHP)IDL / PV-WAVEjavaTable 17 Software coding languagesSR-92040-POR-GEN Level O Component ALLDescriptionCommentLanguage coding of Table 17 should respect latest ECSS guidelines [RD15], [RD 16], [RD 17], [RD 18]Compliance with standards act as adesired requirement in order toaccomplish to both credibility andupdating capabilities; standard criteriashall be issued by engineering task, tobe applied when the case to allparticipants in charge of productsgenerationVerification R3.6 Resources RequirementsSR-93010-RES-GEN Level Component ALLDescriptionCommentOnline disc capacity shall be sufficient to maintain the sum of input,intermediate and output data at least for 7 operational daysVerification TSR-93050-RES-GEN Level Component ALL

H -SAFSystem Requirement DocumentDoc. No: SAF/HSAF/SRD/2.1Issue: Version 2.1Date: 20/06/2008Page: 77/102DescriptionCommentSystem’s hardware resources of physical memory shall be sufficient tohandle data processingVerification TSR-93060-RES-GEN Level Component ALLDescriptionCommentNetwork communication bandwidth shall guarantee data transfer withoutimpact on production time limits described in Table 16Verification TSR-93070-RES-GEN Level Component OMDescriptionCommentA H-SAF web site shall be set up and maintainedThe web site shall provide generalpublic information on H-SAFVerification TSR-93080-RES-GEN Level Component OMDescriptionCommentA H-SAF help desk shall be set up and mantainedVerification T3.7 Safety RequirementsSR-94010-SAF-GEN Level Component ALLDescriptionCommentSituations which could bring the system to a degraded operational modeshall cause a system warning messageVerification TSR-94020-SAF-GEN Level Component ALLDescriptionSituations which should require an operator action shall cause a systemalarm

H -SAFSystem Requirement DocumentDoc. No: SAF/HSAF/SRD/2.1Issue: Version 2.1Date: 20/06/2008Page: 78/102CommentVerification TSR-94030-SAF-GEN Level Component ALLDescriptionCommentError occurring during application execution shall not lead to uncontrolledapplication abort/terminationVerification TSR-94040-SAF-GEN Level Component ALLDescriptionCommentEvery software item shall return its termination statusVerification T3.8 Security RequirementsSR-95010-SEC-GEN Level Component ALLDescriptionCommentSoftware design shall prevent accidental data modificationsVerification RSR-95020-SEC-GEN Level Component ALLDescriptionCommentSoftware design shall prevent unauthorized data modificationsVerification RSR-95030-SEC-GEN Level Component ALLDescriptionCommentSoftware design shall prevent propagation of software damagesVerification R

H -SAFSystem Requirement DocumentDoc. No: SAF/HSAF/SRD/2.1Issue: Version 2.1Date: 20/06/2008Page: 79/1023.9 Documentation RequirementsSR-96010-DOC-GEN Level Component ALLDescriptionCommentDocumentation shall be available for each configuration itemVerification I4 TBDs/TBCs listNo TBD/TBC items are pending.5 Requirements traceability5.1 System Requirements traceability to H-SAF SubsystemsThe following table summarises the mapping of the requirements to H-SAF subsystemsSubsystemAll H-SAF SubsystemsSystem Requirement IdentifierSR-00030-FUN-GENSR-00040-FUN-GENSR-00050-FUN-GENSR-00060-FUN-GENSR-10010-FUN-ACQSR-10020-FUN-ACQSR-10030-FUN-ACQSR-10090-FUN-ACQSR-10100-FUN-ACQSR-10110-FUN-ACQSR-10120-FUN-ACQSR-20010-FUN-PPRSR-70010-RAM-GENSR-70020-RAM-GENSR-70030-RAM-GENSR-70040-RAM-GENSR-70050-RAM-GENSR-70060-RAM-GEN

H -SAFSystem Requirement DocumentDoc. No: SAF/HSAF/SRD/2.1Issue: Version 2.1Date: 20/06/2008Page: 80/102SubsystemPrecipitation SubsystemSystem Requirement IdentifierSR-70070-OPE-GENSR-80010-OPE-GENSR-80020-OPE-GENSR-80040-OPE-GENSR-80050-OPE-GENSR-91000-PER-GENSR-91020-PER-GENSR-92010-POR-GENSR-92020-POR-GENSR-92030-POR-GENSR-92040-POR-GENSR-93010-RES-GENSR-93050-RES-GENSR-93060-RES-GENSR-94010-SAF-GENSR-94020-SAF-GENSR-94030-SAF-GENSR-94040-SAF-GENSR-95010-SEC-GENSR-95020-SEC-GENSR-95030-SEC-GENSR-96010-DOC-GENSR-00010-FUN-GENSR-00020-FUN-GENSR-00070-FUN-GENSR-10130-FUN-ACQSR-12010-FUN-ACQSR-12011-FUN-ACQSR-12020-FUN-ACQSR-12021-FUN-ACQSR-12030-FUN-ACQSR-12031-FUN-ACQSR-12040-FUN-ACQSR-12041-FUN-ACQSR-12050-FUN-ACQSR-12051-FUN-ACQ

H -SAFSystem Requirement DocumentDoc. No: SAF/HSAF/SRD/2.1Issue: Version 2.1Date: 20/06/2008Page: 81/102SubsystemSystem Requirement IdentifierSR-12060-FUN-ACQSR-12061-FUN-ACQSR-12070-FUN-ACQSR-12071-FUN-ACQSR-12080-FUN-ACQSR-12081-FUN-ACQSR-12100-FUN-ACQSR-12110-FUN-ACQSR-12111-FUN-ACQSR-12120-FUN-ACQSR-12130-FUN-ACQSR-12140-FUN-ACQSR-12150-FUN-ACQSR-12160-FUN-ACQSR-12220-FUN-ACQSR-12240-FUN-ACQSR-12250-FUN-ACQSR-12260-FUN-ACQSR-12270-FUN-ACQSR-12280-FUN-ACQSR-12300-FUN-ACQSR-20020-FUN-PPRSR-30010-FUN-PRGSR-30020-FUN-PRGSR-30030-FUN-PRGSR-30040-FUN-PRGSR-32010-FUN-PRGSR-32020-FUN-PRGSR-32030-FUN-PRGSR-32040-FUN-PRGSR-32011-FUN-PRGSR-32021-FUN-PRGSR-32031-FUN-PRGSR-32041-FUN-PRGSR-32060-FUN-PRG

H -SAFSystem Requirement DocumentDoc. No: SAF/HSAF/SRD/2.1Issue: Version 2.1Date: 20/06/2008Page: 82/102SubsystemSoil Moisture subsystemSystem Requirement IdentifierSR-32061-FUN-PRGSR-32062-FUN-PRGSR-32063-FUN-PRGSR-32070-FUN-PRGSR-32080-FUN-PRGSR-32090-FUN-PRGSR-32230-FUN-PRGSR-32240-FUN-PRGSR-54070-FUN-DISSR-54080-FUN-DISSR-54091-FUN-DISSR-54150-FUN-DISSR-54170-FUN-DISSR-00010-FUN-GENSR-00020-FUN-GENSR-00070-FUN-GENSR-10130-FUN-ACQSR-11010-FUN-ACQSR-11030-FUN-ACQSR-11040-FUN-ACQSR-20020-FUN-PPRSR-30010-FUN-PRGSR-30020-FUN-PRGSR-30030-FUN-PRGSR-30040-FUN-PRGSR-31010-FUN-PRGSR-31020-FUN-PRGSR-31030-FUN-PRGSR-31040-FUN-PRGSR-31060-FUN-PRGSR-31061-FUN-PRGSR-31070-FUN-PRGSR-31080-FUN-PRGSR-31090-FUN-PRGSR-31100-FUN-PRGSR-31150-FUN-PRG

H -SAFSystem Requirement DocumentDoc. No: SAF/HSAF/SRD/2.1Issue: Version 2.1Date: 20/06/2008Page: 83/102SubsystemSnow Parameter subsystemSystem Requirement IdentifierSR-31270-FUN-PRGSR-54070-FUN-DISSR-54080-FUN-DISSR-54091-FUN-DISSR-54150-FUN-DISSR-54170-FUN-DISSR-00010-FUN-GENSR-00020-FUN-GENSR-00070-FUN-GENSR-10130-FUN-ACQSR-13010-FUN-ACQSR-13015-FUN-ACQSR-13020-FUN-ACQSR-13025-FUN-ACQSR-13030-FUN-ACQSR-13040-FUN-ACQSR-13050-FUN-ACQSR-13060-FUN-ACQSR-13070-FUN-ACQSR-13080-FUN-ACQSR-13090-FUN-ACQSR-13100-FUN-ACQSR-20020-FUN-PPRSR-30010-FUN-PRGSR-30020-FUN-PRGSR-30030-FUN-PRGSR-30040-FUN-PRGSR-33040-FUN-PRGSR-33050-FUN-PRGSR-33051-FUN-PRGSR-33060-FUN-PRGSR-33065-FUN-PRGSR-33070-FUN-PRGSR-33080-FUN-PRGSR-33090-FUN-PRGSR-33100-FUN-PRG

H -SAFSystem Requirement DocumentDoc. No: SAF/HSAF/SRD/2.1Issue: Version 2.1Date: 20/06/2008Page: 84/102SubsystemHydro Validation subsystemSystem Requirement IdentifierSR-33110-FUN-PRGSR-33120-FUN-PRGSR-33125-FUN-PRGSR-33130-FUN-PRGSR-33140-FUN-PRGSR-33150-FUN-PRGSR-33160-FUN-PRGSR-33170-FUN-PRGSR-33200-FUN-PRGSR-33210-FUN-PRGSR-33220-FUN-PRGSR-33230-FUN-PRGSR-33240-FUN-PRGSR-33250-FUN-PRGSR-33260-FUN-PRGSR-33270-FUN-PRGSR-33280-FUN-PRGSR-33290-FUN-PRGSR-33300-FUN-PRGSR-33310-FUN-PRGSR-33330-FUN-PRGSR-33340-FUN-PRGSR-33320-FUN-PRGSR-54070-FUN-DISSR-54080-FUN-DISSR-54091-FUN-DISSR-54150-FUN-DISSR-54170-FUN-DISSR-00021-FUN-GENSR-14010-FUN-ACQSR-14020-FUN-ACQSR-14030-FUN-ACQSR-14040-FUN-ACQSR-34010-FUN-VPRSR-34020-FUN-VPRSR-34030-FUN-VPR

H -SAFSystem Requirement DocumentDoc. No: SAF/HSAF/SRD/2.1Issue: Version 2.1Date: 20/06/2008Page: 85/102SubsystemSystem Requirement IdentifierSR-34040-FUN-VPRSR-34050-FUN-VPRSR-34060-FUN-VPRSR-34110-FUN-REPSR-34120-FUN-REPSR-34130-FUN-REPSR-34140-FUN-REPSR-34150-FUN-REPSR-34160-FUN-REPSR-34170-FUN-REPSR-34180-FUN-REPOffline Monitoring Subsystem SR-44010-FUN-ARCSR-44020-FUN-ARCSR-44021-FUN-ARCSR-44030-FUN-ARCSR-44040-FUN-ARCSR-44041-FUN-ARCSR-44050-FUN-ARCSR-44060-FUN-ARCSR-44070-FUN-ARCSR-44080-FUN-ARCSR-44090-FUN-ARCSR-54010-FUN-DISSR-54020-FUN-DISSR-54030-FUN-DISSR-54040-FUN-DISSR-54050-FUN-DISSR-54060-FUN-DISSR-54091-FUN-DISSR-54120-FUN-DISSR-54130-FUN-DISSR-54150-FUN-DISSR-54160-FUN-DISSR-52180-FUN-DISTable 18 System Requirements traceability vs H-SAF subsystems

H -SAFSystem Requirement DocumentDoc. No: SAF/HSAF/SRD/2.1Issue: Version 2.1Date: 20/06/2008Page: 86/1025.2 System Requirements traceability to User RequirementsThis paragraph shows System Requirements traceability versus User Requirements,through a proper table. It is assumed that not all of the user requirements have beencarried forward to system requirements, for reasons explained contextually in [AD 4].A summary of these reasons is here reported:UR-GE-08 to UR-GE-12: programmatic requirements not giving rise to systemrequirements;UR-PR-13 to UR-PR-15, UR-SM-09 to UR-SM-11, UR-SN-07 and UR-SN-12:processing activities not giving rise to system requirements;UR-ET-01 to UR-ET-03: education & training activities not giving rise to systemrequirements;UR-RD-01 to UR-RD-03: scientific activities not giving rise to system requirements;UR-HY-01 to UR-HY-15: experimental activities not giving rise to systemrequirements.System Requirement IdentifierSR-00010-FUN-GENSR-00020-FUN-GENUser Requirement IdentifierUR-GE-01UR-GE-02UR-GE-04SR-00021-FUN-GENUR-GE-02UR-GE-04SR-00030-FUN-GENSR-00040-FUN-GENSR-00050-FUN-GENSR-00060-FUN-GENSR-00070-FUN-GENN.A. to User RequirementN.A. to User RequirementN.A. to User RequirementN.A. to User RequirementUR-GE-02UR-PR-01UR-PR-02UR-PR-03UR-PR-04UR-SM-01

H -SAFSystem Requirement DocumentDoc. No: SAF/HSAF/SRD/2.1Issue: Version 2.1Date: 20/06/2008Page: 87/102System Requirement IdentifierUser Requirement IdentifierUR-SN-01UR-SN-02UR-SN-04SR-10010-FUN-ACQUR-GE-02UR-GE-13UR-PR-01UR-PR-02UR-PR-03UR-PR-04UR-SM-01UR-SM-03UR-SM-05UR-SM-06UR-SM-07UR-SN-01UR-SN-02SR-10020-FUN-ACQSR-10030-FUN-ACQN.A. to User RequirementUR-GE-01UR-GE-02SR-10090-FUN-ACQUR-GE-01UR-GE-02SR-10100-FUN-ACQUR-GE-01UR-GE-02SR-10110-FUN-ACQUR-GE-01UR-GE-02UR-GE-03UR-GE-14SR-10120-FUN-ACQSR-10130-FUN-ACQUR-GE-14UR-PR-05

H -SAFSystem Requirement DocumentDoc. No: SAF/HSAF/SRD/2.1Issue: Version 2.1Date: 20/06/2008Page: 88/102System Requirement IdentifierUser Requirement IdentifierUR-SN-04UR-SN-10UR-SN-11SR-11010-FUN-ACQUR-SM-01UR-SM-02SR-11030-FUN-ACQSR-11040-FUN-ACQUR-SM-03UR-SM-01UR-SM-05SR-12010-FUN-ACQSR-12011-FUN-ACQSR-12020-FUN-ACQSR-12021-FUN-ACQSR-12030-FUN-ACQSR-12031-FUN-ACQSR-12040-FUN-ACQSR-12041-FUN-ACQSR-12050-FUN-ACQUR-PR-02UR-PR-02UR-PR-02UR-PR-02UR-PR-02UR-PR-02UR-PR-02UR-PR-02UR-PR-02UR-GE-02UR-SN-01UR-SN-02UR-SN-04SR-12051-FUN-ACQUR-PR-02UR-GE-02UR-SN-01UR-SN-02UR-SN-04SR-12060-FUN-ACQSR-12061-FUN-ACQSR-12070-FUN-ACQUR-PR-02UR-PR-02UR-PR-02

H -SAFSystem Requirement DocumentDoc. No: SAF/HSAF/SRD/2.1Issue: Version 2.1Date: 20/06/2008Page: 89/102System Requirement IdentifierSR-12071-FUN-ACQSR-12080-FUN-ACQSR-12081-FUN-ACQSR-12100-FUN-ACQSR-12110-FUN-ACQSR-12111-FUN-ACQSR-12120-FUN-ACQSR-12130-FUN-ACQSR-12140-FUN-ACQSR-12150-FUN-ACQSR-12160-FUN-ACQSR-12220-FUN-ACQUser Requirement IdentifierUR-PR-02UR-PR-02UR-PR-02UR-PR-01UR-PR-01UR-PR-01UR-PR-03UR-PR-03UR-PR-03UR-PR-03UR-PR-03UR-PR-06UR-PR-07UR-GE-14SR-12240-FUN-ACQUR-GE-02UR-PR-03UR-PR-05SR-12250-FUN-ACQUR-GE-02UR-PR-05SR-12260-FUN-ACQUR-GE-02UR-PR-05SR-12270-FUN-ACQUR-GE-02UR-PR-05SR-12280-FUN-ACQUR-GE-02UR-PR-05SR-12300-FUN-ACQUR-PR-06UR-PR-07SR-13010-FUN-ACQUR-SN-01UR-SN-02

H -SAFSystem Requirement DocumentDoc. No: SAF/HSAF/SRD/2.1Issue: Version 2.1Date: 20/06/2008Page: 90/102System Requirement IdentifierSR-13015-FUN-ACQSR-13020-FUN-ACQUser Requirement IdentifierUR-SN-01UR-SN-02UR-SN-01UR-SN-02SR-13025-FUN-ACQSR-13030-FUN-ACQUR-SN-01UR-SN-02UR-GE-02UR-SN-04SR-13040-FUN-ACQUR-GE-02UR-SN-01UR-SN-02UR-SN-04SR-13050-FUN-ACQSR-13060-FUN-ACQUR-SN-04UR-SN-01UR-SN-02SR-13070-FUN-ACQUR-GE-02UR-SN-04SR-13080-FUN-ACQUR-SN-01UR-SN-02SR-13090-FUN-ACQSR-13100-FUN-ACQSR-14010-FUN-ACQUR-SN-01UR-SN-02UR-SN-01UR-SN-02UR-GE-02UR-GE-03SR-14020-FUN-ACQUR-GE-02UR-GE-03SR-14030-FUN-ACQUR-GE-02UR-GE-03

H -SAFSystem Requirement DocumentDoc. No: SAF/HSAF/SRD/2.1Issue: Version 2.1Date: 20/06/2008Page: 91/102System Requirement IdentifierUser Requirement IdentifierUR-GE-07SR-14040-FUN-ACQUR-GE-02UR-GE-03UR-GE-07SR-20010-FUN-PPRUR-GE-01UR-GE-02UR-GE-03SR-20020-FUN-PPRUR-GE-06UR-SM-01UR-SM-02SR-30010-FUN-PRGSR-30020-FUN-PRGUR-GE-06UR-GE-02UR-GE-06UR-GE-07UR-PR-01UR-PR-02UR-PR-03SR-30030-FUN-PRGUR-PR-11UR-SM-04UR-SN-05SR-30040-FUN-PRGUR-PR-11UR-SM-04UR-SN-05SR-31010-FUN-PRGUR-GE-01UR-SM-05SR-31020-FUN-PRGUR-GE-02UR-SM-05SR-31030-FUN-PRGUR-GE-02UR-SM-05

H -SAFSystem Requirement DocumentDoc. No: SAF/HSAF/SRD/2.1Issue: Version 2.1Date: 20/06/2008Page: 92/102System Requirement IdentifierSR-31040-FUN-PRGUser Requirement IdentifierUR-GE-02UR-SM-05SR-31060-FUN-PRGUR-GE-02UR-SM-05SR-31061-FUN-PRGUR-GE-02UR-SM-05SR-31070-FUN-PRGUR-GE-01UR-SM-06UR-SM-07SR-31080-FUN-PRGUR-GE-02UR-SM-01UR-SM-02UR-SM-06UR-SM-07SR-31090-FUN-PRGUR-GE-02UR-SM-06UR-SM-07SR-31100-FUN-PRGUR-GE-02UR-SM-06UR-SM-07SR-31150-FUN-PRGUR-SM-01UR-SM-02UR-SM-06UR-SM-07SR-31270-FUN-PRGUR-SM-04UR-SM-08SR-32010-FUN-PRGUR-GE-01UR-PR-01UR-PR-02

H -SAFSystem Requirement DocumentDoc. No: SAF/HSAF/SRD/2.1Issue: Version 2.1Date: 20/06/2008Page: 93/102System Requirement IdentifierUser Requirement IdentifierUR-PR-03UR-PR-06SR-32011-FUN-PRGUR-GE-01UR-PR-01UR-PR-02UR-PR-03UR-PR-07SR-32020-FUN-PRGUR-GE-02UR-PR-01UR-PR-02UR-PR-03UR-PR-06SR-32021-FUN-PRGUR-GE-02UR-PR-01UR-PR-02UR-PR-03UR-PR-07SR-32030-FUN-PRGUR-GE-02UR-PR-01UR-PR-02UR-PR-03UR-PR-06SR-32031-FUN-PRGUR-GE-02UR-PR-01UR-PR-02UR-PR-03UR-PR-07SR-32040-FUN-PRGUR-GE-02UR-PR-01

H -SAFSystem Requirement DocumentDoc. No: SAF/HSAF/SRD/2.1Issue: Version 2.1Date: 20/06/2008Page: 94/102System Requirement IdentifierUser Requirement IdentifierUR-PR-02UR-PR-03UR-PR-06SR-32041-FUN-PRGUR-GE-02UR-PR-01UR-PR-02UR-PR-03UR-PR-07SR-32060-FUN-PRGUR-GE-02UR-PR-01UR-PR-02UR-PR-03UR-PR-06UR-GE-01UR-PR-08SR-32061-FUN-PRGUR-GE-02UR-PR-01UR-PR-02UR-PR-03UR-PR-07UR-GE-01UR-PR-09SR-32062-FUN-PRGUR-GE-01UR-PR-10UR-PR-09UR-PR-10SR-32063-FUN-PRGSR-32070-FUN-PRGSR-32080-FUN-PRGUR-PR-16UR-PR-16UR-PR-09

H -SAFSystem Requirement DocumentDoc. No: SAF/HSAF/SRD/2.1Issue: Version 2.1Date: 20/06/2008Page: 95/102System Requirement IdentifierUser Requirement IdentifierUR-PR-10SR-32090-FUN-PRGUR-PR-09UR-PR-10SR-32230-FUN-PRGUR-PR-09UR-PR-10SR-32240-FUN-PRGUR-PR-11UR-PR-12SR-33040-FUN-PRGUR-GE-01UR-GE-02UR-SN-06SR-33050-FUN-PRGUR-GE-01UR-GE-02UR-SN-08SR-33051-FUN-PRGUR-GE-01UR-GE-02UR-SN-08SR-33060-FUN-PRGUR-GE-01UR-GE-02UR-SN-10SR-33060-FUN-PRGUR-GE-01UR-GE-02UR-SN-16SR-33070-FUN-PRGUR-GE-02UR-SN-06SR-33080-FUN-PRGUR-GE-02UR-SN-08SR-33090-FUN-PRGSR-33100-FUN-PRGUR-SN-15UR-GE-02UR-SN-16

H -SAFSystem Requirement DocumentDoc. No: SAF/HSAF/SRD/2.1Issue: Version 2.1Date: 20/06/2008Page: 96/102System Requirement IdentifierSR-33110-FUN-PRGUser Requirement IdentifierUR-GE-02UR-SN-13SR-33120-FUN-PRGUR-GE-02UR-SN-14SR-33125-FUN-PRGSR-33130-FUN-PRGUR-SN-15UR-GE-02UR-SN-16SR-33140-FUN-PRGUR-GE-02UR-SN-03UR-SN-13SR-33150-FUN-PRGUR-GE-02UR-SN-03UR-SN-14SR-33160-FUN-PRGUR-GE-02UR-SN-03UR-SN-15SR-33170-FUN-PRGSR-33200-FUN-PRGUR-SN-16UR-GE-01UR-GE-02UR-SN-13SR-33210-FUN-PRGUR-GE-01UR-GE-02UR-SN-15SR-33220-FUN-PRGUR-GE-01UR-GE-02UR-SN-16SR-33230-FUN-PRGUR-GE-02UR-SN-13SR-33240-FUN-PRGUR-GE-02

H -SAFSystem Requirement DocumentDoc. No: SAF/HSAF/SRD/2.1Issue: Version 2.1Date: 20/06/2008Page: 97/102System Requirement IdentifierUser Requirement IdentifierUR-SN-15SR-33250-FUN-PRGUR-GE-02UR-SN-16SR-33260-FUN-PRGUR-GE-02UR-SN-13SR-33270-FUN-PRGUR-GE-02UR-SN-15SR-33280-FUN-PRGUR-GE-02UR-SN-16SR-33290-FUN-PRGUR-GE-02UR-SN-03UR-SN-13SR-33300-FUN-PRGUR-GE-02UR-SN-03UR-SN-15SR-33310-FUN-PRGUR-GE-02UR-SN-03UR-SN-16SR-33320-FUN-PRGSR-33330-FUN-PRGSR-33340-FUN-PRGSR-34010-FUN-VPRSR-34020-FUN-VPRSR-34030-FUN-VPRSR-34040-FUN-VPRSR-34050-FUN-VPRSR-34060-FUN-VPRSR-34110-FUN-REPUR-SN-09UR-SN-09UR-SN-09UR-HY-04UR-HY-05UR-HY-06UR-HY-07UR-HY-08UR-HY-08UR-RD-04UR-RD-05

H -SAFSystem Requirement DocumentDoc. No: SAF/HSAF/SRD/2.1Issue: Version 2.1Date: 20/06/2008Page: 98/102System Requirement IdentifierUser Requirement IdentifierUR-RD-06SR-34120-FUN-REPUR-RD-04UR-RD-05UR-RD-06SR-34130-FUN-REPUR-RD-04UR-RD-05UR-RD-06SR-34140-FUN-REPUR-RD-04UR-RD-05UR-RD-06SR-34150-FUN- REPUR-RD-04UR-RD-05UR-RD-06SR-34160-FUN- REPUR-RD-04UR-RD-05UR-RD-06SR-34170-FUN-REPUR-RD-04UR-RD-05UR-RD-06SR-34180-FUN-REPUR-RD-04UR-RD-05UR-RD-06SR-44010-FUN-ARCUR-GE-03UR-GE-06SR-44020-FUN-ARCUR-GE-03UR-GE-06SR-44021-FUN-ARCUR-GE-03UR-GE-06SR-44030-FUN-ARCUR-GE-03

H -SAFSystem Requirement DocumentDoc. No: SAF/HSAF/SRD/2.1Issue: Version 2.1Date: 20/06/2008Page: 99/102System Requirement IdentifierUser Requirement IdentifierUR-GE-06SR-44040-FUN-ARCUR-GE-03UR-GE-06SR-44050-FUN-ARCSR-44060-FUN-ARCSR-44070-FUN-ARCSR-44080-FUN-ARCSR-44090-FUN-ARCSR-54010-FUN-DISUR-GE-06UR-GE-06UR-GE-06UR-GE-06UR-GE-06UR-GE-03UR-GE-06SR-54020-FUN-DISUR-GE-03UR-GE-06SR-54030-FUN-DISUR-GE-03UR-GE-06SR-54040-FUN-DISUR-GE-03UR-GE-06SR-54050-FUN-DISUR-GE-06UR-GE-03UR-GE-07SR-54060-FUN-DISUR-GE-03UR-GE-06UR-GE-07SR-54070-FUN-DISUR-GE-03UR-GE-07SR-54080-FUN-DISUR-GE-03UR-GE-07SR-54091-FUN-DISSR-54120-FUN-DISUR-GE-03UR-GE-03UR-GE-06

H -SAFSystem Requirement DocumentDoc. No: SAF/HSAF/SRD/2.1Issue: Version 2.1Date: 20/06/2008Page: 100/102System Requirement IdentifierSR-54130-FUN-DISUser Requirement IdentifierUR-GE-03UR-GE-06SR-54150-FUN-DISUR-GE-03UR-GE-06SR-54160-FUN-DISUR-GE-03UR-GE-06SR-54170-FUN-DISUR-GE-03UR-GE-06SR-54180-FUN-DISUR-GE-03UR-GE-06SR-70010-RAM-GENSR-70020-RAM-GENSR-70030-RAM-GENSR-70040-RAM-GENSR-70050-RAM-GENSR-70060-RAM-GENSR-70070-RAM-GENSR-80010-OPE-GENSR-80020-OPE-GENSR-80040-OPE-GENSR-80050-OPE-GENSR-91000-PER-GENN.A. to User RequirementN.A. to User RequirementN.A. to User RequirementN.A. to User RequirementN.A. to User RequirementN.A. to User RequirementN.A. to User RequirementN.A. to User RequirementN.A. to User RequirementN.A. to User RequirementUR-GE-14UR-GE-02UR-GE-03UR-GE-06SR-91020-FUN-PRGSR-92010-POR-GENSR-92020-POR-GENSR-92030-POR-GENSR-92040-POR-GENN.A. to User RequirementN.A. to User RequirementN.A. to User RequirementN.A. to User RequirementN.A. to User Requirement

H -SAFSystem Requirement DocumentDoc. No: SAF/HSAF/SRD/2.1Issue: Version 2.1Date: 20/06/2008Page: 101/102System Requirement IdentifierSR-93010-RES-GENSR-93050-RES-GENSR-93060-RES-GENSR-93070-RES-GENSR-93080-RES-GENSR-94010-SAF-GENSR-94020-SAF-GENSR-94030-SAF-GENSR-94040-SAF-GENSR-95010-SEC-GENSR-95020-SEC-GENSR-95030-SEC-GENSR-96010-DOC-GENUser Requirement IdentifierN.A. to User RequirementN.A. to User RequirementUR-GE-03UR-GE-15UR-GE-15N.A. to User RequirementN.A. to User RequirementN.A. to User RequirementN.A. to User RequirementN.A. to User RequirementN.A. to User RequirementN.A. to User RequirementN.A. to User RequirementTable 19 System Requirements traceability vs User Requirements

H -SAFSystem Requirement DocumentDoc. No: SAF/HSAF/SRD/2.1Issue: Version 2.1Date: 20/06/2008Page: 102/102- END OF THE DOCUMENT-