UML 2.2 RTF Avatar
  1. OMG Issue

UML22 — Section: Classes (02)

Open Closed All
  • Key: UML22-154
  • Legacy Issue Number: 9004
  • Status: closed  
  • Source: NIST ( Mr. Conrad Bock)
  • Summary:

    raisedException in Figure 10, reused without specialization by Operation in Figure 11 (the entry for it in Operation says it is redefined), but redefined in Figure 315. Should it be a derived union in Figure 10?

  • Reported: UML 2.0 — Sun, 25 Sep 2005 04:00 GMT
  • Disposition: Resolved — UML 2.2
  • Disposition Summary:

    The specialization from A_raisedException_operation to A_raisedException_behavioralFeature comes as a result of L3 package merge. Derived union would make sense if raisedException had a subsetting relationship instead of a specialization refinement.
    (Note also that the redefinition of raisedException is now noted on the diagram for Operation. Also, the resolution of Issue 12558 removed the later BasicBehaviors::BehavioralFeature::raisedException.)
    Revised Text:
    None.
    Disposition: Closed No Change
  • Updated: Fri, 6 Mar 2015 20:58 GMT