1. HMA Follow On Activities
Task 2: Feasibility Analysis Service
(Sensor Planning Service)
Monthly Progress Meeting
2 March 2010
Reuben Wright, Deimos Space

2. Schedule Deliverables Actions Work in Progress SPS 2.0
SPS Extension for EO
SFRE Requirements
SFRE Development

3. Schedule 1/2

4. Schedule 2/2

5. Proposal Information: List of Documentation Deliverables

6. Proposal Information: List of Software Deliverables

7. New actions from PR 02/02/10 open
The current deliverables URD and SRD do not match the structure of the SSS, SRS and SDD documents. To be aligned.
Spotimage to propose an alignment with EO GML data model for pieces where there is overlap. A possibility would be URNs referring to the EO GML specification. [At AWG it was noted that these could be stored in a sub-space of the OGC registry. Note that this uses URLs (not URNs) and RDF descriptions.]
EO specific use cases and scenarios (including notification) should be included in one of the Task 2 deliverables. Old use cases and interaction diagrams from HMA-I Scenario TN can be redrawn. Spotimage/Deimos should review the old HMA-I Scenario TN, extract the old scenarios and use cases, validate them with the new evolution (e.g. reserve, confirm) since and update these scenarios and use cases. Should be included in one of the Task 2 deliverables.
DLR recommends to include also the scenario from GSCDA operational scenarios about tasking.
SPS Tasking Parameters: ESA requests Spotimage to check this list of parameters and see if it maps on descending, ascending etc. There is not yet a consensus on the list of parameters. DLR expresses doubt that Stereoscopic radar would fit these programming parameters. Spot Image will check. If not applicable to radar, this should be explained in the specification.
closed
Spotimage to reply to the post on the Forum from MDA about SPS.
Spotimage to list which are the possible bottlenecks for approval of the EO SPS specification, e.g. dependency on SPS 2.0 approval + SWECommon approval etc. Send about this including date the specification was sent to OAB.
Other HMA-FO tasks to register to the “Ordering SWG”. on
Action to organise a joint teleconf (programming/ordering) with MDA to better understand the tasking scenario where delivery options should be passed at tasking time without a separate ordering service.
ESA requests the other tasks to use the Task 4 SRS and SDD deliverables as reference and also apply the ECSS-E-ST-40C in a similar way for their RB and TS deliverables. The currently existing deliverables are to be reorganized accordingly. [see also action 34]

8. Status: released as an RFC
Work in Progress: SPS 2.0
Status: released as an RFC
There were several caveats:
The OAB will provide comments in parallel during public comment period. OAB members to use twiki to capture comments.
As per the OGC Policies and Procedures, there must be a technical presentation to the OGC Membership. This can happen at the closing Plenary in Frascati.
There is also OAB guidance as to how requirements might be better documented. This guidance will be provided during the public comment period.
To better match the OGC Specification Model
Requirements pulled out of text and labelled with URIs
Specification organised by requirements classes (including ATS)

9. Work in Progress: SPS Extension for EO
Status
Drafted throughout
To be done
Requirements pulled out of text and made explicit
ATS reorganised to match requirements classes

10. Work in Progress: SFRE Requirements
Requirements Baseline Documents
Version 1.0 documents asked to be reworked
Most recent ECSS 40C used
New documents are Software System Specification (SSS) and Software Requirements Specification (SRS)
RIDs
All minor (other than document reorganisation) and implemented
Process
Last review at Deimos and Astrium needed, then will be reissued

11. Work in Progress: SFRE Development
Development meeting
EADS Astrium, Toulouse 25/02/10
Decisions taken regarding process, scope, configuration
Development process
Multiple release strategy will be adopted. Allows for much more confidence in integration
Release 0 of SF Server (previous SPS software updated to SPS 2.0 schemas) is ready to test
Software Design Document (SDD)
Decision taken to produce an integrated document for both SF Client and SF Server
ECSS 40C will be followed