hydrology saf system requirement...

H-SAF System Requirement Document

Doc. No: SAF/HSAF/SRD/2.1

Issue: Version 2.1

Date: 20/06/2008

Page: 1/102

Hydrology SAF

System Requirement Document

Reference Number: SAF/HSAF/SRD/2.1

Issue/Revision Index: Issue 2.1

Last Change: 20/06/2008



Issue: Version 2.1

Date: 20/06/2008

Page: 2/102

DOCUMENT SIGNATURE TABLE

Name Date Signature

Prepared by : H-SAF Project Team 08/02/2008

Approved by : H-SAF Project Manager 08/02/2008

DOCUMENT CHANGE RECORD

Issue / Revision Date Description

Version 0.1 17/03/2006 Preliminary version prepared for discussion

Version 0.5 31/03/2006 Prepared for RR

Version 0.6 13/09/2006 Acknowledgements of RR RIDs:

adoption of UML 2.0 notation and adding of [RD 19], [RD 20],

[RD 21], [RD 22] (this acknowledges RID 74 decision a)

Insertion of TBDs/TBCs list (this acknowledges RIDs 34, 52, 54,

55, 56, 57)

Verification method of SR-96010-TVA-GEN, SR-96020-TVA-

GEN, SR-96030-TVA-GEN, SR-96040-TVA-GEN and SR-

96050-TVA-GEN modifed to “T” (this acknowledges RID 58)

Remotion of quality and testing requirements; modification of

SR-80010-OPE-GEN reference from “critical software” to

“operational software”; (this acknowledges RID 22)

Version 1.0 07/11/2006 Prepared for PDR:

SR-10000-FUN-ACQ turned to SR-00070-FUN-GEN and

updated table

SR-11010-FUN-ACQ, SR-11030-FUN-ACQ, SR-11040-FUN-

ACQ modified due to evolution of Soil Moisture chain

SR-11020-FUN-ACQ, SR-11050-FUN-ACQ to SR-11120-FUN-

ACQ, SR-31120-FUN-PRG, SR-31190-FUN-PRG deleted

because no longer valid



Issue: Version 2.1

Date: 20/06/2008

Page: 3/102

Version 1.1 14/06/2007 Updated Release prepared for V1CP:

Correction of pagination and editorial adjustment as

acknowledgement of RID 102 and RID 111

Review of Applicable Documents list and Reference Documents list as acknowledgement of RID 114: transfer of items to the second 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 input resolution. This acknowledges RID 116

Modification of requirement SR-11010-FUN-ACQ for the local acquisition of ERS 1/2 data to Soil Moisture subsystem, described in Table 6 but not still present as a requirement. (this acknowledges RID 117 and RID 29).

Insertion of a clarification about source data and auxiliary data in the Functional Requirements section, to avoid misunderstanding in the comprehension of Table 6. (Acknowledgement of RID 118).

Version 2.0 08/02/2008 New baseline for CDR. Document preparation includes the following

updates:

Modification of SR-10020-FUN-ACQ with insertion of a

clarification about erroneous data and its management, as

acknowledgement of RID 27.

Modification of SR-10030-FUN-ACQ for a better specification of

archived satellite data description, as acknowledgement of RID

28

Completion of Product Output format list for dissemination (this

acknowledge RID 32).

Update and further details addition on timeliness for

dissemination to NRT users is provided (this acknowledge RID

112).



Issue: Version 2.1

Date: 20/06/2008

Page: 4/102

Version 2.1 20/06/2008 Acknowledgements of CDR RIDs:

Clarifications and corrections on satellite data interfaces, in

Section 2.5 (RID 2)

Drop of requirement SR-91010-PER-ACQ (RID 5)

Modification of Table 4 : completion of interface description

and specification of baseline interface for satellite data

resources (RID 3 and RID 32)

Correction of Section 1.4.1 “Applicable Documents” (RID

30)

Completion of Table 1 with missing roles of project partners

(RID 31)

Completion of glossary (RID33)

Reformulation of requirements SR-13070-FUN-ACQ and

SR-54150-FUN-DIS; drop of requirement SR-91010;

editorial revision of all requirements (RID 34)

Modification of Table 19 and insertion of necessary

explanations (RID 35)



Issue: Version 2.1

Date: 20/06/2008

Page: 5/102

DISTRIBUTION LIST

Country Organization Name Contact

Austria ZAMG Veronika Zwatz-Meise [email protected]

ZAMG Alexander Jann [email protected]

TU-Wien / IPF Wolfgang Wagner [email protected]

TU-Wien / IPF Stefan Hasenauer [email protected]

Belgium IRM Emmanuel Roulin [email protected]

IRM Gaston Demaree [email protected]

ECMWF Philippe Bougeault [email protected]

Matthias Drusch [email protected]

Klaus Scipal [email protected]

Finland FMI Pirkko Pylkko [email protected]

FMI Jarkko Koskinen [email protected]

FMI Jouni Pulliainen [email protected]

FMI Panu Lahtinen [email protected]

TKK Juha-Petri Karna [email protected]

SYKE Sari Metsämäki [email protected]

France Météo France Jean-Christophe Calvet [email protected]

Météo France Laurent Franchisteguy [email protected]

CNRS-CETP Mehrez Zribi [email protected]

CNRS-CESBIO Patricia de Rosnay [email protected]

Germany BfG Thomas Maurer [email protected]

Hungary OMSZ Eszter Lábó [email protected]

Italy USAM Massimo Capaldo [email protected]

CNMCA Luigi De Leonibus [email protected]

CNMCA Costante De Simone [email protected]

CNMCA Francesco Zauli [email protected]

CNMCA Daniele Biron [email protected]

mailto:alexander.jann@zamg

mailto:emmanuel.roulin@oma

mailto:gaston.demaree@oma

mailto:philippe.bougeault@ecmwf

mailto:matthias.drusch@ecmwf

mailto:klaus.scipal@ecmwf

mailto:pirkko.pylkko@fmi

mailto:jarkko.koskinen@fmi

mailto:jouni.pulliainen@fmi

mailto:panu.lahtinen@fmi

mailto:juha-petri.karna@tkk

mailto:sari.metsamaki@ymparisto

mailto:jean-christophe.calvet@meteo

mailto:laurent.franchisteguy@meteo

mailto:mehrez.zribi@cetp

mailto:thomas.maurer@bafg

mailto:labo.e@met

mailto:m.capaldo@meteoam

mailto:l.deleonibus@meteoam

mailto:c.desimone@meteoam

mailto:f.zauli@meteoam

mailto:d.biron@meteoam



Issue: Version 2.1

Date: 20/06/2008

Page: 6/102


CNMCA Davide Melfi [email protected]

CNMCA Attilio Di Diodato [email protected]

CNMCA Lucio Torrisi [email protected]

CNMCA Massimo Bonavita [email protected]

CNMCA Adriano Raspanti [email protected]

CNMCA Alessandro Galliani [email protected]

DPC Roberto Sorani [email protected]

DPC Luca Rossi [email protected]

DPC Silvia Puca [email protected]

DPC Angela Corina [email protected]

DPC William Nardin [email protected]

CNR-ISAC Franco Prodi [email protected]

CNR-ISAC Bizzarro Bizzarri [email protected]

CNR-ISAC Alberto Mugnai [email protected]

CNR-ISAC Vincenzo Levizzani [email protected]

CNR-ISAC Francesca Torricella [email protected]

CNR-ISAC Stefano Dietrich [email protected]

CNR-ISAC Francesco Di Paola [email protected]

Ferrara University Federico Porcu’ [email protected]

Ferrara University Davide Capacci [email protected]

ELSAG DATAMAT Flavio Gattari [email protected]

ELSAG DATAMAT Emiliano Agosta [email protected]

Poland IMWM Piotr Struzik [email protected]

IMWM Bozena Lapeta [email protected]

IMWM Jerzy Niedbala [email protected]

IMWM Jaga Niedbala [email protected]

IMWM Monika Pajek [email protected]

IMWM Jakub Walawender [email protected]

IMWM Jan Szturc [email protected]

mailto:d.melfi@meteoam

mailto:a.didiodato@meteoam

mailto:l.torrisi@meteoam

mailto:m.bonavita@meteoam

mailto:a.raspanti@meteoam

mailto:a.galliani@meteoam

mailto:hsaf.management@protezionecivile

mailto:luca.rossi@protezionecivile

mailto:silvia.puca@protezionecivile

mailto:angela.corina@protezionecivile

mailto:william.nardin@protezionecivile

mailto:f.prodi@isac

mailto:a.mugnai@isac

mailto:v.levizzani@isac

mailto:f.torricella@isac

mailto:s.dietrich@isac

mailto:francesco.dipaola@ifa

mailto:flavio.gattari@datamat

mailto:emiliano.agosta@datamat

mailto:piotr.struzik@imgw

mailto:bozena.lapeta@imgw

mailto:jerzy.niedbala@imgw

mailto:jaga.niedbala@imgw

mailto:monika.pajek@imgw

mailto:jakub.walawender@imgw

mailto:jan.szturc@imgw



Issue: Version 2.1

Date: 20/06/2008

Page: 7/102


Romania NMA Andrei Diamandi [email protected]

NMA Simona Oancea [email protected]

Slovakia SHMÚ Ján Kaňák [email protected]

SHMÚ Marián Jurašek [email protected]

SHMÚ Marcel Zvolenský [email protected]

Turkey TSMS Fatih Demýr [email protected]

TSMS Ali Umran Komuscu [email protected]

TSMS Ibrahim Sonmez [email protected]

TSMS Aydın Erturk [email protected]

METU Ali Unal Sorman [email protected]

METU Zuhal Akyurek [email protected]

METU Orhan Gokdemir [email protected]

METU Ozgur Beser [email protected]

ITU Ahmet Oztopal [email protected]

Anadolu University Aynur Sensoy [email protected]

EUMETSAT Lorenzo Sarlo [email protected]

Frédéric Gasiglia [email protected]

Dominique Faucher [email protected]

Jochen Grandell [email protected]

Lothar Schüller [email protected]

mailto:simona.oancea@meteo

mailto:jan.kanak@shmu

mailto:marian.jurasek@shmu

mailto:marcel.zvolensky@shmu

mailto:orhan.gokdemir@gmail

mailto:lorenzo.sarlo@eumetsat

mailto:frederic.gasiglia@eumetsat

mailto:dominique.faucher@eumetsat

mailto:jochen.grandell@eumetsat

mailto:lothar.schueller@eumetsat



Issue: Version 2.1

Date: 20/06/2008

Page: 8/102

TABLE OF CONTENTS

1 Introduction .............................................................................................................. 11

1.1 Purpose of the Document .................................................................................... 11

1.2 Document Overview ............................................................................................ 11

1.3 Glossary .............................................................................................................. 12

1.4 References .......................................................................................................... 18

1.4.1 Applicable documents .................................................................................. 18

1.4.2 Reference documents .................................................................................. 18

2 General Description ................................................................................................. 19

2.1 Purpose of the H-SAF ......................................................................................... 19

2.2 Outlines of the H-SAF consortium ....................................................................... 20

2.3 Products / Deliveries of the H-SAF ...................................................................... 21

2.4 System Overview ................................................................................................ 24

2.5 General Constraints ............................................................................................ 26

3 Specific Requirements ............................................................................................. 29

3.1 Functional requirements ...................................................................................... 32

3.1.1 General Requirements ................................................................................. 32

3.1.2 Data Acquisition Requirements .................................................................... 37

3.1.3 Pre-Processing Requirements ..................................................................... 48

3.1.4 Product Generation Requirements ............................................................... 49

3.1.5 Hydrovalidation Processing Requirements .................................................. 60

3.1.6 Hydrovalidation Reporting Requirements ..................................................... 63

3.1.7 Archival Requirements ................................................................................. 65

3.1.8 Dissemination Requirements ....................................................................... 67

3.2 Reliability, Availability and Maintenance Requirements ...................................... 70

3.3 Operational Requirements .................................................................................. 71

3.4 Performance Requirements ................................................................................ 72

3.5 Portability Requirements ..................................................................................... 74

3.6 Resources Requirements .................................................................................... 76

3.7 Safety Requirements ........................................................................................... 77

3.8 Security Requirements ........................................................................................ 78

3.9 Documentation Requirements ............................................................................. 79



Issue: Version 2.1

Date: 20/06/2008

Page: 9/102

4 TBDs/TBCs list ......................................................................................................... 79

5 Requirements traceability ........................................................................................ 79

5.1 System Requirements traceability to H-SAF Subsystems ................................... 79

5.2 System Requirements traceability to User Requirements ................................... 86



Issue: Version 2.1

Date: 20/06/2008

Page: 10/102

LIST OF TABLES

Table 1 Outlines of H-SAF Consortium ............................................................................. 21

Table 2 Satellite-derived H-SAF products and satellite data sources ................................ 23

Table 3 Backup products generated by a NWP model ...................................................... 23

Table 4 H-SAF External Interfaces for Data Acquisition .................................................... 29

Table 5 Classes of messages ............................................................................................ 33

Table 6 H-SAF Data sources ............................................................................................. 36

Table 7 Information related to satellite data ....................................................................... 38

Table 8 Elements for soil moisture consistency control ..................................................... 55

Table 9 Formats for Hydrovalidation processing ............................................................... 61

Table 10 Timings for Hydrovalidation processing .............................................................. 62

Table 11 Input data and parameters used by selected operational hydrological models ... 63

Table 12 Payload information for Hydrovalidation reports ................................................. 64

Table 13 Header information for Hydrovalidation reports .................................................. 64

Table 14 Output data formats for Hydrovalidation reports ................................................. 65

Table 15 Formats for data dissemination to Hydro Validation Subsystem ......................... 69

Table 16 Time limits in products generation/dissemination ............................................... 74

Table 17 Software coding languages ................................................................................ 76

Table 18 System Requirements traceability vs H-SAF subsystems .................................. 85

Table 19 System Requirements traceability vs User Requirements ................................ 101

LIST OF FIGURES

Figure 1: H-SAF system decomposition ............................................................................ 25



Issue: Version 2.1

Date: 20/06/2008

Page: 11/102

1 Introduction

1.1 Purpose of the Document

This document specifies the system requirements for the Hydrology SAF (H-SAF). It

focuses mainly on product generation features, as the main objective of H-SAF system is

to provide new satellite derived products in order to satisfy the needs of operational

hydrology. It identifies the requirements regarding products, functions, components and

interfaces as they have been described in the Project Plan [AD 2] and in the User

Requirement Document [AD 4]. It is the input for the architectural specification of the

system, describedI in the System Design Document.

In accordance with the project phasing depicted in the Project Plan, the System

Requirements Document (SRD) has to be released in a preliminary version at the

Requirement Review and in baseline version at the Preliminary Design Review.

An updating of SRD (current document) has been made necessary as consequence of

URD and PP modifications. So this document should be considered as the new SRD

baseline version.

1.2 Document Overview

The H-SAF System Requirement Document is structured as follows:

Chapter 1: Introduces the purpose of the document, provide the references and a list of

acronyms

Chapter 2: Gives a general description of H-SAF system in terms of purpose, outlines of

consortium, 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 item

and a planned date for resolution.

Chapter 5: Presents the traceability of the System Requirements versus the User

Requirements 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]; all

diagrams 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 and

System Engineering.



Issue: Version 2.1

Date: 20/06/2008

Page: 12/102

These principles are particularly meaningful in the H-SAF context, since H-SAF is a

complex system into which the software layer is just one of many different layers building

up the heterogeneous set-up.

1.3 Glossary

AAPP AVHRR and ATOVS Processing Package

ADEOS Advanced Earth Observation Satellite (I and II)

ALOS Advanced Land Observing Satellite

AMIR Advanced Microwave Imaging Radiometer

AMSR Advanced Microwave Scanning Radiometer (on ADEOS-II)

AMSR-E Advanced Microwave Scanning Radiometer–- E (on EOS-Aqua)

AMSU-A Advanced Microwave Sounding Unit–- A (on NOAA satellites and EOS-Aqua)

AMSU-B Advanced Microwave Sounding Unit–- B (on NOAA satellites up to NOAA-17)

API Application Program(ming) Interface

ASAR Advanced SAR (on ENVISAT)

ASCAT Advanced Scatterometer (on MetOp)

ASI Agenzia Spaziale Italiana

ATDD Algorithms Theoretical Definition Document

ATMS Advanced Technology Microwave Sounder (on NPP and NPOESS)

ATOVS Advanced TIROS Operational Vertical Sounder (on NOAA and MetOp)

AU Anatolian University

AVHRR Advanced Very High Resolution Radiometer (on NOAA and MetOp)

BAMPR Bayesian Algorithm for Microwave Precipitation Retrieval

BfG Bundesanstalt für Gewässerkunde

BRDF Bi-directional Reflectance Distribution Function

BVA Boundary Value Analysis

CASE Computer Aided System Engineering

CBA Component-Based Architecture

CBSD Component-based Software Development

CDA Command and Data Acquisition (EUMETSAT station at Svalbard)

CDD Component Design Document

CDR Critical Design Review

CESBIO Centre ’'Etudes Spatiales de la BIOsphere (of CNRS)

CETP Centre d’études des Environnements Terrestres et Planétaires (of CNRS)

CI Configuration Item

CMIS Conical-scanning Microwave Imager/Sounder (on NPOESS)

CMP Configuration Management Plan



Issue: Version 2.1

Date: 20/06/2008

Page: 13/102

CNMCA Centro Nazionale di Meteorologia e Climatologia Aeronautica

CNR Consiglio Nazionale delle Ricerche

CNRM Centre Nationale de la Recherche Météorologique (of Météo-France)

CNRS Centre Nationale de la Recherche Scientifique

COM Component Object Model

CORBA Common Object Request Broker Architecture

COTS Commercial-off-the-shelf

CPU Central Processing Unit

CR Component Requirement

CRD Component Requirement Document

CVERF Component Verification File

CVS Concurrent Versions System

DCOM Distributed Component Object Model

DEM Digital Elevation Model

DFD Data Flow Diagram

DMSP Defense Meteorological Satellite Program

DOF Data Output Format

DPC Dipartimento della Protezione Civile

DWD Deutscher Wetterdienst

E&T Education and Training

EARS EUMETSAT Advanced Retransmission Service (station)

ECMWF European Centre for Medium-range Weather Forecasts

ECSS European Cooperation on Space Standardization

EGPM European contribution to the GPM mission

EOS Earth Observing System

EPS EUMETSAT Polar System

ERS European Remote-sensing Satellite (1 and 2)

ESA European Space Agency

EUR End-User Requirements

FMI Finnish Meteorological Institute

FOC Full Operational Chain

FTP File Transfer Protocol

GEO Geostationary Earth Orbit

GIS Geographical Information System

GMES Global Monitoring for Environment and Security

GOMAS Geostationary Observatory for Microwave Atmospheric Sounding

GOS Global Observing System

GPM Global Precipitation Measurement mission

GPROF Goddard Profiling algorithm



Issue: Version 2.1

Date: 20/06/2008

Page: 14/102

GTS Global Telecommunication System

GUI Graphical User Interface

HMS Hungarian Meteorological Service

HRU Hydrological Response Unit

H-SAF SAF on support to Operational Hydrology and Water Management

HSB Humidity Sounder for Brazil (on EOS-Aqua)

HTML Hyper Text Markup Language

HTTP Hyper Text Transfer Protocol

HUT/LST Helsinki University of Technology / Laboratory of Space Technology

HV Hydrovalidation (referred to Hydro Validation Subsystem items, e.g.: reports, components etc.)

HVR Hydrological Validation Review

HYDRO Preliminary results of Hydrological validation

HYDROS Hydrosphere State Mission

HW Hardware

ICD Interface Control Document

ICT Information and Communication Technology

IEEE Institute of Electrical and Electronics Engineers

IFS Integrated Forecast System

INF Progress reports in between meetings

INWM Institute of Meteorology and Water Management (of Poland)

IPF Institut für Photogrammetrie und Fernerkundung

ISAC Istituto di Scienze dell’Atmosfera e del Clima (of CNR)

ISO International Standards Organization

IT Information Technology

ITU Istanbul Technical University

JPS Joint Polar System (MetOp + NOAA/NPOESS)

J2EE Java 2 Enterprise Edition

KIDS Kestrel Interactive Development System

KLOC Thousand (Kilo) Lines Of Code

KOM Kick-Off Meeting

LAI Leaf Area Index

LAN Local Area Network

LEO Low Earth Orbit

LIS Lightning Imaging Sensor (on TRMM)

LLS Lower Level Specifications

LOC Lines Of Code

LRIT Low-Resolution Information Transmission

LST Solar Local Time (of a sun-synchronous satellite)

MARS Meteorological Archive and Retrieval System



Issue: Version 2.1

Date: 20/06/2008

Page: 15/102

MetOp Meteorological Operational satellite

METU Middle East Technical University (of Turkey)

MHS Microwave Humidity Sounder (on NOAA N/N’ and MetOp)

MIMR Multi-frequency Imaging Microwave Radiometer

MIN Minutes of Meetings/Reviews

MODIS Moderate-resolution Imaging Spectro-radiometer (on EOS Terra and Aqua)

MSG Meteosat Second Generation

MTBF Mean Time Between Failure

MTG Meteosat Third Generation

MTTR Mean Time To Repair

MVIRI Meteosat Visible Infra-Red Imager (on Meteosat 1 to 7)

N/A Not Available

N.A. Not Applicable

NASA National Aeronautics and Space Administration

NATO North Atlantic Treaty Organisation

NDI Non-developmental Items

NIMH National Institute for Meteorology and Hydrology (of Hungary)

NMS National Meteorological Service

NOAA National Oceanic and Atmospheric Organisation (intended as a satellite series)

NPOESS National Polar-orbiting Operational Environmental Satellite System

NPP NPOESS Preparatory Programme

NRT Near-Real Time

NWP Numerical Weather Prediction

OAR Options Analysis for Reengineering

OFL Off-line

OM Offline Monitoring (referred to Offline Monitoring Subsystem items, e.g.: components)

OMG Object Management Group

OO Object Oriented

OP Proposal for H-SAF Operational phase

OPS Operational Product Segment

ORB Object Request Broker

ORR Operations Readiness Review

OWL Web Ontology Language

PAC Prototype Algorithm Code

PALSAR Phased Array L-band Synthetic Aperture Radar (on ALOS)

PAW Plant Available Water

PDR Preliminary Design Review

POP Precipitation Observation Production

PP Project Plan



Issue: Version 2.1

Date: 20/06/2008

Page: 16/102

PPR Products Prototyping Reports

PR Precipitation (referred to Precipitation Subsystem items, e.g.: products, components etc.)

PRB Problem Review Board

QoS Quality of Service

R&D Research and Development

RCS Revision Control System

REP Report

RMI Royal Meteorological Institute (of Belgium)

RR Requirements Review

RT Real Time

SAAM Simulation, Analysis and Modeling

SAF Satellite Application Facility

SAG Science Advisory Group

SAOCOM Argentinean Satellite for Observation and Communication

SAR Synthetic Aperture Radar

SA/SD Structured Analysis / Structured Design

SCA Snow Covered Area

SCAT Scatterometer (on ERS-1 and 2)

SCM Source Configuration Management

SD Snow depth

SDAS Surface Data Assimilation System

SDD System Design Document

SDP Software Development Plan

SEI Software Engineering Institute

SEVIRI Spinning Enhanced Visible Infra-Red Imager (on MSG)

SHW State Hydraulic Works of Turkey

SHFWG SAF Hydrology Framework Working Group

SHMI Slovakian Hydrological and Meteorological Institute

SIRR System Integration Readiness Review

SIVVP System Integration, Verification & Validation Plan

SLAs Service-Level Agreements

SM Soil Moisture (referred to Soil Moisture Subsystem items, e.g.: products, components etc.)

SMART Service Migration and Reuse Technique

SMMR Scanning Multichannel Microwave Radiometer (on SeaSat and Nimbus VII)

SMOS Soil Moisture and Ocean Salinity

SN Snow Parameters (referred to Snow Parameters Subsystem products)

SOA Service-Oriented Architecture

SoS System of Systems

SP Snow Parameters (referred to Snow Parameters Subsystem items, e.g.: components)

http://en.wikipedia.org/wiki/Revision_Control_System



Issue: Version 2.1

Date: 20/06/2008

Page: 17/102

SQL Structured Query Language

SR System Requirement

SRD System Requirements Document

SSM/I Special Sensor Microwave / Imager (on DMSP up to F-15)

SSMIS Special Sensor Microwave Imager/Sounder (on DMSP starting with F-16)

SSVD System/Software Version Document

STRR System Test Results Review

SVALF System Validation File

SVERF System Verification File

SVRR System Validation Results Review

SW Software

SWE Snow Water Equivalent

SYKE Finnish Environment Institute

TBC To be confirmed

TBD To be defined

TC Test Case

TKK/LST Helsinki University of Technology / Laboratory of Space Technology

TLE Two-line-element (telemetry data format)

TMI TRMM Microwave Imager (on TRMM)

TP Test Procedure

TR Test Report

TRMM Tropical Rainfall Measuring Mission

TSMS Turkish State Meteorological Service

TU Wien Technische Universität Wien

UM User Manual

U-MARF Unified Meteorological Archive and Retrieval Facility

UML Unified Modelling Language

UR User Requirement

URD User Requirements Document

VIIRS Visible/Infrared Imager Radiometer Suite (on NPP and NPOESS)

VS Visiting Scientist

WBS Work Breakdown Structure

WMO World Meteorological Organization

WP Work Package

WPD Work Package Description

WS Workshop

W3C World Wide Web Consortium

XMI XML (eXtensible Markup Language ) Metadata Interchange

XML eXtensible Markup Language



Issue: Version 2.1

Date: 20/06/2008

Page: 18/102

ZAMG Zentral Anstalt für Meteorologie und Geodynamik

1.4 References

1.4.1 Applicable documents

[AD 1] H-SAF Development Proposal - Issue 2.1, 15 May 2005

[AD 2] H-SAF Project Plan (PP). Ref.: SAF/HSAF/PP/2.1

[AD 3] H-SAF Configuration Management Plan (CMP). Ref.: SAF/HSAF/CMP/1.0

[AD 4] H-SAF Users Requirement Document (URD). Ref.: SAF/HSAF/URD/2.1

[AD 5] H-SAF SAF Preliminary Design Review Organization Note. Ref.:

EUM/PPS/PRC/06/0125

[AD 6] H-SAF System Requirements Document (SRD). Ref.: SAF/HSAF/SRD/2.0

[AD 7] Algorithmic Software Development Guidelines Document (ASDGD). Ref.:

SAF/HSAF/ASDGD/0.1

[AD 8] System Integration, Verification & Validation Plan (SIVVP). Ref.: SAF/HSAF/SIVVP/1.0

[AD 9] Guide to Software Configuration Management. Ref.: ESA PSS-05-09 Issue 1 Revision

1

[AD 10] SAF Software Development Guidelines. Ref.: SAF/NET/EUM/SW/GD/MTR/01

[AD 11] H-SAF Algorithmic Software Development Guidelines Document (ASDGD) – internal

issue – Ref.: SAF/HSAF/ASDGD/0.5

[AD 12] Algorithms Theoretical Definition Document (ATDD) - Ref.: SAF/HSAF/ATDD/1.1

[AD 13] H-SAF System Verification File (SVERF). Ref.: SAF/HSAF/SVERF/0.5

[AD 14] H-SAF System/Software Version Document (SSVD). Ref.: SAF/HSAF/SSVD/0.5

1.4.2 Reference documents

[RD 1] EUM.TD.08 MSG - Image Data Dissemination Service

[RD 2] EPS AMSU-A L1 Product Generation Specification

[RD 3] EPS AMSU-A L1 Product Format Specification

[RD 4] EPS MHS L1 Product Generation Specification

[RD 5] EPS MHS L1 Product Format Specification

[RD 6] MetOp-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_Gener

ation/index.html=en)

http://rst.vcs.de/

http://directreadout.gsfc.nasa.gov/index.cfm

http://www.eumetsat.int/Home/Main/What_We_Do/Satellites/Meteosat_Second_Generation/index.html=en

http://www.eumetsat.int/Home/Main/What_We_Do/Satellites/Meteosat_Second_Generation/index.html=en



Issue: Version 2.1

Date: 20/06/2008

Page: 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] EPS NRT User Interface Specification. Ref.: EPS-ASPI-IR-0648

[RD 11] National Oceanic and Atmospheric Administration (NOAA) Low-Rate Information

Transmission (LRIT) System. Ref.: http://noaasis.noaa.gov/LRIT/

[RD 12] WMO–WWWDM specifications. Ref.: http://www.wmo.ch/web/www/WDM/wdm.html

[RD 13] MARS – Meteorological Archive and Retrieval System, MARS User Guide (for Data

Retrieval), Revision 11 – September 1995, Meteorological Bulletin B6.7/3, ECMWF

Reading, England. Ref.: http://www.wmo.ch/web/www/WDM/wdm.html

[RD 14] MSG Level 1.5 Image Data Format Description. Ref.: ESA PSS-05-09 Issue 1 Revision

1

[RD 15] ECSS Standard on Space engineering. Verification. Ref.: ECSS-E-10-02A

[RD 16] ECSS Standard on Space engineering. Testing. Ref.: ECSS-E-10-03A

[RD 17] ECSS Standard on Space engineering. Software - Part 1: Principles and requirements.

Ref.: ECSS-E-40 Part 1B

[RD 18] ECSS Standard on Space engineering. Software - Part 2: Document requirements

definitions (DRDs). Ref.: ECSS-E-40 Part 2B

[RD 19] Object Management Group, Inc. (OMG), “Unified Modelling Language: Infrastructure”

Version 2.0 – 05/072005

[RD 20] Object Management Group, Inc. (OMG), “Unified Modelling Language: Superstructure”

Version 2.0 – 05/072005

[RD 21] Object Management Group, Inc. (OMG), “Unified Modelling Language: Diagram

Interchange” Version 2.0 – 05/072005

[RD 22] Object Management Group, Inc. (OMG), “Unified Modelling Language: Business

Modelling” Version 2.0 – 05/072005

[RD 23] Brown, Alan W. & Wallnau, Kurt C. "Engineering of Component-Based Systems".

Component-Based Software Engineering: Selected Papers from the Software

Engineering Institute. Los Alamitos, CA: IEEE Computer Society Press, 1996.

[RD 24] Jim Rumbaugh, Ivar Jacobson, Grady Booch. “The Unified Modeling Language

Reference Manual (2nd edition)”

2 General Description

2.1 Purpose of the H-SAF

The main objectives of H-SAF are:

a. to provide new satellite-derived products from existing and future satellites with sufficient time and space resolution to satisfy the needs of

http://www.eumetsat.int/Home/Main/What_We_Do/EUMETCast/index.html=en

http://noaasis.noaa.gov/LRIT/



Issue: Version 2.1

Date: 20/06/2008

Page: 20/102

operational hydrology, by generating, centralizing, archiving and disseminating the identified products:

precipitation (liquid, solid, rate, accumulated);

soil moisture (at large-scale, at local-scale, at surface, in the roots region);

snow parameters (detection, cover, melting conditions, water equivalent);

b. to perform independent validation of the usefulness of the new products for fighting against floods, landslides, avalanches, and evaluating water resources; the activity includes:

downscaling/upscaling modelling from observed/predicted fields to basin level;

fusion of satellite-derived measurements with data from radar and raingauge networks;

assimilation of satellite-derived products in hydrological models;

assessment of the impact of the new satellite-derived products on hydrological applications.

2.2 Outlines of the H-SAF consortium

The H-SAF participants and their roles are reported as follows (see also [AD 2]:

No. Country Units in the Country Role in the Project

01 Austria

Zentralanstalt für Meteorologie und

Geodynamik Leader for soil moisture

Vienna University of Technology, Inst. of

Photogram. & Remote Sensing

02 Belgium

Royal Meteorological Institute of Belgium Contributor for validation of

PR, SM and SP products and

for Hydro validation

03 ECMWF European Centre for Medium-range

Weather Forecasts

Contributor for “core” soil

moisture

04 Finland

Finnish Meteorological Institute (FMI) Leader for snow parameters.

Contributor for development

and validation of SN products

and for Hydro validation

Helsinki University of Technology,

Laboratory of Space Technology

Finnish Environment Institute



Issue: Version 2.1

Date: 20/06/2008

Page: 21/102

05 France

Météo-France Contributor for development

and validation of SM products

and for Hydro validation CNRS Centre d'Etudes Spatiales de la

BIOsphere

CNRS Centre d’études des Environnem.

Terrestres et Planétaires

06 Germany

Bundesanstalt für Gewässerkunde Contributor for validation of

PR and SP products and for

Hydro validation

07 Hungary Hungarian Meteorological Service Contributor for validation of

PR products

08 Italy

Servizio Meteorologico dell’Aeronautica

Host + Leader for precipitation

Dipartimento Protezione Civile,

Presidenza Consiglio Ministri

CNR Istituto di Scienze dell’Atmosfera e

del Clima

Ferrara University, Department of

Physics

09 Poland Institute of Meteorology and Water

Management

Leader for Hydrology

10 Romania National Institute for Meteorology and

Hydrology

Contributor for development of

SP products

11 Slovakia

Slovakia Hydro-Meteorological Institute Contributor for validation of

PR products and for Hydro

validation

12 Turkey

Turkish State Meteorological Service

Contributor for “core” snow

parameters

Middle East Technical University, Civil

Engineering Department

Istanbul Technical University,

Meteorological Department

Table 1 Outlines of H-SAF Consortium

2.3 Products / Deliveries of the H-SAF

The following table lists the targeted satellite-derived H-SAF products.



Issue: Version 2.1

Date: 20/06/2008

Page: 22/102

The Table lists the satellites to be used pre-operationally and experimentally during the

Development Phase and those to be available during the Operational Phase (> 2010).

Precipitation Anticipated product quality in the operational phase Satellites / Sensors

products Resolution Accuracy Cycle Delay Development Operations

Precipitation

rate (by MW

only) with flag

for phase

10 km (MIS)

15 km (additional GPM

satellites)

10-20 % (> 10 mm/h)

20-40 % (1-10 mm/h)

40-80 % (< 1 mm/h)

9 h (MIS

only)

3 h (full

GPM)

20 min

Meteosat

(MVIRI, SEVIRI)

+

DMSP

(SSM/I, SSMIS)

+

NOAA + MetOp

(AMSU-A,

AMSU-B/MHS)

+

EOS/Aqua

(AMSR-E,

AMSU-A, HSB)

+

TRMM

(TMI, PR, LIS)

Meteosat

(SEVIRI)

+

NPP

(ATMS)

+

NPOESS

(CMIS, ATMS)

+

Further satellites

of the GPM

(all equipped at

least with a MW

radiometer, one

also with radar)

Precipitation

rate (by MW +

IR) with flag

for phase

10 km

Ranging from that of

MW to one degraded

by an extent

15 min 10 min

Cumulate

precipitation

(by MW + IR)

on 3, 6, 12, 24 h

10 km

Tentative:

10 % over 24 h

30 % over 3 h

3 h 20 min

Soil moisture Anticipated product quality in the operational phase Satellites / Sensors


Soil moisture in

the surface

layer

25 km (from ASCAT)

50 km (from MIS)

0.05 m3 m-3 (depending

on vegetation)

36 h (from

ASCAT)

9 h (from

MIS)

2 h

ERS 1 / 2

(AMI-SCAT)

+

MetOp

(ASCAT)

+

EOS/Aqua

(AMSR-E)

MetOp

(ASCAT)

+

NPOESS

(MIS)

Soil moisture in

the roots region

25 km (from ASCAT)

50 km (from MIS)

To be assessed

(model-dependent).

Tentative: 0.05 m3 m-3

36 h (from

ASCAT)

9 h (from

MIS)

2 h

Snow Anticipated product quality in the operational phase Satellites / Sensors




Issue: Version 2.1

Date: 20/06/2008

Page: 23/102

Snow detection

by optical

bands

2 km 95 % probability of

correct classification

6 h

(depending

on latitude)

2 h

NOAA

(AVHRR)

+

MetOp

(AVHRR, ASCAT)

+

Meteosat

(SEVIRI)

+

EOS-Terra/Aqua

(MODIS)

+

DMSP

(SSM/I, SSMIS)

+

EOS-Aqua

(AMSR-E)

+

QuickSCAT

(SeaWinds)

MetOp

(AVHRR, ASCAT)

+

Meteosat

(SEVIRI)

+

NPOESS

(VIIRS, MIS)

+

MW radiometers

of the GPM

constellation

Effective cover

by optical and

MW bands, with

flag for wet/dry

10 km (in MW)

5 km (in

VIS/SWIR/TIR)

15 % (depending on

target size and

complexity)

6 h

(depending

on latitude)

2 h

Snow Water

Equivalent by

MW radiometer

+ scatterometer

10–25 km ~ 20 mm

6 h

(depending

on latitude)

2h

Table 2 Satellite-derived H-SAF products and satellite data sources

In addition to satellite-derived products, H-SAF will make available forecast products

derived by a NWP limited-area model, so that end-users have available a back-up product

at any time. The targeted forecast products are shown as follows (Table 3).

Forecast products Resolution Accuracy (long term > 2010) Cycle Delay

Instantaneous

precipitation rate

at the ground

Mid-project: 7 km,

end-project: 2.5 km

10-20 % (> 10 mm/h)

20-40 % (1-10 mm/h)

40-80 % (< 1 mm/h)

Mid-project: 3-6

h,

end-project: 1 h

Fixed times

of the day

Accumulated

precipitation

10 % over 24 h, 30 % over 3 h.

Table 3 Backup products generated by a NWP model

The Development Phase, in addition to including the activities for developing and

generating new satellite-derived products, includes a Hydrology validation programme,

performed by “Cluster-4”, lead by Poland; this aim shall be achieved through a complex

set of activities and working programs, fully explained in details in the Project Plan [AD 2]



Issue: Version 2.1

Date: 20/06/2008

Page: 24/102

2.4 System Overview

The 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 databases

other SAF’s products

locally available auxiliary/ancillary data

NWP model and climatology data.

a structure for hydrological validation of all products and for generation of validation reports, physically distributed among seven countries and centrally managed and coordinated by Poland as stated in [AD 2]

existing dedicated communication networks (regional branches of the WMO Global Telecommunication System, dissemination system based on connection with EUMETSAT for re-distribution via EUMETCast) for immediate dissemination of products 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 all generated 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 -SAF System Requirement Document


Issue: Version 2.1

Date: 20/06/2008

Page: 25/102

id System Decomposition

«system»

HSAF

UMARF

client

«subsystem»

Precipitation

«subsystem»

Snow Parameters

«subsystem»

Soil Moisture

«subsystem»

Offline Monitoring

EUMETSAT::

UMARF

Representativ e End

User(from Representative End-Users)

Data Source

(from Data Sources)

SCIENTIFIC USERS (R&D Institutes)

request HSAF product via UMARF

system

WMO::GTS

EUMETSAT::

EUMETCast

EUMETSAT::PPF

«subsystem»

Hydro Validation

Figure 1: H-SAF system decomposition



Issue: Version 2.1

Date: 20/06/2008

Page: 26/102

In this architecture, as detailed in the System Design Document, five main subsystems

have been identified:

1. Precipitation Subsystem: in charge of acquiring and pre-processing input data,

generating Precipitation (Observation and Assimilation) products, performing

quality control processes and activities and disseminating products to end users;

2. Soil Moisture Subsystem, in charge of acquiring and pre-processing input

data, generating Soil Moisture (Observation and Assimilation) products,

performing quality control processes and activities and disseminating products

to end users;

3. Snow Parameter Subsystem, in charge of acquiring and pre-processing input

data, generating Snow Parameters (flat/forested, mountainous and merged)

products, performing quality control activities and disseminating products to end

users;

4. Hydro Validation Subsystem, in charge of providing independent assessment

of the usefulness of H-SAF products in operational hydrology and water

management, performing near-real-time acquisition of all products and carrying

out hydrological validation activities using available tools and consolidated

methods and models. It also provides valuable output for cal/val and validation

reports used by production subsystems for possible products quality

improvements;

5. Offline Monitoring Subsystem, in charge of acquiring products and validation

reports from the other subsystems, storing them in a central online/offline

archive, disseminating the archived data in OFL to scientific users via U-MARF

interface and performing a monitoring on dissemination results.

2.5 General Constraints

The availability of envisaged satellite data (current and planned) is a constraint both for the

development and for the operational phase of H-SAF. For this reason it is relevant to

depict some details about the situation at the time being (i.e. to be used pre-operationally

and experimentally in development phase). The following table summarises this situation

and states, for each data sources, which of the specified access means is the one

considerd baseline:

Data Source Interface



Issue: Version 2.1

Date: 20/06/2008

Page: 27/102

Data Source Description Baseline for operations

SEVIRI Meteosat 8 LRIT Backup

NRT via EUMETCast Baseline

AMSU-A NOAA Direct read-out Baseline

NRT via EUMETCast Backup

AMSU-B NOAA 17 Direct read-out Baseline


SSM/I DMSP 15 NRT via EUMETCast Baseline if implemented

FTP from UKMO Current baseline

SSMIS DMSP 16 NRT via EUMETCast Baseline if implemented

FTP from UKMO Current baseline

MHS MetOp Direct read-out Baseline if implemented

NRT via EUMETCast Current baseline

AMSU-A MetOp Direct read-out Baseline if implemented


NWP ECMWF Dedicated link

Synoptic

Observation

WMO-GOS GTS

Auxiliary/Ancillary

Data

(various) OFL

MHS NOAA 18 Direct read-out Baseline


MVIRI (2) Meteosat 7 U-MARF

AMSR-E (for

precipitation)

EOS-Aqua FTP

ATMS (1) NPP NRT via EUMETCast If implemented

LIS (1) TRMM FTP and other NASA



Issue: Version 2.1

Date: 20/06/2008

Page: 28/102



interfaces

PR (1) TRMM FTP and other NASA

interfaces

TMI (1) TRMM FTP and other NASA

interfaces

ASCAT MetOp NRT via EUMETCast Backup (Level-1 data)

AMI-SCAT (5) ERS 1/2 OFL

ASAR (6) Envisat OFL

Level-2

processed

MetOp/ ASCAT

data (7)

EUMETSAT-PPF NRT via EUMETCast

AVHRR NOAA Direct read-out Baseline


AVHRR MetOp Direct read-out Baseline if implemented


MODIS EOS-Aqua Direct read-out Baseline if implemented

FTP Current baseline

AMSR-E for

snow EOS-Aqua

Direct read-out Baseline if implemented


MODIS EOS-Terra Direct read-out Baseline if implemented


NASA Archived

Data

NASA FTP

NOAA Archived

Data

NOAA FTP

ECMWF ECMWF FTP



Issue: Version 2.1

Date: 20/06/2008

Page: 29/102



Archived Data

Table 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 risk

analysis, see [AD 2]) (4) availability of instrument is not certain (managed in Project Plan risk analysis, see [AD

2]) (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 available

Note: Direct read-out data acquisition from NOAA-17, NOAA-18, MetOp and Meteosat-9

shall be replaced in case of acquisition failure by NRT acquisition via EUMETCast

All 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 User

Requirement Document and in the Project Plan will be available in the envisaged timing.

Anyway, instruments-related requirements are here adequately flagged, and this

document will take into account of their evolution.

3 Specific Requirements

In this section the H-SAF System Requirements are presented, following some

conventions described next.

1 – Requirement Composition

Each requirement is composed of:

Requirement Identifier: univocally identifies the requirement throughout the document following the naming convention described hereinafter.



Issue: Version 2.1

Date: 20/06/2008

Page: 30/102

<Requirement Title>: optional, is a short requirement description.

<Requirement Level>: 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 (desirable requirement);

o R: Instrument-related: the requirement is related to the availability of a specific instrument which is not certain at the time being; this aspect is described in Project Plan risk analysis [AD 2].

o When not appropriately filled, the related requirement is considered as mandatory and not instrument-related.

Subsystem identifier: identifies the H-SAF subsystem specifically related to the requirement; if missing, the requirement is mapped to the whole system.

Verification Method: describes the method to be used for verifying the requirement compliance. The following values can be used:

o Analysis [A]

o When verification is achieved by performing theoretical or empirical evaluation by accepted techniques, the method shall be referred to as Analysis

o Review of Design [R]

o When verification is achieved by validation of records or by evidence of validated design documents or when approved design reports, technical descriptions, engineering drawings unambiguously show the requirement is met, the method shall be referred as Review-of-design

o Inspection [I]

o When verification is achieved by visual determination of physical characteristics (such as construction features, hardware conformance to document drawing or workmanship requirements) the method shall be referred to as Inspection.

o Demonstration [D]

o This verification method may be used when actual conduct can verify achievement of requirements such as service and access, transportability, human engineering features and qualitative features. A requirement which is of an operational or functional nature and is not quantified by a specific measurable parameter may be verified by demonstration.

o Test [T]

o When requirements have to be verified by measuring product performance and function under various simulated environments, the method shall be referred to as Test; these measurements may require the use of special equipment, instrumentation and simulation techniques; the analysis of data derived from Test shall be considered an integral part of the test. When relevant, Test also gives evidence of qualitative operational performance and requirements. The performance, as proved, shall be observed and recorded.

Requirement Description: full description of the requirement.

<Requirement Source>: optional, applicable document the requirement derives from.



Issue: Version 2.1

Date: 20/06/2008

Page: 31/102

<Comment>: optional field which intends to provide additional information, justification, or explanation of the requirement. Comment is for information only and is not considered part of the requirement.

2- Requirement Identifier

The requirement identifier has been coded in this document as follows:

SR-NNNNN-XXX-YYY

where:

SR System Requirement

NNNNN Progressive number, unique for each requirement.

XXX One of the following requirement classes:

FUN Functional

PER Performance

OPE Operational

INT Interface

DES Design

QUA Quality

RAM Reliability, Availability, Maintenance

POR Portability

RES Resources

TVA Test, Verification and Acceptance

DOC Documentation

SAF Safety

SEC Security

YYY One of the following functional areas

GEN General

ACQ Data acquisition

PPR Pre-processing

PRG Product generation

VPR HydroValidation Processing

REP Reporting

ARC Archiving

DIS Distribution/Dissemination

VMQ Validation, Monitoring and Quality Control

In order to improve the document readability, the requirements have been grouped

together following a two levels decomposition structure:



Issue: Version 2.1

Date: 20/06/2008

Page: 32/102

First level: by requirement class

Second level: by functional area.

Note: the second decomposition level can be missing when not applicable or when a

limited number of requirements are present within the class.

3.1 Functional requirements

For a better comprehension of the below list and in particular of the Table 6, a clarification

has 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 in

order to improve quality/accuracy; data sources, instead, are intended as the input data

flows which act as the fundamental starting point in production processes.

3.1.1 General Requirements

SR-00010-FUN-GEN Level Component PR, SM, SP

Description Products shall be automatically generated by operational chains

Comment Verification T


Description The geographical region of product appliance shall be Europe (including

Turkey) and North Africa


SR-00021-FUN-GEN Level Component HV

Description The geographical region of hydrovalidation appliance shall be Europe

(including Turkey) and North Africa


SR-00030-FUN-GEN Level Component ALL



Issue: Version 2.1

Date: 20/06/2008

Page: 33/102

Description The system shall be able to identify classes of error conditions within the

ones listed in Table 5


Class Description of the notification message

INFO Non-threatening information to the user.

E.g.: a simple splash screen to notify an alert

WARNING Potential dangerous operation in advance.

E.g.: "Warning: this operation will erase your data."

ERROR Critical situation.

E.g.: "There is not enough memory to install the

application."

ALARM Notification about something in progress or to be

done

E.g.: "Staff meeting in five minutes."

CONFIRMATION Non-threatening information to the user.

E.g.: "The file has been saved."

Table 5 Classes of messages


Description Error codes shall be identified by a unique identifier code



Description The system shall handle system warnings or alarms messages on the

basis of error classes





Issue: Version 2.1

Date: 20/06/2008

Page: 34/102

Description UTC time reference shall be used throughout all manual activities and

automatic processes

Comment Verification I


Description System shall be able to receive data listed in Table 6 via the interfaces

there specified.


Data Source Interface Description

Data Source

SEVIRI Meteosat 8 Direct read-out (only for 9)

NRT via EUMETCast

AMSU-A NOAA 17 Direct read-out

NRT via EUMETCast

AMSU-A NOAA 18 Direct read-out

NRT via EUMETCast

AMSU-B NOAA 17 Direct read-out

NRT via EUMETCast

SSM/I DMSP 15 NRT via EUMETCast

FTP from UKMO

SSMIS DMSP 16 NRT via EUMETCast

FTP from UKMO

MHS (4) MetOp Direct read-out

NRT via EUMETCast

AMSU-A (4) MetOp Direct read-out

NRT via EUMETCast

NWP UKMO FTP



Issue: Version 2.1

Date: 20/06/2008

Page: 35/102


Data Source

Synoptic / Observation WMO-GTS RT

Auxiliary/Ancillary Data (various) OFL

MHS (3) NOAA 18 Direct read-out

NRT via EUMETCast

MVIRI (2) Meteosat 7 Direct read-out

NRT via EUMETCast

AMSR-E (1) EOS-Aqua FTP

ATMS (1) NPP (1)

Gras (1) MetOp (1)

LIS (1) TRMM FTP and other NASA interfaces

PR (1) TRMM FTP and other NASA interfaces

TMI (1) TRMM FTP and other NASA interfaces

ASCAT MetOp Direct read-out

AMI-SCAT (5) ERS 1/2 OFL

ASAR (6) Envisat OFL

Level-1 and 2

processed MetOp/

ASCAT data (7)

EUMETSAT-PPF NRT via EUMETCast

Synoptic / Observation WMO-GTS RT

Auxiliary Data (various) OFL

AVHRR NOAA Direct read-out

NRT via EUMETCast

AVHRR MetOp Direct read-out

NRT via EUMETCast

Modis EOS-Aqua Direct read-out

FTP



Issue: Version 2.1

Date: 20/06/2008

Page: 36/102


Data Source

AMSR-E (8) EOS-Aqua FTP

Modis EOS-Terra Direct read-out

FTP

SEVIRI Meteosat NRT via EUMETCast

SSM/I (9) DMSP FTP

SSMIS (9) DMSP FTP

Synoptic / Observation

Data WMO-GTS RT

NASA Archived Data NASA FTP

NOAA Archived Data NOAA FTP

ECMWF Archived Data ECMWF FTP

Table 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 risk

analysis, see [AD 2] ) (4) availability of instrument is not certain (managed in Project Plan risk analysis, see [AD

2]) (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 available

Note: Direct read-out data acquisition from NOAA-17, NOAA-18, MetOp and Meteosat-9

shall be replaced in case of acquisition failure by NRT acquisition via EUMETCast



Issue: Version 2.1

Date: 20/06/2008

Page: 37/102

3.1.2 Data Acquisition Requirements

SR-10010-FUN-ACQ Level O Component ALL

Description Data input listed in Table 6 should be archived locally (either physically or

virtually) and made accessible to the H-SAF central archive

Comment It should be made in order to enable

reconstruction of time series, or re-

calibration and/or re-processing by

advanced algorithms. Re-processing

activity shall be carried out upon

decision by Project Team and Steering

Group

Verification T

SR-10020-FUN-ACQ Level Component ALL

Description Input filters shall reject automatically erroneous data

Comment As a matter of principle, whereas

possible data correction and/or warning

is preferred to automatical rejection.

Rejection is achieved only when data is

unambiguously recognized as erroneous

data type by the involved algorithm

facility

Verification T

SR-10030-FUN-ACQ Level O Component ALL

Description Archival of satellite data should allow identification of information listed in

Table 7


Satellite data information

Satellite identifier

Satellite coordinates

Satellite time information



Issue: Version 2.1

Date: 20/06/2008

Page: 38/102

Satellite data information

Channel availability

Sensor Identifier

Data version

Table 7 Information related to satellite data


Description Source of auxiliary data shall be identified



Description Time information of time-related auxiliary data shall be identified



Description Failure in acquiring mandatory data shall not cause abnormal interruption

of operational chain of product generation



Description Failure in acquiring mandatory data shall cause an error rising and

logging


SR-10130-FUN-ACQ Level Component PR, SM, SP

Description System shall be able to acquire synoptic observation data through WMO-

GTS




Issue: Version 2.1

Date: 20/06/2008

Page: 39/102

3.1.2.1 Precipitation subsystem

SR-12010-FUN-ACQ Level Component PR

Description System shall acquire AMSU-A data from NOAA-17 through direct-read-

out interface



Description System shall acquire AMSU-A data from NOAA-17 through NRT interface

via EUMETCast



Description System shall acquire AMSU-B data from NOAA-17 through direct-read-

out interface



Description System shall acquire AMSU-B data from NOAA-17 through NRT interface

via EUMETCast



Description System shall acquire AMSU-A data from NOAA-18 through direct-read-

out interface



Description System shall acquire AMSU-A data from NOAA-18 through NRT interface

via EUMETCast



Issue: Version 2.1

Date: 20/06/2008

Page: 40/102



Description System shall acquire MHS data from NOAA-18 through direct-read-out

interface



Description System shall acquire MHS data from NOAA-18 through NRT interface via

EUMETCast


SR-12050-FUN-ACQ Level R Component PR

Description System shall acquire AMSU-A data from NOAA-N’(19) through direct-

read-out interface

Comment instrument related requirement:

availability of instrument is not certain

(managed in Project Plan risk analysis

[AD 2])

Verification T


Description System shall acquire AMSU-A data from NOAA-N’(19) through NRT

interface via EUMETCast




[AD 2])

Verification T




Issue: Version 2.1

Date: 20/06/2008

Page: 41/102

Description System shall acquire MHS data from NOAA-N’(19) through direct-read-

out interface

Comment Instrument related requirement:



[AD 2])

Verification T


Description System shall acquire MHS data from NOAA-N’(19) through NRT interface

via EUMETCast




[AD 2])

Verification T


Description System shall acquire AMSU-A data from MetOp through direct-read-out

interface




[AD 2])

Verification T


Description System shall acquire AMSU-A data from MetOp through NRT interface

via EUMETCast




[AD 2])

Verification T




Issue: Version 2.1

Date: 20/06/2008

Page: 42/102

Description System shall acquire MHS data from MetOp through direct-read-out

interface




[AD 2])

Verification T


Description System shall acquire MHS data from MetOp through NRT interface via

EUMETCast




[AD 2])

Verification T


Description System shall acquire SEVIRI data from Meteosat8 through NRT interface

via EUMETCast



Description System shall acquire SEVIRI data from Meteosat 9 through direct-read-

out interface



Description System shall acquire SEVIRI data from Meteosat 9 through NRT interface

via EUMETCast




Issue: Version 2.1

Date: 20/06/2008

Page: 43/102


Description System shall acquire SSM/I data from DMSP-15 through NRT interface

Comment actually, for most of the HSAF Development Phase these data shall be acquired from FTP from UKMO

Verification T


Description System shall acquire SSMIS data from DMSP-16 through NRT interface


Verification T



Comment actually, for most of the HSAF Development Phase these data shall be acquired through FTP from UKMO

Verification T

SR-12150-FUN-ACQ Level Component



Verification T




Verification T




Issue: Version 2.1

Date: 20/06/2008

Page: 44/102

Description Direct acquisition of NOAA-17, NOAA-18, MetOp, Meteosat-9 data shall

be replaced in case of acquisition failure by NRT acquisition via

EUMETCast


SR-12240-FUN-ACQ Level O Component PR

Description System should be able to acquire lightning data as auxiliary data in

precipitation chain

Comment data is needed for quality control Verification T


Description System should be able to acquire VIS/IR/MW image data as auxiliary data

in precipitation chain



Description System should be able to acquire meteorological analysis data as

auxiliary data in precipitation chain



Description System should be able to acquire data from raingauge networks as

auxiliary data in precipitation chain



Description System should be able to acquire rain data images as auxiliary data in

precipitation chain




Issue: Version 2.1

Date: 20/06/2008

Page: 45/102


Description System shall be able to acquire boundary conditions data from ECMWF


3.1.2.2 Soil moisture subsystem

SR-11010-FUN-ACQ Level Component SM

Description System shall be able to acquire through NRT interface via EUMETCast

the level II processed MetOp ASCAT data at 25 km resolution (SM-OBS-

1) and level I one, generated by EUMETSAT-PPF

Comment Level I ASCAT product shall be used for

producing the SM-OBS-1 backup

product. Moreover ERS-1&2 AMI-SCAT

archived data (only in absence of

ASCAT data and for testing the surface

soil moisture products generation chain)

from TU-Wien H-SAF component

Verification T


Description System shall be able to access European Parameter database, data

about land cover, operational snow cover maps, freeze/thaw cycles, water

bodies, and topography as auxiliary data

Comment data is needed for the disaggregation of

the surface soil moisture product

Verification T


Description System shall be able to access modelled root zone soil moisture (first

guess) coming from IFS as auxiliary data

Comment data is needed for the assimilation of

satellite-derived product in hydrological

model

Verification T



Issue: Version 2.1

Date: 20/06/2008

Page: 46/102

3.1.2.3 Snow Parameters subsystem

SR-13010-FUN-ACQ Level Component SP

Description system shall be able to acquire data from EOS-aqua and terra data from

MODIS through direct-read-out interface



Description system shall be able to acquire data from EOS-aqua and terra data from

MODIS through FTP interface



Description system shall be able to acquire AVHRR data from NOAA through direct-

read-out interface



Description System shall acquire AMSR-E data from EOS-Aqua through FTP

interface

Comment at the time being there is a problem with

direct read-out

Verification T


Description System shall acquire SSM/I data from DMSP through FTP from UKMO

Comment might not be actually used, at least until

EOS-Aqua/AMSR-E is available

Verification T




Issue: Version 2.1

Date: 20/06/2008

Page: 47/102

Description System shall acquire SSMIS data from DMSP through FTP from UKMO

Comment might not be actually used, at least until

EOS-Aqua/AMSR-E is available

Verification T


Description System shall access to synoptic/observation data in RT through WMO-

GTS



Description System shall be able to access, through FTP, NOAA and NASA archived

data

Comment Verification D

SR-13080-FUN-ACQ Level O Component SP

Description System should be able to access, through FTP, ECMWF archived data



Description system shall be able to acquire AVHRR data from MetOp through direct-

read-out interface



Description system shall be able to acquire AVHRR data from NOAA through NRT

interface via EUMETCast




Issue: Version 2.1

Date: 20/06/2008

Page: 48/102

3.1.2.4 Hydro Validation subsystem

SR-14010-FUN-ACQ Level Component HV

Description Hydrological validation subsystem shall acquire H-SAF products as an

input data for hydrological models



Description Hydrological validation subsystem shall be able to acquire H-SAF

products through FTP interface via Internet




products in NRT through EUMETCast


SR-14040-FUN-ACQ Level R Component HV


products in RT through WMO GTS


3.1.3 Pre-Processing Requirements

SR-20010-FUN-PPR Level Component ALL

Description Satellite data pre-processing and local archiving shall not be affected by a

failure in reception of data from channels not listed in Table 6




Issue: Version 2.1

Date: 20/06/2008

Page: 49/102

SR-20020-FUN-PPR Level Component PR, SM, SP

Description Satellite raw data from sources described in Table 6 shall be prepared

(pre-processed) as structured data files suitable for processing


3.1.4 Product Generation Requirements

SR-30010-FUN-PRG Level Component PR, SM, SP

Description Products generated within a subsystem shall be archived locally and then

sent to the central archive



Description Products shall be submitted to automatic quality control



Description Quality flags shall be associated to products



Description Generation chains shall be able to receive Hydrovalidation reports from

central archive

Comment central archive is part of Offline

Monitoring subsystem

Verification T



Issue: Version 2.1

Date: 20/06/2008

Page: 50/102

3.1.4.1 Precipitation subsystem

SR-32010-FUN-PRG Level Component PR

Description The system shall produce the “Precipitation rate at ground by MW conical

scanners (with indication of phase)” product (PR-OBS-1)



Description The system shall produce the “Precipitation rate at ground by MW cross-

track scanners (with indication of phase)” product (PR-OBS-2)



Description Resolution of PR-OBS-1 product shall be 10 km (with MIS) or 15 km

(with additional GPM)



Description Resolution of PR-OBS-2 product shall be 10 km (with MIS) or 15 km (with

other GPM)



Description Accuracy 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)



Description Accuracy 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)



Issue: Version 2.1

Date: 20/06/2008

Page: 51/102



Description Frequency of PR-OBS-1 product shall be 9 h (with MIS) or 3 h (with full

GPM)



Description Frequency of PR-OBS-2 product shall be 9 h (with CMIS) or 3 h (with full

GPM)



Description The system shall produce the “Precipitation rate at ground by GEO/IR

supported by LEO/MW” product (PR-OBS-3)



Description The system shall produce the “Precipitation rate at ground by LEO/MW

supported by GEO/IR (with flag for phase)” product (PR-OBS-4)



Description The system shall produce the “Accumulated precipitation at ground by

MW+IR and MW only” product (PR-OBS-5)





Issue: Version 2.1

Date: 20/06/2008

Page: 52/102

Description The system shall produce the “Instantaneous and accumulated

precipitation at the ground computed by a NWP model” product (PR-ASS-

1)


SR-32070-FUN-PRG Level O Component PR

Description System should allow clouds classifications, by mean of SAFNWC/MSG

software package



Description System should provide spatial/time derivative informations on IR and WV

cell pixels, by means of NEFODINA software package



Description System should provide space/time continuised field by assimilating

original precipitation data in LAMI NWP model



Description A database of regular observation of 1-hour cumulated precipitation

parameter shall be locally set up



Description System shall be able to access to datasets for calibration and validation




Issue: Version 2.1

Date: 20/06/2008

Page: 53/102

3.1.4.2 Soil Moisture subsystem

SR-31010-FUN-PRG Level Component SM

Description The system shall produce the “Global surface soil moisture by radar

scatterometer” product (SM-OBS-1)



Description Resolution of SM-OBS-1 product shall be 25 km (from ASCAT) or 50 km

(from MIS)



Description Accuracy of SM-OBS-1 product shall be 0.05 m3 m-3



Description Frequency of SM-OBS-1 product shall be 36 h (from ASCAT) or 9 h (from

MIS)



Description “Regional surface soil moisture by radar scatterometer” product (SM-

OBS-2) shall be derived from SM-OBS-1 one, re-sampling it at 1 km

intervals



Description SM-OBS-2 product shall be corrected in topography and projected to

user-defined coordinate systems



Issue: Version 2.1

Date: 20/06/2008

Page: 54/102



Description The system shall produce the “Volumetric soil moisture (roots region) by

scatterometer assimilation in NWP model” product (SM-ASS-1)



Description Resolution of SM-ASS-1 product shall be 25 km (from ASCAT) and 50 km

(from MIS)


SR-31090-FUN-PRG Level O Component SM

Description Accuracy of SM-ASS-1 product should be 0.05 m3 m-3

Comment it is an attempt only (model dependent) Verification T


Description Frequency of SM-ASS-1 product shall be 36 h (from ASCAT) and 9h

(from MIS)



Description Soil moisture operational chain shall be triggered by the reception of

level-II processed ASCAT data files





Issue: Version 2.1

Date: 20/06/2008

Page: 55/102

Description A reference database for cal/val, which shall archive elements described

in Table 8, shall be set up


Element for SM consistency control

In-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 Analysis

from United States National Snow and Ice Data Center NSIDC, Snow maps

being produced by H-SAF consortium)

Global topography datasets (e.g. United States Geological Survey Global

Topographic 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 control

3.1.4.3 Snow Parameter subsystem

SR-33040-FUN-PRG Level Component SP

Description The system shall produce at FMI the “snow detection (snow mask) by

VIS/IR radiometry” (SN-OBS-1a) observation product in flat/forested area



Description The system shall produce at FMI the “snow status (dry/wet) by MW

radiometry” (SN-OBS-2) observation product in flat/forested area





Issue: Version 2.1

Date: 20/06/2008

Page: 56/102

Description Product SN-OBS-2 shall provide a flag reporting snow status parameter

(dry/wet)

Comment This product shall not be merged with an

analogous product on mountainous

areas, as instead foreseen for the other

three flat/forested products

Verification T


Description The system shall produce at FMI the “effective snow cover by VIS/IR

radiometry” (SN-OBS-3a) observation product in flat/forested area



Description The system shall produce at FMI the “snow water equivalent by MW

radiometry” (SN-OBS-4a) observation product in flat/forested area



Description Resolution of SN-OBS-1a product shall be 2 km



Description Resolution of SN-OBS-2 product shall be 10 km



Description Resolution of SN-OBS-3a product shall be 5 Km




Issue: Version 2.1

Date: 20/06/2008

Page: 57/102


Description Resolution of SN-OBS-4a product shall be 10 km



Description Accuracy of SN-OBS-1a product shall be 95 % probability of correct

classification



Description Accuracy of SN-OBS-2 product shall be 15 % (depending on basin size

and complexity)



Description Accuracy of SN-OBS-3a product shall be 15 % (depending on basin size

and complexity)



Description Accuracy of SN-OBS-4a product shall be about 20 mm



Description Frequency SN-OBS-1a product shall be 6 h (depending on latitude)





Issue: Version 2.1

Date: 20/06/2008

Page: 58/102

Description Frequency of SN-OBS-2 product shall be 6 h (depending on latitude)









Description The system shall produce at TSMS the “snow detection (snow mask) by

VIS/IR radiometry” (SN-OBS-1b) observation product in mountainous

area



Description The system shall produce at TSMS the “effective snow cover by VIS/IR

radiometry” (SN-OBS-3b) observation product in mountainous area



Description The system shall produce at TSMS the “snow water equivalent by MW

radiometry” (SN-OBS-4b) observation product in mountainous area





Issue: Version 2.1

Date: 20/06/2008

Page: 59/102

Description Resolution of SN-OBS-1b product shall be 2 km









Description Accuracy of SN-OBS-1b product shall be 95 % probability of correct

classification



Description Accuracy of SN-OBS-3b product shall be 15 % (depending on basin size

and complexity)



Description Accuracy of SN-OBS-4b product shall be about 20 mm



Description Frequency SN-OBS-1b product shall be 6 h (depending on latitude)




Issue: Version 2.1

Date: 20/06/2008

Page: 60/102








Description The system shall merge at FMI SN-OBS-1a and SN-OBS-1b observation

products generating SN-OBS-1 combined product










3.1.5 Hydrovalidation Processing Requirements

SR-34010-FUN-VPR Level Component HV



Issue: Version 2.1

Date: 20/06/2008

Page: 61/102

Description Hydro validation subsystem shall be able to process H-SAF products in

the formats listed in Table 9

Comment JPEG or similar used for a quick look Verification T

Product format for HV processing

GRIB ver. 1

BUFR ver. 3

HDF-5

ASCII

JPEG or similar

Table 9 Formats for Hydrovalidation processing


Description Hydro validation process in development phase shall be performed daily

at fixed time of the day, except for SN-OBS-4 that shall be performed on

the orbital basis



Description Hydro validation process in operational phase shall be performed

according to timing listed in Table 10


Product Timing

PR-OBS-1 and PR-OBS-2 On the orbital basis / near-real-time

,PR-OBS-3, PR-OBS-4 and PR-ASS-1 Hourly

PR-OBS-5 At standard synoptic time (every 3

hours)

SN-OBS-1a, SN-OBS-1b, SN-OBS-1, On the orbital basis



Issue: Version 2.1

Date: 20/06/2008

Page: 62/102

Product Timing

SN-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 and

SM-ASS-1

Table 10 Timings for Hydrovalidation processing


Description Hydro validation process shall be able to use digital terrain models, land

cover maps, river network data as ancillary data



Description Hydro validation subsystem shall achieve preprocessing of input data in

order to fit input variables to model resolution



Description Hydrological models shall be able to process input parameters with

spatial and temporal resolution as presented in Table 11


Parameter Required spatial resolution Required temporal

resolution

Precipitation Regular grid 50, 100, 500 m: 1, 7, 8

km, HRU, subcatchment

10 min, 15 min, 1h, 3h, 6h,

daily

Snowfall Regular grid 1 km, 8 km, HRU 6 h – daily

Air temperature 8 km, 25 km, point, HRU 10 min, 15 min, 1h, 2h,

daily

Soil moisture point, catchment daily



Issue: Version 2.1

Date: 20/06/2008

Page: 63/102

Snow covered

area

From 50 meter to the full catchment

area daily

Solar radiation 8 km, 50 km, point 15 min,1h, 6h, daily

Snow water

equivalent

From 50 meter to the full catchment

area daily

Long wave

radiation 8 km 1h

Sun duration 50 km 6h

Land use,

vegetation type 30m, 250 m, 1km 10 days, season

Wind speed 7 km, 8 km, 25 km 10 min, 1h, 2h

Humidity 8 km, 50 km, point 1h, 2h, 6 h

Table 11 Input data and parameters used by selected operational hydrological models

3.1.6 Hydrovalidation Reporting Requirements

SR-34110-FUN-REP Level Component HV

Description Hydrological Validation shall provide structured results to be retro-fitted to

the product generation chains.



Description Hydrological Validation subsystem shall be able to generate reports in an

automatic way.



Description Hydrological Validation reports shall include at least payload information

listed in Table 12




Issue: Version 2.1

Date: 20/06/2008

Page: 64/102

Payload information for HV reports

information on what was the objective of the impact study (e.g., flood

forecasting);

main basin characteristics (size, hydrological regime, …);

description of the meteorological event;

assessment of the benefit of satellite versus no-satellite

judgement whether the result was occasional or structural;

advice on how the results could have been better.

Table 12 Payload information for Hydrovalidation reports


Description Hydrological Validation reports shall include at least header information

listed in Table 13


Header information for HV reports

Date/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 hydrological

model results and the real situation; possibility of replacement of non-functional

parts of standard measurement network by satellite products.

Satellite products used for impact study.

Hydrological model used for the impact study

Table 13 Header information for Hydrovalidation reports


Description Reports produced by Hydrological Validation subsystem shall be archived



Issue: Version 2.1

Date: 20/06/2008

Page: 65/102



Description Archive of Hydrological Validation reports shall be accessible through

standard FTP and HTTP browsers



Description Hydrological Validation reports shall be automatically distributed to the

product generation chains



Description Hydrological Validation reports shall be generated in the formats listed in

Table 14


Output data format for HV reports

Microsoft Word documents (.doc)

Microsoft Excel documents (.xls)

Portable Document Format (.pdf)

Table 14 Output data formats for Hydrovalidation reports

3.1.7 Archival Requirements

SR-44010-FUN-ARC Level Component OM

Description Central archival shall be guaranteed in an online/offline archive




Issue: Version 2.1

Date: 20/06/2008

Page: 66/102


Description Archive shall maintain logging of archival-relevant data



Description Duration of archival-relevant data logging shall be not less than one

month



Description H-SAF central archive shall be set up



Description H-SAF central archive shall ingest all products outputs from Snow

Parameter chain, Precipitation chain and Soil Moisture chain



Description Hydro Validation reports shall be collected in H-SAF central archive



Description Performance reports of online-offline dissemination to users shall be

collected in H-SAF central archive




Issue: Version 2.1

Date: 20/06/2008

Page: 67/102


Description Analysis of reports from the addressed users shall be performed, to

assess compliance with system performance requirements such as

timeliness and reliability



Description Content of performance report regarding time of reception, format check,

message soundness shall be automatically detected



Description Data transfer from online to offline archive shall be automated



Description System shall be able to restore offline data to online archive


3.1.8 Dissemination Requirements

SR-54010-FUN-DIS Level Component OM

Description System shall be able to receive orders from users through UMARF



Description System shall be able to process orders from users by disseminating

products through UMARF



Issue: Version 2.1

Date: 20/06/2008

Page: 68/102



Description System shall provide a catalogue to UMARF



Description Validation of orders received through UMARF shall be performed



Description Orders acceptance/rejection shall be notified to UMARF



Description Updated information about orders progress status shall be guaranteed to

UMARF


SR-54070-FUN-DIS Level Component PR,SM,SP

Description System shall disseminate products to meteorological services through

WMO-GTS


SR-54080-FUN-DIS Level Component PR, SM, SP

Description GTS disseminated products shall respond to WMO standard encoding




Issue: Version 2.1

Date: 20/06/2008

Page: 69/102

SR-54091-FUN-DIS Level Component PR, SM, SP, OM

Description Products shall be disseminated to Hydro Validation Subsystem using

formats listed in Table 15

Comment JPEG or similar used for a quick look Verification T

Products file format

GRIB ver. 1

BUFR ver. 3

HDF-5

ASCII

JPEG or similar

Table 15 Formats for data dissemination to Hydro Validation Subsystem


Description System shall archive records of disseminated products



Description Connection to U-MARF shall be established via a client installed locally


SR-54150-FUN-DIS Level Component PR, SM, SP, OM

Description Communication links via EUMETCast shall guarantee dissemination time

compatible with time limits as addressed in Table 16

Comment Timeliness for dissemination to NRT

users is defined as acquisition time +

generation time + dissemination time

Verification T



Issue: Version 2.1

Date: 20/06/2008

Page: 70/102


Description System shall disseminate products to operational users other than

meteorological services through EUMETCast


SR-54170-FUN-DIS Level Component PR, SM, SP

Description H-SAF products shall be disseminated to H-SAF central archive in real

time



Description Hydro Validation Reports shall be retro-fitted from the central archive to

the generation chains


3.2 Reliability, Availability and Maintenance Requirements

SR-70010-RAM-GEN Level O Component ALL

Description Software should be under configuration control, following what is defined

in Configuration Management Plan


SR-70020-RAM-GEN Level Component ALL

Description Logging messages shall permit identification of the event-related items





Issue: Version 2.1

Date: 20/06/2008

Page: 71/102

Description Freely available or cots software packages shall be used only with written

support guarantee by the developer during the whole programme lifetime



Description Freely available or cots software packages should be encapsulated in a

modular access interface



Description Systems availability shall be of 99%



Description System failure should be fail-silent



Description System functions shall be available 24 hours a day 7 days a week


3.3 Operational Requirements

SR-80010-OPE-GEN Level Component ALL

Description Backup of operational software configuration items shall be performed,

with regular frequency, following indications reported in the Configuration

Management Plan




Issue: Version 2.1

Date: 20/06/2008

Page: 72/102

SR-80020-OPE-GEN Level O Component ALL

Description System should need human specific operations only in offline operations

(such as backing-up operations or offline archiving), system configuration,

and mainteinance


SR-80040-OPE-GEN Level Component ALL

Description Human-Machine-Interface shall provide user authentication functions


SR-80050-OPE-GEN Level Component

Description The system shall be able to manage missing real time production

(because of missed acquisitions, corrupted input data, unavailability of the

online products generation facilities and/or of the dissemination means)

using a specific recovery plan

Comment A recovery plan should be foreseen only

for the reconstructing time series. If the

recovery is impossible or not sufficiently

cost effective (the Project Team to

decide) the gap shall be accepted as it

is

Verification R

3.4 Performance Requirements

SR-91000-PER-GEN Level O Component ALL

Description During operational phase 95% of products reported in Table 2 with

envisaged quality level, should be guaranteed in case of availability of

related input data




Issue: Version 2.1

Date: 20/06/2008

Page: 73/102

SR-91020-FUN-PRG Level Component ALL

Description Product processing shall be completed (from the end of reception) in

accordance to production timeliness described in Table 16

Comment Timeliness for dissemination to NRT

users is defined as acquisition time +

generation time + dissemination time

Verification T

Subsystem Product Product description Timelimess

Precipitation

PR-OBS-1

Precipitation rate at ground by

MW conical scanners (with

indication of phase)

Demonstrational status, First release:

within 90 min from the end of

acquisition

Operational status. Final release: within

15 min from the end of reception if

within the acquisition range of Rome;

otherwise 90 min

PR-OBS-2


MW cross-track scanners (with

indication of phase)

15 min from the end of reception if

within the acquisition range of Rome;

otherwise 30 min

PR-OBS-3 Precipitation rate at ground by

GEO/IR supported by LEO/MW

Within 5 min from the end of (real time)

acquisition

PR-OBS-4


LEO/MW supported by GEO/IR

(with flag for phase)

20 min after acquisition of a new MW

image (5 min after availability of new

MW retrievals requiring 15 miin

process)

PR-OBS-5 Accumulated precipitation at

ground by MW+IR and MW only

At fixed times of the day, within 15 min

after synoptic hours (00, 03, 06, 09, 12,

15, 18 and 21 UTC)

PR-ASS-1

Instantaneous and accumulated

precipitation at the ground

computed by a NWP model

At fixed times of the day, 4 h after

nominal time of analysis (00, 06, 12, 18

and, in Operational status and final

release, 03, 09, 15, 21 UTC)

Soil

Moisture SM-OBS-1

Global surface soil moisture by

radar scatterometer

130 min (potentially 30 min using the

EARS service)



Issue: Version 2.1

Date: 20/06/2008

Page: 74/102

SM-OBS-2 Regional surface soil moisture by

radar scatterometer

135 min (potentially 35 min using the

EARS service)

SM-ASS-1

Volumetric soil moisture (roots

region) by scatterometer

assimilation in NWP model

36 h (due to the need to assimilate data

observed in the 6-30 hours preceding

start of the operational run)

Snow

Parameters

SN-OBS-1 Snow detection (snow mask) by

VIS/IR radiometry

Fixed time of the day, product updated

to account for data available until 1 h

before delivery

SN-OBS-2 Snow status (dry/wet) by MW

radiometry



before delivery

SN-OBS-3 Effective snow cover by VIS/IR

radiometry



before delivery

SN-OBS-4 Snow water equivalent by MW

radiometry



before delivery

Table 16 Time limits in products generation/dissemination

3.5 Portability Requirements

H-SAF does not fit compulsory portability requirements, for the reason that (as stated even

at proposal stage) each of the production centres will use as far as possible its own

SW/HW environment.

Anyway, the compliance with standards acts as a desirable requirement in order to

accomplish to both credibility and updating capabilities; standard criteria shall be issued by

engineering task (see Project Plan [AD 2]), to be applied, when the case, to all participants

in charge of products generation.

SR-92010-POR-GEN Level O Component ALL

Description System software should be platform independent (by using open standard

environment and/or tools)



Issue: Version 2.1

Date: 20/06/2008

Page: 75/102

Comment Compliance with standards act as a

desired requirement in order to

accomplish to both credibility and

updating capabilities; standard criteria

shall be issued by engineering task, to

be applied when the case to all

participants in charge of products

generation.

Verification D


Description Software should run in unix compliant environment








generation.

Verification I


Description Software of product generation chains should be written in programming

languages such those described in Table 17








generation

Verification I



Issue: Version 2.1

Date: 20/06/2008

Page: 76/102

SW Language

ISO/IEC 9899 C

ISO/IEC 14882 C++

Fortran 90/95

Bourne/Korn/C-shell scripts

ISO/IEC std script languages (PERL, PYTHON; PHP)

IDL / PV-WAVE

java

Table 17 Software coding languages


Description Language coding of Table 17 should respect latest ECSS guidelines [RD

15], [RD 16], [RD 17], [RD 18]








generation

Verification R

3.6 Resources Requirements

SR-93010-RES-GEN Level Component ALL

Description Online disc capacity shall be sufficient to maintain the sum of input,

intermediate and output data at least for 7 operational days





Issue: Version 2.1

Date: 20/06/2008

Page: 77/102

Description System’s hardware resources of physical memory shall be sufficient to

handle data processing



Description Network communication bandwidth shall guarantee data transfer without

impact on production time limits described in Table 16


SR-93070-RES-GEN Level Component OM

Description A H-SAF web site shall be set up and maintained

Comment The web site shall provide general

public information on H-SAF

Verification T

SR-93080-RES-GEN Level Component OM

Description A H-SAF help desk shall be set up and mantained


3.7 Safety Requirements

SR-94010-SAF-GEN Level Component ALL

Description Situations which could bring the system to a degraded operational mode

shall cause a system warning message



Description Situations which should require an operator action shall cause a system

alarm



Issue: Version 2.1

Date: 20/06/2008

Page: 78/102



Description Error occurring during application execution shall not lead to uncontrolled

application abort/termination



Description Every software item shall return its termination status


3.8 Security Requirements

SR-95010-SEC-GEN Level Component ALL

Description Software design shall prevent accidental data modifications

Comment Verification R


Description Software design shall prevent unauthorized data modifications



Description Software design shall prevent propagation of software damages




Issue: Version 2.1

Date: 20/06/2008

Page: 79/102

3.9 Documentation Requirements

SR-96010-DOC-GEN Level Component ALL

Description Documentation shall be available for each configuration item


4 TBDs/TBCs list

No TBD/TBC items are pending.

5 Requirements traceability

5.1 System Requirements traceability to H-SAF Subsystems

The following table summarises the mapping of the requirements to H-SAF subsystems

Subsystem System Requirement Identifier

All H-SAF Subsystems SR-00030-FUN-GEN

SR-00040-FUN-GEN

SR-00050-FUN-GEN

SR-00060-FUN-GEN

SR-10010-FUN-ACQ

SR-10020-FUN-ACQ

SR-10030-FUN-ACQ

SR-10090-FUN-ACQ

SR-10100-FUN-ACQ

SR-10110-FUN-ACQ

SR-10120-FUN-ACQ

SR-20010-FUN-PPR

SR-70010-RAM-GEN

SR-70020-RAM-GEN

SR-70030-RAM-GEN

SR-70040-RAM-GEN

SR-70050-RAM-GEN

SR-70060-RAM-GEN



Issue: Version 2.1

Date: 20/06/2008

Page: 80/102


SR-70070-OPE-GEN

SR-80010-OPE-GEN

SR-80020-OPE-GEN

SR-80040-OPE-GEN

SR-80050-OPE-GEN

SR-91000-PER-GEN

SR-91020-PER-GEN

SR-92010-POR-GEN

SR-92020-POR-GEN

SR-92030-POR-GEN

SR-92040-POR-GEN

SR-93010-RES-GEN

SR-93050-RES-GEN

SR-93060-RES-GEN

SR-94010-SAF-GEN

SR-94020-SAF-GEN

SR-94030-SAF-GEN

SR-94040-SAF-GEN

SR-95010-SEC-GEN

SR-95020-SEC-GEN

SR-95030-SEC-GEN

SR-96010-DOC-GEN

Precipitation Subsystem SR-00010-FUN-GEN

SR-00020-FUN-GEN

SR-00070-FUN-GEN

SR-10130-FUN-ACQ

SR-12010-FUN-ACQ

SR-12011-FUN-ACQ

SR-12020-FUN-ACQ

SR-12021-FUN-ACQ

SR-12030-FUN-ACQ

SR-12031-FUN-ACQ

SR-12040-FUN-ACQ

SR-12041-FUN-ACQ

SR-12050-FUN-ACQ

SR-12051-FUN-ACQ



Issue: Version 2.1

Date: 20/06/2008

Page: 81/102


SR-12060-FUN-ACQ

SR-12061-FUN-ACQ

SR-12070-FUN-ACQ

SR-12071-FUN-ACQ

SR-12080-FUN-ACQ

SR-12081-FUN-ACQ

SR-12100-FUN-ACQ

SR-12110-FUN-ACQ

SR-12111-FUN-ACQ

SR-12120-FUN-ACQ

SR-12130-FUN-ACQ

SR-12140-FUN-ACQ

SR-12150-FUN-ACQ

SR-12160-FUN-ACQ

SR-12220-FUN-ACQ

SR-12240-FUN-ACQ

SR-12250-FUN-ACQ

SR-12260-FUN-ACQ

SR-12270-FUN-ACQ

SR-12280-FUN-ACQ

SR-12300-FUN-ACQ

SR-20020-FUN-PPR

SR-30010-FUN-PRG

SR-30020-FUN-PRG

SR-30030-FUN-PRG

SR-30040-FUN-PRG

SR-32010-FUN-PRG

SR-32020-FUN-PRG

SR-32030-FUN-PRG

SR-32040-FUN-PRG

SR-32011-FUN-PRG

SR-32021-FUN-PRG

SR-32031-FUN-PRG

SR-32041-FUN-PRG

SR-32060-FUN-PRG



Issue: Version 2.1

Date: 20/06/2008

Page: 82/102


SR-32061-FUN-PRG

SR-32062-FUN-PRG

SR-32063-FUN-PRG

SR-32070-FUN-PRG

SR-32080-FUN-PRG

SR-32090-FUN-PRG

SR-32230-FUN-PRG

SR-32240-FUN-PRG

SR-54070-FUN-DIS

SR-54080-FUN-DIS

SR-54091-FUN-DIS

SR-54150-FUN-DIS

SR-54170-FUN-DIS

Soil Moisture subsystem SR-00010-FUN-GEN

SR-00020-FUN-GEN

SR-00070-FUN-GEN

SR-10130-FUN-ACQ

SR-11010-FUN-ACQ

SR-11030-FUN-ACQ

SR-11040-FUN-ACQ

SR-20020-FUN-PPR

SR-30010-FUN-PRG

SR-30020-FUN-PRG

SR-30030-FUN-PRG

SR-30040-FUN-PRG

SR-31010-FUN-PRG

SR-31020-FUN-PRG

SR-31030-FUN-PRG

SR-31040-FUN-PRG

SR-31060-FUN-PRG

SR-31061-FUN-PRG

SR-31070-FUN-PRG

SR-31080-FUN-PRG

SR-31090-FUN-PRG

SR-31100-FUN-PRG

SR-31150-FUN-PRG



Issue: Version 2.1

Date: 20/06/2008

Page: 83/102


SR-31270-FUN-PRG

SR-54070-FUN-DIS

SR-54080-FUN-DIS

SR-54091-FUN-DIS

SR-54150-FUN-DIS

SR-54170-FUN-DIS

Snow Parameter subsystem SR-00010-FUN-GEN

SR-00020-FUN-GEN

SR-00070-FUN-GEN

SR-10130-FUN-ACQ

SR-13010-FUN-ACQ

SR-13015-FUN-ACQ

SR-13020-FUN-ACQ

SR-13025-FUN-ACQ

SR-13030-FUN-ACQ

SR-13040-FUN-ACQ

SR-13050-FUN-ACQ

SR-13060-FUN-ACQ

SR-13070-FUN-ACQ

SR-13080-FUN-ACQ

SR-13090-FUN-ACQ

SR-13100-FUN-ACQ

SR-20020-FUN-PPR

SR-30010-FUN-PRG

SR-30020-FUN-PRG

SR-30030-FUN-PRG

SR-30040-FUN-PRG

SR-33040-FUN-PRG

SR-33050-FUN-PRG

SR-33051-FUN-PRG

SR-33060-FUN-PRG

SR-33065-FUN-PRG

SR-33070-FUN-PRG

SR-33080-FUN-PRG

SR-33090-FUN-PRG

SR-33100-FUN-PRG



Issue: Version 2.1

Date: 20/06/2008

Page: 84/102


SR-33110-FUN-PRG

SR-33120-FUN-PRG

SR-33125-FUN-PRG

SR-33130-FUN-PRG

SR-33140-FUN-PRG

SR-33150-FUN-PRG

SR-33160-FUN-PRG

SR-33170-FUN-PRG

SR-33200-FUN-PRG

SR-33210-FUN-PRG

SR-33220-FUN-PRG

SR-33230-FUN-PRG

SR-33240-FUN-PRG

SR-33250-FUN-PRG

SR-33260-FUN-PRG

SR-33270-FUN-PRG

SR-33280-FUN-PRG

SR-33290-FUN-PRG

SR-33300-FUN-PRG

SR-33310-FUN-PRG

SR-33330-FUN-PRG

SR-33340-FUN-PRG

SR-33320-FUN-PRG

SR-54070-FUN-DIS

SR-54080-FUN-DIS

SR-54091-FUN-DIS

SR-54150-FUN-DIS

SR-54170-FUN-DIS

Hydro Validation subsystem SR-00021-FUN-GEN

SR-14010-FUN-ACQ

SR-14020-FUN-ACQ

SR-14030-FUN-ACQ

SR-14040-FUN-ACQ

SR-34010-FUN-VPR

SR-34020-FUN-VPR

SR-34030-FUN-VPR



Issue: Version 2.1

Date: 20/06/2008

Page: 85/102


SR-34040-FUN-VPR

SR-34050-FUN-VPR

SR-34060-FUN-VPR

SR-34110-FUN-REP

SR-34120-FUN-REP

SR-34130-FUN-REP

SR-34140-FUN-REP

SR-34150-FUN-REP

SR-34160-FUN-REP

SR-34170-FUN-REP

SR-34180-FUN-REP

Offline Monitoring Subsystem SR-44010-FUN-ARC

SR-44020-FUN-ARC

SR-44021-FUN-ARC

SR-44030-FUN-ARC

SR-44040-FUN-ARC

SR-44041-FUN-ARC

SR-44050-FUN-ARC

SR-44060-FUN-ARC

SR-44070-FUN-ARC

SR-44080-FUN-ARC

SR-44090-FUN-ARC

SR-54010-FUN-DIS

SR-54020-FUN-DIS

SR-54030-FUN-DIS

SR-54040-FUN-DIS

SR-54050-FUN-DIS

SR-54060-FUN-DIS

SR-54091-FUN-DIS

SR-54120-FUN-DIS

SR-54130-FUN-DIS

SR-54150-FUN-DIS

SR-54160-FUN-DIS

SR-52180-FUN-DIS

Table 18 System Requirements traceability vs H-SAF subsystems



Issue: Version 2.1

Date: 20/06/2008

Page: 86/102

5.2 System Requirements traceability to User Requirements

This paragraph shows System Requirements traceability versus User Requirements,

through a proper table. It is assumed that not all of the user requirements have been

carried 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 system

requirements;

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 system

requirements;

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 system

requirements.

System Requirement Identifier User Requirement Identifier

SR-00010-FUN-GEN UR-GE-01


UR-GE-04


UR-GE-04

SR-00030-FUN-GEN N.A. to User Requirement





UR-PR-01

UR-PR-02

UR-PR-03

UR-PR-04

UR-SM-01



Issue: Version 2.1

Date: 20/06/2008

Page: 87/102


UR-SN-01

UR-SN-02

UR-SN-04

SR-10010-FUN-ACQ UR-GE-02

UR-GE-13

UR-PR-01

UR-PR-02

UR-PR-03

UR-PR-04

UR-SM-01

UR-SM-03

UR-SM-05

UR-SM-06

UR-SM-07

UR-SN-01

UR-SN-02

SR-10020-FUN-ACQ N.A. to User Requirement


UR-GE-02


UR-GE-02


UR-GE-02


UR-GE-02

UR-GE-03

UR-GE-14


SR-10130-FUN-ACQ UR-PR-05



Issue: Version 2.1

Date: 20/06/2008

Page: 88/102


UR-SN-04

UR-SN-10

UR-SN-11

SR-11010-FUN-ACQ UR-SM-01

UR-SM-02



UR-SM-05










UR-GE-02

UR-SN-01

UR-SN-02

UR-SN-04


UR-GE-02

UR-SN-01

UR-SN-02

UR-SN-04






Issue: Version 2.1

Date: 20/06/2008

Page: 89/102














UR-PR-07

UR-GE-14


UR-PR-03

UR-PR-05


UR-PR-05


UR-PR-05


UR-PR-05


UR-PR-05


UR-PR-07

SR-13010-FUN-ACQ UR-SN-01

UR-SN-02



Issue: Version 2.1

Date: 20/06/2008

Page: 90/102



UR-SN-02


UR-SN-02


UR-SN-02


UR-SN-04


UR-SN-01

UR-SN-02

UR-SN-04



UR-SN-02


UR-SN-04


UR-SN-02


UR-SN-02


UR-SN-02


UR-GE-03


UR-GE-03


UR-GE-03



Issue: Version 2.1

Date: 20/06/2008

Page: 91/102


UR-GE-07


UR-GE-03

UR-GE-07

SR-20010-FUN-PPR UR-GE-01

UR-GE-02

UR-GE-03

SR-20020-FUN-PPR UR-GE-06

UR-SM-01

UR-SM-02

SR-30010-FUN-PRG UR-GE-06


UR-GE-06

UR-GE-07

UR-PR-01

UR-PR-02

UR-PR-03

SR-30030-FUN-PRG UR-PR-11

UR-SM-04

UR-SN-05


UR-SM-04

UR-SN-05


UR-SM-05


UR-SM-05


UR-SM-05



Issue: Version 2.1

Date: 20/06/2008

Page: 92/102



UR-SM-05


UR-SM-05


UR-SM-05


UR-SM-06

UR-SM-07


UR-SM-01

UR-SM-02

UR-SM-06

UR-SM-07


UR-SM-06

UR-SM-07


UR-SM-06

UR-SM-07

SR-31150-FUN-PRG UR-SM-01

UR-SM-02

UR-SM-06

UR-SM-07

SR-31270-FUN-PRG UR-SM-04

UR-SM-08


UR-PR-01

UR-PR-02



Issue: Version 2.1

Date: 20/06/2008

Page: 93/102


UR-PR-03

UR-PR-06


UR-PR-01

UR-PR-02

UR-PR-03

UR-PR-07


UR-PR-01

UR-PR-02

UR-PR-03

UR-PR-06


UR-PR-01

UR-PR-02

UR-PR-03

UR-PR-07


UR-PR-01

UR-PR-02

UR-PR-03

UR-PR-06


UR-PR-01

UR-PR-02

UR-PR-03

UR-PR-07


UR-PR-01



Issue: Version 2.1

Date: 20/06/2008

Page: 94/102


UR-PR-02

UR-PR-03

UR-PR-06


UR-PR-01

UR-PR-02

UR-PR-03

UR-PR-07


UR-PR-01

UR-PR-02

UR-PR-03

UR-PR-06

UR-GE-01

UR-PR-08


UR-PR-01

UR-PR-02

UR-PR-03

UR-PR-07

UR-GE-01

UR-PR-09


UR-PR-10

UR-PR-09

UR-PR-10






Issue: Version 2.1

Date: 20/06/2008

Page: 95/102


UR-PR-10


UR-PR-10


UR-PR-10


UR-PR-12


UR-GE-02

UR-SN-06


UR-GE-02

UR-SN-08


UR-GE-02

UR-SN-08


UR-GE-02

UR-SN-10


UR-GE-02

UR-SN-16


UR-SN-06


UR-SN-08

SR-33090-FUN-PRG UR-SN-15


UR-SN-16



Issue: Version 2.1

Date: 20/06/2008

Page: 96/102



UR-SN-13


UR-SN-14



UR-SN-16


UR-SN-03

UR-SN-13


UR-SN-03

UR-SN-14


UR-SN-03

UR-SN-15



UR-GE-02

UR-SN-13


UR-GE-02

UR-SN-15


UR-GE-02

UR-SN-16


UR-SN-13




Issue: Version 2.1

Date: 20/06/2008

Page: 97/102


UR-SN-15


UR-SN-16


UR-SN-13


UR-SN-15


UR-SN-16


UR-SN-03

UR-SN-13


UR-SN-03

UR-SN-15


UR-SN-03

UR-SN-16




SR-34010-FUN-VPR UR-HY-04






SR-34110-FUN-REP UR-RD-04

UR-RD-05



Issue: Version 2.1

Date: 20/06/2008

Page: 98/102


UR-RD-06


UR-RD-05

UR-RD-06


UR-RD-05

UR-RD-06


UR-RD-05

UR-RD-06

SR-34150-FUN- REP UR-RD-04

UR-RD-05

UR-RD-06

SR-34160-FUN- REP UR-RD-04

UR-RD-05

UR-RD-06


UR-RD-05

UR-RD-06


UR-RD-05

UR-RD-06

SR-44010-FUN-ARC UR-GE-03

UR-GE-06


UR-GE-06


UR-GE-06




Issue: Version 2.1

Date: 20/06/2008

Page: 99/102


UR-GE-06


UR-GE-06






SR-54010-FUN-DIS UR-GE-03

UR-GE-06


UR-GE-06


UR-GE-06


UR-GE-06


UR-GE-03

UR-GE-07


UR-GE-06

UR-GE-07


UR-GE-07


UR-GE-07



UR-GE-06



Issue: Version 2.1

Date: 20/06/2008

Page: 100/102



UR-GE-06


UR-GE-06


UR-GE-06


UR-GE-06


UR-GE-06

SR-70010-RAM-GEN N.A. to User Requirement







SR-80010-OPE-GEN N.A. to User Requirement



SR-80050-OPE-GEN UR-GE-14

SR-91000-PER-GEN UR-GE-02

UR-GE-03

UR-GE-06

SR-91020-FUN-PRG N.A. to User Requirement

SR-92010-POR-GEN N.A. to User Requirement






Issue: Version 2.1

Date: 20/06/2008

Page: 101/102


SR-93010-RES-GEN N.A. to User Requirement

SR-93050-RES-GEN N.A. to User Requirement

SR-93060-RES-GEN UR-GE-03



SR-94010-SAF-GEN N.A. to User Requirement




SR-95010-SEC-GEN N.A. to User Requirement



SR-96010-DOC-GEN N.A. to User Requirement

Table 19 System Requirements traceability vs User Requirements



Issue: Version 2.1

Date: 20/06/2008

Page: 102/102

- END OF THE DOCUMENT-