Issues for Mailing list of the AMSM Revision Task Force
To comment on any of these issues, send email to amsm-rtf@omg.org. (Please include the issue number in the Subject: header, thusly: [Issue ###].) To submit a new issue, send email to issues@omg.org.
List of issues (green=resolved, yellow=pending Board vote, red=unresolved)
Issue 13053: Aggregations/Associations in DCPS PSM:
Issue 13220: CIM_Process/CIM_Thread OSName attribute missing
Issue 13231: Error code
Issue 13237: How is a kind of host specified
Issue 13246: Abstract classes link CIM_Action and CIM_Check can be instantiated
Issue 13316: The association with AMS_Host is redundant
Issue 13838: AMSM FTF2 report XMI file
Issue 14091: Issue: Figures 7.7 and 7.8 on pages resp. 38 and 39 are identical
Issue 13053: Aggregations/Associations in DCPS PSM: (amsm-rtf)
Click here for this issue's archive.
Source: THALES (Mr. Willy Boenink, willy.boenink@nl.thalesgroup.com)
Nature: Enhancement
Severity: Significant
Summary:
Aggregations/Associations in DCPS PSM: The mapping of aggregations and associations from the PIM model to the DCPS PSM are not always practical. Due to some mapping rules, references are defined more than once, causing potential inconsistencies (e.g. sequence of relations in one topic with Owner reference in the addressed topic). Rules sometimes disable query opportunities (e.g. use of sequences and unions). The DCPS PSM preferably should do without sequences and unions, and redundant information
Resolution:
Revised Text:
Actions taken:
October 31, 2008: received issue
April 30, 2009: deferred
Discussion: Too much work, too late. Besides, this not an impediment for implementation. DEFERRED
Issue 13220: CIM_Process/CIM_Thread OSName attribute missing (amsm-rtf)
Click here for this issue's archive.
Source: THALES (Mr. Willy Boenink, willy.boenink@nl.thalesgroup.com)
Nature: Revision
Severity: Significant
Summary: CIM_Process/CIM_Thread OSName attribute missing According the PIM on page 39, CIM_Process and CIM_Thread have an attribute OSName. In the DCPS PSM there is only an attribute Name and not an OSName.
Resolution:
Revised Text:
Actions taken:
January 13, 2009: received issue
Issue 13231: Error code (amsm-rtf)
Click here for this issue's archive.
Source: THALES (Mr. Willy Boenink, willy.boenink@nl.thalesgroup.com)
Nature: Revision
Severity: Significant
Summary: The AMS_ErrorCode key value are inconsistent, e.g. key 2 has value AMS_BADCONNECTIVITY, and key 2 has value AMS_BADFILTER
Resolution:
Revised Text:
Actions taken:
January 13, 2009: received issue
April 30, 2009: deferred
Discussion: No time left.
Issue 13237: How is a kind of host specified (amsm-rtf)
Click here for this issue's archive.
Source: THALES (Mr. Willy Boenink, willy.boenink@nl.thalesgroup.com)
Nature: Clarification
Severity: Significant
Summary: The AMS_DeploymentLinkSpec specifies the host for the deployment. This can be an kind of host (requested hardware). How is a kind of host specified.
Resolution:
Revised Text:
Actions taken:
January 13, 2009: received issue
April 30, 2009: deferred
Discussion: Need time to think more on that.
Issue 13246: Abstract classes link CIM_Action and CIM_Check can be instantiated (amsm-rtf)
Click here for this issue's archive.
Source: THALES (Mr. Willy Boenink, willy.boenink@nl.thalesgroup.com)
Nature: Clarification
Severity: Significant
Summary: The Application Specification allows the abstract classes like CIM_Action and CIM_Check to be instantiated.
Resolution: No time left.
Revised Text:
Actions taken:
January 13, 2009: received issue
April 30, 2009: deferred
Issue 13316: The association with AMS_Host is redundant (amsm-rtf)
Click here for this issue's archive.
Source: THALES (Mr. Willy Boenink, willy.boenink@nl.thalesgroup.com)
Nature: Revision
Severity: Significant
Summary: The association with AMS_Host is redundant. AMS_OperatingSystem has an association with AMS_Host, see figure 7.19 and 7.20 on page 96/97. This implies that the association with AMS_Host in Application Deployment Specification class diagram on page 57 is redundant
Resolution:
Revised Text:
Actions taken:
January 22, 2009: received issue
April 30, 2009: deferred
Discussion: Not enough time.
Disposition: Deferred
Issue 13838: AMSM FTF2 report XMI file (amsm-rtf)
Click here for this issue's archive.
Source: Adaptive (Mr. Pete Rivett, pete.rivett@adaptive.com)
Nature: Uncategorized Issue
Severity:
Summary: AMSM FTF2 report XMI file http://doc.omg.org/dtc/09-02-10
[PJR] This is a UML 1.4 XMI 1.1 file, created by a Japanese tool called Jude. It has some structural problems e.g. AssociationEnds owned by the Package not the Association.
Resolution:
Revised Text:
Actions taken:
March 26, 2009: received issue
Issue 14091: Issue: Figures 7.7 and 7.8 on pages resp. 38 and 39 are identical (amsm-rtf)
Click here for this issue's archive.
Source: THALES (Dr. Jacek Skowronek, jacek.skowronek@nl.thalesgroup.com jacek_skowronek@hotmail.com)
Nature: Uncategorized Issue
Severity:
Summary: Issue: Figures 7.7 and 7.8 on pages resp. 38 and 39 are identical.
Resolution: Figure 7.7 should be replaced by another figure, which will be supplied as part fo the move to the new UML tool.
Cheers,
Resolution:
Revised Text:
Actions taken:
July 22, 2009: received issue