System Requirement Document (SRD) - H-SAF

More documents

Recommendations

Info

H-SAFLIST OF TABLESSystem Requirement DocumentDoc. No: SAF/HSAF/SRD/2.1Issue: Version 2.1Date: 20/06/2008Page: 10/102Table 1 Outlines of H-SAF Consortium ............................................................................. 21Table 2 Satellite-derived H-SAF products and satellite data sources ................................ 23Table 3 Backup products generated by a NWP model ...................................................... 23Table 4 H-SAF External Interfaces for Data Acquisition .................................................... 29Table 5 Classes of messages ............................................................................................ 33Table 6 H-SAF Data sources ............................................................................................. 36Table 7 Information related to satellite data ....................................................................... 38Table 8 Elements for soil moisture consistency control ..................................................... 55Table 9 Formats for Hydrovalidation processing ............................................................... 61Table 10 Timings for Hydrovalidation processing .............................................................. 62Table 11 Input data and parameters used by selected operational hydrological models ... 63Table 12 Payload information for Hydrovalidation reports ................................................. 64Table 13 Header information for Hydrovalidation reports .................................................. 64Table 14 Output data formats for Hydrovalidation reports ................................................. 65Table 15 Formats for data dissemination to Hydro Validation Subsystem ......................... 69Table 16 Time limits in products generation/dissemination ............................................... 74Table 17 Software coding languages ................................................................................ 76Table 18 System Requirements traceability vs H-SAF subsystems .................................. 85Table 19 System Requirements traceability vs User Requirements ................................ 101LIST OF FIGURESFigure 1: H-SAF system decomposition ............................................................................ 25
H-SAFSystem Requirement DocumentDoc. No: SAF/HSAF/SRD/2.1Issue: Version 2.1Date: 20/06/2008Page: 11/1021 Introduction1.1 Purpose of the DocumentThis document specifies the system requirements for the Hydrology SAF (H-SAF). Itfocuses mainly on product generation features, as the main objective of H-SAF system isto provide new satellite derived products in order to satisfy the needs of operationalhydrology. It identifies the requirements regarding products, functions, components andinterfaces as they have been described in the Project Plan [AD 2] and in the UserRequirement Document [AD 4]. It is the input for the architectural specification of thesystem, describedI in the System Design Document.In accordance with the project phasing depicted in the Project Plan, the SystemRequirements Document (SRD) has to be released in a preliminary version at theRequirement Review and in baseline version at the Preliminary Design Review.An updating of SRD (current document) has been made necessary as consequence ofURD and PP modifications. So this document should be considered as the new SRDbaseline version.1.2 Document OverviewThe H-SAF System Requirement Document is structured as follows:Chapter 1: Introduces the purpose of the document, provide the references and a list ofacronymsChapter 2: Gives a general description of H-SAF system in terms of purpose, outlines ofconsortium, products to be generated, system overview and general constraints.Chapter 3: Defines the system requirements classified in categories.Chapter 4: summarizes the TBDs and TBCs items, providing the responsible of each itemand a planned date for resolution.Chapter 5: Presents the traceability of the System Requirements versus the UserRequirements and the subsystems identified in the system design.The design methods here used are the UML 2.0 [RD 19], [RD 20], [RD 21], [RD 22]; alldiagrams and engineering notations intend to be compliant with standard there depicted.H-SAF System Engineering is compliant to the latest ECSS standards [RD 15], [RD 16],[RD 17], [RD 18] tailored to the H-SAF peculiarity.Most of ECSS standard founding principles have been adopted into H-SAF Engineering,such as the tailoring concept and the strict relationship between Software Engineering andSystem Engineering.
Page 1: H-SAFSystem Requirement DocumentDoc
Page 4 and 5: H-SAFSystem Requirement DocumentDoc
Page 26 and 27: H -SAFSystem Requirement DocumentDo
Page 60 and 61:
H -SAFSystem Requirement DocumentDo
Page 62 and 63:
Page 64 and 65:
Page 66 and 67:
Page 68 and 69:
Page 70 and 71:
Page 72 and 73:
Page 74 and 75:
Page 76 and 77:
Page 78 and 79:
Page 80 and 81:
Page 82 and 83:
Page 84 and 85:
Page 86 and 87:
Page 88 and 89:
Page 90 and 91:
Page 92 and 93:
Page 94 and 95:
Page 96 and 97:
Page 98 and 99:
Page 100 and 101:
Page 102:
show all

System Requirement Document (SRD) - H-SAF

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

Delete template?

Save as template?