UML 2.4 RTF Avatar
  1. OMG Issue

UML24 — Wrong constraint on Operation::bodyCondition

  • Key: UML24-113
  • Legacy Issue Number: 15768
  • Status: closed  
  • Source: NASA ( Dr. Maged Elaasar)
  • Summary:

    The spec says:

    bodyCondition: Constraint[0..1]
    An optional Constraint on the result values of an invocation of this Operation. Subsets Namespace::ownedRule

    couple this with:

    The bodyCondition for an operation constrains the return result. The bodyCondition differs from postconditions in that
    the bodyCondition may be overridden when an operation is redefined, whereas postconditions can only be added during

    Also, in the current MM, the defined operations logic is implemented as a body Condition.

    Therefore, the bodyCondition is not an invariant, but rather a condition that describes the return result. of an operation

    Since a non-query operation can also have a return result, I see no reason to prevent a body condition on it.

  • Reported: UML 2.3 — Fri, 15 Oct 2010 04:00 GMT
  • Disposition: Resolved — UML 2.4
  • Disposition Summary:

    Merged with 15501

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