1. OMG Issue

EAI — clarify relationship between EAI, FCM and ECA

  • Key: EAI-39
  • Legacy Issue Number: 5351
  • Status: closed  
  • Source: Adaptive ( Pete Rivett)
  • Summary:

    Section 2.3 of EDOC explains that architectures will be defined at the E/CCA level and thereby mapped to business processes etc. CCA components will then be 'mapped down' to various technology choices with FCM (and hence EAI) being one of them. EDOC contains only a proof of concept mapping for Business Process to FCM and not CCA to FCM.
    This section also states that "Normative mappings from ECA to these models in the subject of future RFPs." It would seem that the current EAI RFP does not provide such a normative mapping (which I find disappointing though to be fair it was not a RFP requirement) and it should be made clear that this means one still has neither a development lifecycle nor a mechanism for either developing nor even recording the refinement from ECA (Enterprise/business architectures) to EIA technology. Just defining a correspondence between concepts or a means of representing EAI artefacts as CCA Components (6.5) does not achieve that. In particular it does not show how an arbitrary CCA design (possibly with defined constraints) can map to a EAI technology implementation. Without this, it is hard to evaluate the adequacy of the EAI proposal.

    FCM "is a low-level metamodel focused on the middleware machinery for executing message flows. Higher levels of abstraction can be built upon the FCM for integrating a whole range of technologies and runtime environments:" (examples include Message Brokering). FCM allows the definition of hierarchic decompositions and the mapping of flows to FCMComponents.
    EAI actually extends FCM rather than creating a higher level of grouping/abstraction

  • Reported: EAI 1.0b1 — Wed, 12 Jun 2002 04:00 GMT
  • Disposition: Resolved — EAI 1.0
  • Disposition Summary:

    See resolution to issue 4854

  • Updated: Fri, 6 Mar 2015 20:58 GMT