ESA > Join & Share > HMA > HMA-FO Progress Task 2 1005

(Cached)

HMA-FO Progress Task 2 1005

Project Manager Assessment

The status of the project is nominal.

Key Problem List

None

Deliverables Table

I65.1 HMA-FO-DMS-PMD-PMP01-E-R Project Management Plan. v1.0
I65.7 HMA-FO-DMS-QMD-PAP01-E-R Project Assurance Plan. v1.0
I51.2.2 Interface Control Document, I25.2 Specifications:
- OGC 09-001 SWE Service Model. RFC
- OGC 08-094 SWE Common Data Model. RFC
- OGC 09-000 SPS 2.0. RFC
- OGC 07-018 EO Extension for SPS. Draft
I51.1 HMA-FO-DMS-TEC-URD01-10-E-R Software system specification (SSS). v1.1
I51.2.1 HMA-FO-DMS-TEC-SRD01-10-E-R Software requirements specification (SRS). v1.1
I51.3.1 HMA-FO-DMS-TEC-ATP01-10-E-R Acceptance Test Plan. Awaiting confirmation that format is acceptable.
I51.4.1 HMA-FO-DMS-TEC-SDD01-10-E-R Software Design Document (SDD). Draft

WP1000 Project Management

Activities performed

Progress Meeting (and minutes, actions etc)
Coordination with subcontractors
Progress report updated
Coordination of EO Extension for SPS parameters review

Outcome and results

Ongoing

Problems and concerns

None

Plans for next period

General Project Management work

WP 2000: Completion of the SPS Specification

Activities performed

Final drafting of RFC candidate SPS Extension for EO.
Drafts of SPS 2.0 and SWE specifications are in RFC. Comments being discussed.

Outcome and results

Draft Specifications.

Problems and concerns

SPS 2.0 will need to be revised to match OGC Specification Model more closely. Need to ensure this is done in a timely fashion.
Identifier concept must be harmonised across all SWE specs, iGSI hope is to have everyone agree on use of http-URIs
SPS EO Specification has not received as many reviews as was hoped for. RFC version to be circulated widely to ensure it matches as many mission systems as closely as possible

Plans for next period

SPS EO Specification move to RFC agreed at or before June TC
SPS 2.0 and Swe Common RFC comments to be decided upon at June TC

WP 3000: Sensor Feasibility Reference Environment

Activities performed

Development work on SF Client and SF Server
Drafting architecture documents

Outcome and results

Internal release 1 of SF Server

Problems and concerns

None

Plans for next period

Internal release 2 SF Client (first UI) and SF Server
Architecture documents
Drafting of Test Plan (once format is decided)

WP 4000: EO Extension for SPS 2.0 - Conformance Testing

Activities performed

Discussion of suitable conformance classes for SPS specifications and level of detail in SPS ATS
Investigation of different TEAM engine options

Outcome and results

None (awaiting final ATS and answers on TEAM Engine)

Problems and concerns

TEAM engine situation complicated. Several versions exist.

Plans for next period

Get and set up TEAM engine
Begin development of ETS, based on ATS for EO Extension for SPS in RFC candidate

WP 5000: Additional Server Environments Demonstration

Activities performed

None

Outcome and results

None

Problems and concerns

None

Plans for next period

None

WP 6000: Warranty

Activities performed

None

Outcome and results

None

Problems and concerns

None

Plans for next period

None

Contributors to this page:

Page last modified on Tuesday 01 of June 2010 11:40:46 CEST by .

Category: HMA

History

Search Help

Non Advanced Search or Natural Search

The documents are returned sorted on relevance depending on order, proximity, frequency of terms.

Advanced Search or Boolean Search

Default search behavior

By default, all search terms are optional. It behaves like an OR logic. Objects that contain the more terms are rated higher in the results and will appear first in their type. For example, wiki forum will find:

objects that include both terms
objects that include the term wiki
objects that include the term forum

Requiring terms

Add a plus sign ( + ) before a term to indicate that the term must appear in results. Example: +wiki forum will find objects containing at least wiki. Objects with both terms and many occurences of the terms will appear first.

Excluding terms

Add a minus sign ( - ) before a term to indicate that the term must not appear in the results. To reduce a term's value without completely excluding it, use a tilde. Example: -wiki forum will find objects that do not contain wiki but contain forum

Grouping terms

Use parenthesis ( ) to group terms into subexpressions. Example: +wiki +(forum blog) will find objects that contain wiki and forum or that contain wiki and blog in any order.

Finding phrases

Use double quotes ( " " ) around a phrase to find terms in the exact order, exactly as typed. Example: "Alex Bell" will not find Bell Alex or Alex G. Bell.

Using wildcards

Add an asterisk ( * ) after a term to find objects that include the root word. For example, run* will find:

objects that include the term run
objects that include the term runner
objects that include the term running

Reducing a term's value

Add a tilde ( ~ ) before a term to reduce its value indicate to the ranking of the results. Objects that contain the term will appear lower than other objects (unlike the minus sign which will completely exclude a term). Example: +wiki ~forum will rate an object with only wiki higher that an object with wiki and forum.

Changing relevance value

Add a less than ( < ) or greater than ( > ) sign before a term to change the term's contribution to the overall relevance value assigned to a object. Example: +wiki +(>forum < blog) will find objects that contain wiki and forum or wiki and blog in any order. wiki forum will be rated higher.