Application Management and System Monitoring Avatar
  1. OMG Specification

Application Management and System Monitoring — Open Issues

  • Acronym: AMSM
  • Issues Count: 5
  • Description: Issues not resolved
Open Closed All
Issues not resolved

Issues Descriptions

AMSM FTF2 report XMI file

  • Key: AMSM12-5
  • Legacy Issue Number: 13838
  • Status: open  
  • Source: Adaptive ( Pete Rivett)
  • 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.

  • Reported: AMSM 1.0 — Thu, 26 Mar 2009 04:00 GMT
  • Updated: Fri, 6 Mar 2015 20:57 GMT

Abstract classes link CIM_Action and CIM_Check can be instantiated

  • Key: AMSM12-4
  • Legacy Issue Number: 13246
  • Status: open  
  • Source: THALES ( Willy Boenink)
  • Summary:

    The Application Specification allows the abstract classes like CIM_Action and CIM_Check to be instantiated.

  • Reported: AMSM 1.0b2 — Tue, 13 Jan 2009 05:00 GMT
  • Updated: Fri, 6 Mar 2015 20:57 GMT

How is a kind of host specified

  • Key: AMSM12-3
  • Legacy Issue Number: 13237
  • Status: open  
  • Source: THALES ( Willy Boenink)
  • 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.

  • Reported: AMSM 1.0b2 — Tue, 13 Jan 2009 05:00 GMT
  • Updated: Fri, 6 Mar 2015 20:57 GMT

Error code

  • Key: AMSM12-2
  • Legacy Issue Number: 13231
  • Status: open  
  • Source: THALES ( Willy Boenink)
  • Summary:

    The AMS_ErrorCode key value are inconsistent, e.g. key 2 has value AMS_BADCONNECTIVITY, and key 2 has value AMS_BADFILTER

  • Reported: AMSM 1.0b2 — Tue, 13 Jan 2009 05:00 GMT
  • Updated: Fri, 6 Mar 2015 20:57 GMT

Aggregations/Associations in DCPS PSM:

  • Key: AMSM12-1
  • Legacy Issue Number: 13053
  • Status: open  
  • Source: THALES ( Willy Boenink)
  • 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

  • Reported: AMSM 1.0b2 — Fri, 31 Oct 2008 04:00 GMT
  • Updated: Fri, 6 Mar 2015 20:57 GMT