TACSIT Controller Interface for CMS Systems
Version 1.0 - Beta 1
Date: October 2010
dtc/10-10-11

Chapter/Section: 7.1
Title: Selection by track number
Nature: Enhancement
Severity: Significant

The ways to select by track number as well as to select within geographic geometry seem to me inefficient. Indeed, in that way there are 2 accesses to the TACSIT server(s): one to query on one to effectively select when an interface proposing to select from a an interface with a query as parameter would be more efficient since it implied just one access call to the TACSIT server.

TACSIT Controller Interface for CMS Systems
Version 1.0 - Beta 1
Date: October 2010
dtc/10-10-11

-------------------------------
Chapter/Section: 7.1
Title: addSelectionListener
Nature: Enhancement
Severity: Significant

This API seems to me very poor. Wouldn't it be possible to add some convenience APIs allowing a listener on the primary selection, the secondary selection, on setting or unsetting on of these selection... This would lower the number of server-client exchanges for nothing but test that this not something of interest.

TACSIT Controller Interface for CMS Systems
Version 1.0 - Beta 1
Date: October 2010
dtc/10-10-11

-------------------------------
Chapter/Section: all
Title: GeoPosition vs. GeodeticPosition
Nature: Revision
Severity: Significant

Two classes seems to speak of the same stuff: GeoPosition (see Section 2.3.1.3) and GeodeticPosition. My guess is that GeoPosition should be renamed ad GeodeticPosition. Please fix or explain.

TACSIT Controller Interface for CMS Systems
Version 1.0 - Beta 1
Date: October 2010
dtc/10-10-11

Chapter/Section: all
Title: Dealing with error at PIM level
Nature: Revision
Severity: Significant

Error should be dealt with at the PIM level for each method.

TACSIT Controller Interface for CMS Systems
Version 1.0 - Beta 1
Date: October 2010
dtc/10-10-11

Chapter/Section: 7.1
Title: SelectionType
Nature: Clarification
Severity: Minor

It is not clear what "OTHER" is for.

TACSIT Controller Interface for CMS Systems
Version 1.0 - Beta 1
Date: October 2010
dtc/10-10-11

-------------------------------
Page: 7
Title: Stanard
Nature: Clarification
Severity: Minor

"stanard" instead of "standard".

Chapter/Section: 2
Title: Conformance Criteria
Nature: Revision
Severity: Significant

Please add "completely" between "match" and "one or more of".

TACSIT Controller Interface for CMS Systems
Version 1.0 - Beta 1
Date: October 2010
dtc/10-10-11

Chapter/Section: 7.1
Title: Setting the categories of selectable items
Nature: Enhancement
Severity: Significant

I didn't find any interface allowing to set the categories of selectable items.

The proposed way to do the consistent centring with a moving entity seems inefficient and will imply unsmooth multiple movements of the viewport.
A specific interface allowing such a slaved centring with an entity would be, in my point of view, by far better than this.

Chapter/Section: 9
Title: Sample C++ header files
Nature: Enhancement
Severity: Significant

Please replace the "sample" before "C++ header files" with "normative".

"getEntityTypes" is misnamed because it doesn't get all the entity types, hence a name such as "getSelectableEntityTypes" would be more explicit.

TACSIT Controller Interface for CMS Systems
Version 1.0 - Beta 1
Date: October 2010
dtc/10-10-11

Page: 7
Title: Ref. to 6.3.2
Nature: Clarification
Severity: Minor

Broken reference to section 6.3.2.

In the AB today, when the TACSIT submission was presented, I noted that the normative PIM is expressed as a MagicDraw file, not a pure OMG-compliant XMI file. The normative PIM should be an OMG-compliant file and the MagicDraw file should be a convenience artifact.

The machine readable files include redundant and/or useless files – the .mdr and mdr.bak files are useless and the mdzip is not needed as well as the .xml file since one is a compressed version of the other.

The Compliance section should state how software complies e.g. it might say that for the Java PSM that software will implement all the normative APIs and exhibit the behavior for each as defined in the specification.

The Normative References section should be in part 2. However the current reference is not Normative and so the section should be blank

There is a Model file for the Java PSM but not the C++ PSM as claimed in the Manifest.