1. HMA Follow-on Kickoff Meeting
Negotiation and KO Meeting
24 June 2009, Frascati
Pier-Giorgio Marchetti, ESA
Yves Coene, SPACEBEL
Slide 1

2. Overview Project Tools Conformance Testing Schedule and Reviews
Baseline
Project Reporting etc.
Conformance Testing
Schedule and Reviews
Slide 2

3. Project Tools - Wiki Wiki & Forum http://wiki.services.eoportal.org
Register on to obtain login name and password.
Slide 3

4. Project Tools – RID Tracking
Cross review of documents
Excel Spreadsheet.
Slide 4

5. Action Tracking Action Tracking Excel spreadsheet, one tab per "Task".
Slide 5

6. Project Tools - other
Slide 6

7. Project Tools - Skeleton
HMA Skeleton
Simulates various HMA protocols
Available from Wiki.
Slide 7

8. Project Tools - Skeleton
Supports:
Catalogue, Ordering, Programming
Slide 8

9. Project Tools SSE Permanent Testbed Email alias
and
Transfer from services-test to services.eoportal.org only after "approval" from technical officer.
alias
(TBC)
Slide 9

10. Project Tools - Wiki Deliverables Page Project Baseline Page
Most recent versions
Project Baseline Page
Up-to-date HMA-FO project baseline will be put on HMA-FO Wiki. Will be controlled via HMA-FO Change Control Board.
Organised per standard.
Latest working versions (not yet baseline) will also be made available for information via HMA-FO Wiki.
Slide 10

11. Project Tools
Wiki - Baseline Page (HMA-T example)
Slide 11

12. Project Tools Progress Reporting - Monthly Reports
Contractual: Word Document per contractor
Technical Progress: Wiki Page per month. Predefined section headings.
Slide 12

13. Overview Project Tools Conformance Testing Schedule and Reviews
Baseline
Project Reporting etc.
Conformance Testing
Schedule and Reviews
Slide 13

14. Conformance Testing
Modifications to the TEAM engine shall be made available on Northrop Grumman Corporation’s teamengine pages on sourceforge.
Slide 14

15. SVN Repository – CTL Scripts
Slide 15

16. Conformance Testing CTL Scripts Mapping with ECSS-E-ST-40C
HMA-T test scripts available on OGC SVN ("hma" project). See link on "HMA Open Software" page.
Mapping with ECSS-E-ST-40C
Annex L: "Software validation testing specification"
Slide 16

17. Conformance Testing Two levels of testing:
Item Under Test: catalogue server, ordering server, feasibility server, EO WCS server etc.
ATS, ETS fulfil role of ECSS test artifacts (see below)
Item Under Test: developed CTL test scripts (i.e. client software)
Requires Acceptance Test Plan for the scripts. Should also define which endpoints will be tested, cross testing if any etc.
Need to demonstrate scripts find errors
Use cases to be defined in Technical Specification (TS)
Slide 17

18. Conformance Testing
Mapping with ECSS-E-ST-40C
Slide 18

19. Conformance Testing
Mapping with ECSS-E-ST-40C
Slide 19

20. Conformance Testing Other documents to be included in the baseline:
“HMA Testing Policy”, HMAT-TN-0001-IGN, Issue 1, revision 2, 9/03/ Update expected still.
OGC r2, Compliance Test Language (CTL), version 0.6, 31/03/2009.
The Specification Model – Modular specifications, OGC r2, version 1.0.1, 11/03/2009.
Slide 20

21. Overview Project Tools Conformance Testing Schedule and Reviews Wiki
Slide 21

22. Common Schedule and Reviews
Preliminary review:
T0+4 (Task 4), T0+4 (Task 1), T0+6 (Task 2), T0+5 (Task 3)
Midterm review
T0+7 (Task 4), T0+8M (Task 1), T0+9 (Task 2), T0+10M (Task 3) AR
T0+14M (Task 1), T0+17 (Task 2), T0+15M (Task 3), T0+17 (Task 4) FP
T0+18M
Locations
September 2009 – OGC TC Darmstadt (=T0+3M)
March 2010 – OGC TC ESRIN (=T0+9M)
Other: Frascati
Slide 22

23. Lessons learned and recommendations
Use same CTL language specification, e.g. for <soap> tag.
Be clear on what is in or out of scope
Which bindings ?
CITE tests for a "layer" without tests for underlying layer make not make sense. E.g. CITE for EO EP might be limited to testing mapping and leave tests of operations to underlying specs (e.g. ebRIM AP) for which no CTL scripts exist.
Consider that CITE targets may be proxy implementations, thus incomplete and read-only.
Scripts shall not stop after one failure.
CTL scripts shall be run from Web Portal "manager" and not just in batch mode without user interface.
Slide 23

24. Risks
Preliminary:
Baselines of 4 tasks may diverge (quote different applicable versions of some documents).
Obtain coherent results across Tasks with long duration and few physical meetings (about one every 6 months).
Impact of external events/decisions (OGC SWG, INSPIRE) on direction/content/timeliness of HMA baseline specifications.
Divergence of Ordering (OGC ) and new Programming OGC specifications. E.g. asynchronous solution.
Scope of CITE tests for layered specifications. Testing only the top-layer may be too little. E.g. EO EP without ebRIM AP or CSW testing. Same risk for EO SPS and EO WCS.
Slide 24

25. Proposed Actions All partners to:
Provide abstract of their Follow-on task in appropriate section on HMA-FO Wiki (TBC) – one page per partner.
Communicate addresses to be included in project alias.
Publish meeting slides on dedicated HMA-FO Wiki Page.
List reference implementation (and test) end-points on Wiki
Publish reference datasets on Wiki
Slide 25