1. HMA Follow On Task 4 - Order Preliminary Review 2-3 February 2010
Daniele Marchionni Elsag Datamat
Stefania Pappagallo Elsag Datamat
2-3 February 2010 – Slide 1

2. Task 4 – Preliminary Review – Agenda
Task 4 Activities Status
HMA Ordering ICD evolution
HMA Ordering ATS
Reference Order Server - OPGW
2-3 February 2010 – Slide 2

3. Task 4 – Activities Status - Deliverables
Deliverables for PR
Ordering Services for Earth Observation Products OGC V0.9.5 Draft 2 28/01/2010
Ordering Services for Earth Observation Products Abstract Test Suite - (ATS) 25/01/2010
Reference Order Server documentation:
OPGW Software Requirements Specification – SRS V1.0 22/01/2010
OPGW Software Design Document – SDD v1.0 22/01/2010
Previous Deliverables
TASK 4 Software Development Plan – SDP - V1.0 30/11/2009
TASK 4 Software Product Assurance Plan – SPAP – V1.0 30/11/2009
2-3 February 2010 – Slide 3

4. Task 4 – Activities Status - SWG
Ordering Services for Earth Observation Products SWG
RFC Submitted on 29/09/2009
OAB answered on 24/11/2009
Work appreciated and few comments raised, implementation on the way
SWG formally activated on 04/12/2009
3 teleconference already had, usual attendees:
Jerome Gasperi, CNES
Michael Schick, EUMETSAT
D. Marchionni, U. Voges, TASK 4 Consortium
2-3 February 2010 – Slide 4

5. Task 4 – Activities Status - SWG
A number of issues have been raised ( iew&project_id=325&tab=5):
21 issues closed with V0.9.5 draft 1
4 issues closed with V0.9.5 draft 2
10 issues currently open
2-3 February 2010 – Slide 5

6. Task 4 – Activities Status - SWG
Next activities:
To close the comments raised from OAB
To comply with OGC r3
To close pending issues
To produce a final V0.9.5 for SWG for voting for the 30 days public comment period by 05/03/2010
To produce final version by 08/2010
2-3 February 2010 – Slide 6

7. Ordering ICD (OGC 06-141) Evolution
Summary of Changes:
Enhanced Contents section of Capabilities
Processing options at order level
Delivery options at order level
Enhanced Description and Setting of Scene Selection Options
Extension of the value list for delivery methods and delivery options
Many clarifications on the document
2-3 February 2010 – Slide 7

8. OGC 06-141 Evolution - Enhancement of Contents section
2-3 February 2010 – Slide 8

9. OGC 06-141 Evolution - Enhancement of Contents section
V0.9.5.draft 2
2-3 February 2010 – Slide 9

10. OGC 06-141 Evolution - Processing Options at order level
2-3 February 2010 – Slide 10

11. OGC 06-141 Evolution - Processing Options at order level
V0.9.5 draft 2
2-3 February 2010 – Slide 11

12. OGC 06-141 Evolution - Delivery options at order level
2-3 February 2010 – Slide 12

13. OGC 06-141 Evolution - Delivery options at order level
V0.9.5 draft 2
2-3 February 2010 – Slide 13

14. OGC 06-141 Evolution - Enhancement of Scene Selection options
Scene Selection Options Description V0.9.4
2-3 February 2010 – Slide 14

15. OGC 06-141 Evolution - Enhancement of Scene Selection options
Scene Selection Options Description V0.9.5 draft 2
2-3 February 2010 – Slide 15

16. OGC 06-141 Evolution - Enhancement of Scene Selection options
Scene Selection Options Description V0.9.5 draft 2
2-3 February 2010 – Slide 16

17. OGC 06-141 Evolution - Enhancement of Scene Selection options - Example
2-3 February 2010 – Slide 17

18. OGC 06-141 Evolution - Enhancement of Scene Selection options - Example
2-3 February 2010 – Slide 18

19. OGC 06-141 Evolution - Enhancement of Scene Selection options
Setting Scene Selection Option V0.9.4
2-3 February 2010 – Slide 19

20. OGC 06-141 Evolution - Enhancement of Scene Selection options
Setting Scene Selection Option V0.9.5 draft 2
2-3 February 2010 – Slide 20

21. Already Identified Scene Selection Options
ParameterID
Type
acrossTrackSize
swe:Quantity (Kilometers)
alongTrackSize
columnsExtraction
swe:CountRange
frame
swe:Count
lookAngle
swe:DataRecord/swe:field
name: “lookAngle”
type: swe:Quantity
name: “FOV”
orbit
Swe:Count
rowsExtraction
SAT
sceneBoundingPolygon
gml:Polygon
sceneCentreCoordinates
gml:Point
sceneCoordinates
Gml:Rectangle
sceneStartStopTime
swe:TimeRange
sceneType
swe:Category
track
Sep 2009 – Slide 21

22. Joint usage of SPS and OS:
OGC Issues
Alignment with TASK 2:
Async management: Ordering Services will continue to use only the WS-addressing, no WS-notification
SWE Common: to define a common version to use in both protocols.
Joint usage of SPS and OS:
Solution agreed during TASK 2 presentation:
SPSEO::GetStatus will return all the metadata of future acquisitions
The SPS:ID will encode the service address + the actual feasibility ID
OPGW will call GetStatus for getting the needed information
Sep 2009 – Slide 22

23. Ordering ICD - ATS
Ordering Services for Earth Observation Products Abstract Test Suite (ATS)
con terra GmbH - presentation
2-3 February 2010 – Slide 23

24. Reference Order Server - Overview
A reference order server will be set-up with the following objectives:
Demonstrate the updated specification;
Support the implementation of ordering clients;
Support the implementation of ordering servers.
Since ordering process implies processing, formatting and delivering to the user of the required products, then a fully functional order server would mean a complete ordering handling system for EO products.
The order server that will be provided is a system that will provide to the client an OGC compliant interface, but the ordering functionality is accomplished by calling an actual order handling system (MUIS / M2EOS).
The order server that will be provided is the evolution of Ordering & Programming Gateway – OPGW already implemented in previous HMA-I and HMA-E projects.
Sep 2009 – Slide 24

25. Reference Order Server - Context
2-3 February 2010 – Slide 25

26. Reference Order Server - Context
External Entities:
HMA Client: TEAM Engine, SSE
EOLI XML Catalogue Server (M2EOS – M2CS Catalogue)
Called for getting details about the product to order
EOLI XML Order Server (MMOHS via M2EOS)
The input HMA Order is translated in the corresponding EOLI XML Order for being actually executed
OPGW Operator
Provides the order options configuration, some ESA GS users
Sep 2009 – Slide 26

27. Reference Order Server - Context
External Entities:
External OGC Catalogue
This is the OGC Catalogue storing the EO Product metadata to be queried and ordered from the HMA Client.
This catalogue must be kept synchronized with OPGW in order to make sure that the EO products returned by this catalogue have the same identifiers understood from OPGW.
ESA Order Desk
In order to simulate the on-line cancellation of orders, OPGW will send an to a configured address asking for the cancellation of the specified order.
Sep 2009 – Slide 27

28. Reference Order Server – Level 1 decomposition
2-3 February 2010 – Slide 28

29. Reference Order Server – Level 1 decomposition
OPGW – HMA Skeleton
This is the framework where the other sub-components run. It is in charge of:
listening incoming SOAP requests issued via HTTP protocol;
parse the input SOAP messages;
understanding the correct object to activate;
OPGW – Database
Package including the RDBMS (HSQLDB) and the Java library in charge of providing the functions for querying and storing permanently users and orders.
OPGW – Order Service
It is a set of java classes deployed on the Skeleton that are in charge of managing the operations defined in HMA Ordering ICD so it shall be able to manage the following operations: GetCapabilities, GetOptions, GetQuotation, Submit, GetStatus, Cancel, DescribeResultAccess.
2-3 February 2010 – Slide 29

30. Reference Order Server – Level 1 decomposition
OPGW – Support Tools
Tool for loading ESA GS users in the OPGW database;
Tool for converting the order options of ServiceDirectory.xml;
SOAP client tool for testing the system;
Asynchronous notification: it includes Java stand alone applications for sending the notifications of asynchronous operations.
OPGW - Security Layer
This is a set of java classes in charge of performing encryption, decryption, digital signature preparation and verification.
2-3 February 2010 – Slide 30

31. OPGW SW & HW Environment
Hardware resources:
CPU: at least INTEL P4 2.4 GHz or equivalent;
RAM: at least 512 MB
Al least 300 MB of free disk space;
Graphic Adapter: no specific needs.
Software resources:
Operating System: Linux RedHat ES 5 Update 2 (supported also Windows XP OS).
Tomcat
Ant 1.6.5
Java ;
XML Beans 2.2.0
HSQLDB
Sep 2009 – Slide 31

32. Reference Order Server - Documentation
PR Documents:
OPGW Software Requirements Specification – SRS V1.0 (Order Server Requirements Baseline)
OPGW Software Design Document – SDD V1.0 (Order Server Architectural Design)
2-3 February 2010 – Slide 32

33. OPGW SRS – Requirements Approach
OPGW Software Requirements Specification Document has been prepared following the ECSS Space engineering ECSS-E-ST-40C DRD.
Logical Model Description: It presents a technical specification of system, independent of the implementation, describing the functional behaviour of the software product and decomposes it in sub- components.
Requirements have been derived from OPGW SRS prepared in the frame of HMA-E Project, tailoring with respect to HMA FO needs:
Updated Ordering ICD
Removed Programming Service
2-3 February Slide 33

34. OPGW SRS – Requirements Approach
Mapping of HMA ICD wrt EOLI XML ICD: The Ordering ICD is implemented by the Reference Order Server that translates the incoming requests in EOLI XML Ordering ICD compliant requests. The mapping specifies how the two ICDs has been accomplished defining the ‘protocol translation’.
Each requirement is provided with:
Identifier
Description
Source (applicable or reference document the requirements is derived from)
Verification Method: describes the method to be used for verifying the requirement compliance: Analysis, Inspection, Test, …
For the requirement specification the following terms are used:
SHALL – mandatory requirement.
SHOULD – Requirements containing ‘should’ are considered strongly recommended, i.e. an explicit justification is required if they are not met.
IT IS DESIRABLE - Requirements containing ‘it is desirable’ should be considered in the current release but are not formal requirements.
2-3 February Slide 34

35. OPGW SRS – Requirements Statistics
Category
Number of Req.
Functional Requirements 10
Performance Requirements 2
Interface Requirements 12
Operational Requirements 3
Resources Requirements 4
Design and Implementation Requirements
Security and Privacy Requirements 1
Portability Requirements
2-3 February 2010 – Slide 35

36. OPGW SRS – Requirements Statistics
Category
Number of Req
Software Quality Requirements 2
Software Reliability Requirements
Maintainability Requirements -
Software Safety Requirements
Software Configuration and Delivery Requirements
Data Definition and Database Requirements 1
Human Factors Related requirements
Adaptation and Installation requirements
2-3 February Slide 36

37. OPGW SRS – Validation Approach
The system tests will verify the correct functioning and validate the requirements using an end-to-end approach running test procedures prepared in order to cover all meaningful operational scenarios.
Already Identified Test Designs:
TD1: Installation & Configuration: to verify the correctness of the delivery kit and documentation
TD2: Ordering Service Validation: to verify the correct functioning of the HMA Ordering ICD
Validation Requirements
Category
N.Req.
Validation Requirements 6
2-3 February Slide 37

38. OPGW SDD - Overview
The OPGW Software Design Document (SDD) has been prepared following the ECSS Space engineering ECSS-E-ST-40C DRD.
Describes:
Software static & dynamic architecture: it defines the components and the behaviour of OPGW
Interfaces Context: It defines input and output interfaces between Order Server (OPGW) and external entities.
Software Components Design: it provides the formal definition of each sub-component describing function, processing, subordinates, etc.
Internal Interfaces Design: it lists the envisaged internal interfaces
Traceability – Requirements to Components Design
2-3 February 2010 – Slide 38