EAI 1.0 NO IDEA Avatar
  1. OMG Issue

EAI — Derivation of the "defines" association for EAIPrimitiveOperator

  • Key: EAI-19
  • Legacy Issue Number: 4892
  • Status: closed  
  • Source: Model Driven Solutions ( Mr. Ed Seidewitz)
  • Summary:

    Document: UML Profile and Interchange Models for EAI
    Section: (EAIPrimitiveOperator)

    Under Constraints in Section it states that "When used in an EAIMessageFlow, an EAIPrimitiveOperator also 'defines' a type." Since this is listed as a constraint, and since the "defines" association is shown as <<derived>> in Figure 6-18, one would assume that the constraint is intended to give the derivation of the association. But it certainly does not state that clearly, nor do I see any way, in the underlying FCM, for an EAIPrimitiveOperator (as an FCMFunction) to define an FCMType in the context of an EAIMessageFlow (as an FCMComposition).

    Either make the association not derived (in which case the constraint statement needs to be expanded into a statement of the semantics of what it means for a primitive operator to "define a type") or make the derivation constraint much more explicit (i.e., provide the OCL).

  • Reported: EAI 1.0b1 — Fri, 22 Feb 2002 05:00 GMT
  • Disposition: Resolved — EAI 1.0
  • Disposition Summary:

    see below

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