1. HMA Follow On Task 4 - Order Final Presentation 21 June 2011
Daniele Marchionni TELESPAZIO
June 2011 – Slide 1

2. Task 4 – Final Presentation – Agenda
Task 4 objectives:
Promotion of Ordering ICD as OGC Standard (currently under voting for final adoption);
Implementation of a Reference Server;
Implementation of Executable Test Suite.
June 2011 – Slide 2

3. TASK 4 Deliverables: Task 4 – Deliverables
TASK 4 Software Development Plan – SDP - V1.0 30/11/2009
Configuration Item Data List (CIDL): DIL in the SDP document
TASK 4 Software Product Assurance Plan – SPAP – V1.0 30/11/2009
Non Conformance Reports (NCRs): none
OPGW Software Requirements Specification :
OPGW SRS V1.2 28/01/2011
OPGW Software Installation Document:
OPGW SID V1.1 07/02/2011
June 2011 – Slide 3

4. OPGW Software Design Document: HMA Ordering ICD (including ATS):
Task 4 – Deliverables
OPGW Software Design Document:
OPGW SDD V1.2 28/01/2011
HMA Ordering ICD (including ATS):
Ordering Services for Earth Observation Products OGC r6 V /04/2011
OPGW Software Validation Testing Specification:
OPGW SVS V1.1 28/01/2011
OPGW Acceptance Test Reports:
OPGW ATR V1.0 28/01/2011
Ordering Services for Earth Observation Products - Executable Test Suite (ETS) – (Technical Note)
June 2011 – Slide 4

5. Task 4 – Deliverables
Ordering Services for Earth Observation Products - Executable Test Suite (ETS) – (CTL Scripts)
ETS_V1.0.zip
ETS Execution Report
OPGW SW
OPGW V5.1
June 2011 – Slide 5

6. Created SWG for Ordering ICD (formally activated on 04/12/2009)
Ordering ICD (OGC )
Created SWG for Ordering ICD (formally activated on 04/12/2009)
Chair: Daniele Marchionni
Co-chair: Uwe Voges
10 members, 15 observers
Ordering Service submitted for Public Comments on (24/01/2011 – 23/02/2011)
Comments received and document updated for final adoption vote (voting period 03/05/2011 – 02/07/2011).
Currently 9 Yes and 1 No (John Herring) votes.
June 2011 – Slide 6

7. Ordering ICD Overview:
Ordering ICD (OGC )
Ordering ICD Overview:
Provides operations for:
Submitting order requests for the following type of orders:
Orders for precisely identified EO products
Orders for future EO products, derived from the interaction with an SPS EO compliant server
Subscription to EO Products: to support bulk orders and subscriptions
Discovering of supported collections
Discovering of processing, delivery and scene selection options
Order quotation
SWE Common for modeling order options
June 2011 – Slide 7

8. Ordering ICD Overview:
Ordering ICD (OGC )
Ordering ICD Overview:
Operations:
GetCapabilities
GetOptions
GetQuotation & GetQuotationResponse
Submit & SubmitResponse
GetStatus
Cancel & CancelResponse
DescribeResultAccess
June 2011 – Slide 8

9. Ordering ICD (OGC 06-141) – Requirement Classes
Because Ordering ICD supports different types of orders; with different modes: sync / async; with different delivery methods (media / online);
And different Service Providers are interested in few combinations only;
Then different conformance classes have been defined regrouping the most sensible combinations:
June 2011 – Slide 9

10. Ordering ICD (OGC 06-141) – Requirement Classes
June 2011 – Slide 10

11. Ordering ICD (OGC 06-141) – Conformance Classes
Full compliance is very difficult to achieve, possible examples of compliance are:
An Order Server supporting product ordering for scientific users should implement:
Core
MediaDelivery
ProductOrder
SceneSelection
Optionally it should support also on-line delivery:
OnlineDataAccess
OnlineDataDelivery
June 2011 – Slide 11

12. Ordering ICD (OGC 06-141) – Conformance Classes
An Order Server supporting product ordering for commercial users should implement:
Core
MediaDelivery
ProductOrder
SceneSelection
Quotation, and at least one of:
QuotationAsync
QuotationMonitoring
QuotationOffLine
QuotationSync
Optionally it should support also on-line delivery:
OnlineDataAccess
OnlineDataDelivery
June 2011 – Slide 12

13. Ordering ICD (OGC 06-141) – Requirement Classes
Statistics:
Requirement Class
Number of requirements
AsyncCancellation 7
Quotation 8
AsyncSubmit
QuotationAsync 5
Cancellation
QuotationMonitoring 4
Core 40
QuotationOffLine 3
MediaDelivery 2
QuotationSync
Notification 1
SceneSelection
OnlineDataAccess 12
SubscriptionOrder 6
OnlineDataDelivery
TaskingOrder
ProductOrder
TOTAL
126
June 2011 – Slide 13

14. Ordering ICD (OGC 06-141) – Conformance Classes
1:1 mapping between Conformance Classes and Requirements Classes (as required by OGC policies):
June 2011 – Slide 14

15. Ordering ICD (OGC 06-141) – Conformance Classes
Each Conformance Class is composed of a set of tests, each verifying one or more requirements of the corresponding Requirements Class.
Each Conformance Class covers all requirements of the corresponding Requirements Class.
It has to be noted that the tests reported in the Conformance classes have “temporal dependencies”: in fact for running one test another specific test might be needed (e.g. to test order status at least one order needs to be created in the Order Server by Submitting an order). Then:
The tests specified in a Conformance Class must be executed in the order they are specified in the document;
The tests of a Conformance Class can be started only if the tests of the parent class have been completed.
June 2011 – Slide 15

16. Ordering ICD (OGC 06-141) – Conformance Classes
Statistics:
Conformance Class
Number of tests
AsyncCancellation 4
Quotation 5
AsyncSubmit
QuotationAsync 2
Cancellation
QuotationMonitoring 3
Core 13
QuotationOffLine 1
MediaDelivery
QuotationSync
Notification
SceneSelection
OnlineDataAccess 6
SubscriptionOrder
OnlineDataDelivery
TaskingOrder
ProductOrder
TOTAL 70
June 2011 – Slide 16

17. Ordering ICD (OGC 06-141) Evolution
Summary of changes w.r.t. V0.9.4 (current operational baseline):
Added comprehensive list of processing options (inputs from ESA, EUMETSAT, CNES, MDA, DLR)
Added comprehensive list of scene selection options (inputs from ESA, EUMETSAT, CNES, MDA, DLR)
Implemented many comments received from: conterra, EUMETSAT, ESA (HMA-E and DAIL implementation projects)
Enhanced Contents section of Capabilities document (to allow clients to discover which collections, which functions, which mechanisms are supported by the server with minimal pre-configuration)
Processing options at order and order item level
Delivery options at order and order item level
June 2011 – Slide 17

18. Ordering ICD (OGC 06-141) Evolution
Summary of changes w.r.t. V0.9.4 (current operational baseline):
Enhanced Description of Scene Selection Options (one of the major weaknesses of the previous spec). Now the client can set scene selection options with minimal pre-configuration.
Order option model updated to SWE Common 2.0
Improved definition of delivery options
Added extensibility of the specification: xs:any added at order level, order item level and as search criterion
Document reformatted according to updated OGC policy and procedures.
June 2011 – Slide 18

19. Reference Order Server
A reference order server has been set-up with the following objectives:
Demonstrate the updated specification;
Support the implementation of ordering clients;
Support the implementation of ordering servers.
The implemented order server – OPGW - provides an interface compliant with Ordering V1.0.0; the ordering function has been accomplished by translating the incoming requests in EOLI XML calls to the back-end server. It is meant to be used with M2EOS.
In order to have a stand-alone installation of OPGW a simulator of EOLI XML Order server – MOHS has been also developed.
In order to test the join with SPS EO service, a simulator of SPS EO server – SPSEO has been implemented also.
June 2011 – Slide 19

20. Reference Order Server
Architecture:
Developed in Java (JDK )
Deployed within TOMCAT (6.0.32)
Web Service Layer developed using AXIS2 + XMLBEANS data binding
Light weight Java Database: HyperSQL V2
OPGW will be made available as open source
June 2011 – Slide 20

21. Ordering ETS
Ordering Executable Test Suite (ETS): “Implements” the test cases defined within the Conformance Classes
“Implementations” are defined as Compliance Test Language (CTL) Scripts
For each Conformance Class a dedicated CTL script has been prepared e.g.:
ETS_CC_OSEO_Core.ctl
ETS_CC_OSEO_Cancellation.ctl
ETS_CC_OSEO_MediaDelivery.ctl
ETS_CC_OSEO_OnlineDataDelivery.ctl
...
Tests within a Conformance Class are implemented within dedicated CTL scripts, one for each operation e.g.:
ETS_CC_OSEO_Core_GetCapabilities.ctl
ETS_CC_OSEO_Core_GetOptions.ctl
ETS_CC_OSEO_Core_GetStatus.ctl
June 2011 – Slide 21

22. ETS All tests are started from ETS.ctl CTL script ETS.ctl:
includes main .ctl-scripts of Conformance Classes
defines the variables provided to the test scripts
calls the main test scripts of the Conformance Classes
Some test implement a request-chain as some requests must be processed (e.g. submit) to test another one (e.g. getStatus)
Test messages are outside the CTL scripts, unless they are generated on the fly re-using results from previous tests.
If a test needs a test message, it is named with this rule:
<TEST_ID prefix>_<Operation name>.xml
e.g. for Core Conformance Class (§A.3.1) we have:
A_3_01_01_GetCapabilities.xml
A_3_01_02_GetCapabilities.xml
A_3_01_03_GetOptions.xml
A_3_01_04_01_GetOptions.xml
A_3_01_04_02_GetOptions.xml
....
June 2011 – Slide 22

23. ETS .ctl scripts are in the \ETS dir
the request messages are in the following path:
ETS\messages\requests
June 2011 – Slide 23

24. ETS
Currently UserManagement is not considered in the ETS
All tests defined in the ATS have been implemented and tested against the Reference Order Server
June 2011 – Slide 24