BACM 1.0b2 FTF Avatar
  1. OMG Issue

BACM — The BACM specification does not document XML for interoperability

  • Key: BACM-75
  • Status: open   Implementation work Blocked
  • Source: Agile Enterprise Design ( Fred Cummins)
  • Summary:

    The BACM specification, diagrams and text, specifies the BACM model using stereotypes that are not consistent with MOF. Consequently, the XML of the specified model is translated to a MOF-compliant XML as required by the RFP and interoperability of implementations. Both XML models are unnecessarily complex since there is no need to use stereotypes. MOF associations are sufficient, and the model would be more straightforward. The implementation Intent can be adequately specified in text with constraints, if necessary. The intent appears to be an effort to over-specify the expected method for development of an application of the model.

  • Reported: BACM 1.0a1 — Mon, 9 Jan 2023 01:04 GMT
  • Updated: Thu, 9 Mar 2023 00:09 GMT