UML 2.2 RTF Avatar
  1. OMG Issue

UML22 — UML2: Actor cannot have ownedAttributes

  • Key: UML22-303
  • Legacy Issue Number: 10780
  • Status: closed  
  • Source: International Business Machines ( Mr. Jim Amsden)
  • Summary:

    Constraint [1] in section 16.3.1 is incorrect.
    [1] An actor can only have associations to use cases, components, and classes. Furthermore these associations must be binary.
    self.ownedAttribute->forAll ( a |
    (a.association->notEmpty()) implies
    ((a.association.memberEnd.size() = 2) and
    (a.opposite.class.oclIsKindOf(UseCase) or
    (a.opposite.class.oclIsKindOf(Class) and not a.opposite.class.oclIsKindOf(Behavior))))

    An Actor is a BehavioredClassifier and therefore cannot have ownedAttributes. The constraint above would have to iterate over all the associations in the model and insure that if one ownedEnd is an Actor or UseCase, the other ownedEnd must be a UseCase or Actor respectively.

  • Reported: UML 2.1 — Tue, 20 Feb 2007 05:00 GMT
  • Disposition: Resolved — UML 2.2
  • Disposition Summary:

    Agreed. This also resolves issues 13948 and 14875

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