UML 2.2 RTF Avatar
  1. OMG Issue

UML22 — Use case extension inconsistencies

  • Key: UML22-49
  • Legacy Issue Number: 7993
  • Status: closed  
  • Source: Adaptive ( Mr. Pete Rivett)
  • Summary:

    According to Figure 401, an Extend object references at least one ExtensionPoint which itself must be owned by exactly one UseCase.
    Therefore it seems that the Extend.extendedCase property is redundant and should be derived.

    Also the section for ExtensionPoint does not include the useCase property shown in Figure 401, which itself does not show the

    {subset}

    .

    Proposed resolution
    -----------------------------

    1) Update Figure 401 to replace +extendedCase by +/extendedCase

    2) Update Figure 401 to replace +useCase by +useCase

    {subsets owner}

    .

    3) Section 16.3.3 Extend: update the Associations section to replace:
    extendedCase : UseCase [1] References the use case that is being extended. (Specializes DirectedRelationship.target.)

    by

    /extendedCase : UseCase [1] References the use case that is being extended: this is derived as the Use case that owns the ExtensionPoint(s). (Specializes DirectedRelationship.target.) in OCL: extendedCase = self.extensionLocation->useCase

    4) Section 16.3.4 ExtensionPoint update the Associations section to replace:
    No additional associations

    by

    useCase: UseCase [1] References the use case that owns the ExtensionPoint. (subsets owner.)

  • Reported: UML 1.4.2 — Mon, 20 Dec 2004 05:00 GMT
  • Disposition: Resolved — UML 2.2
  • Disposition Summary:

    No Data Available

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