UML 2.2 RTF Avatar
  1. OMG Issue

UML22 — CombinedFragment Loop notation

  • Key: UML22-100
  • Legacy Issue Number: 8698
  • Status: closed  
  • Source: TMNA Services ( Jim Schardt)
  • Summary:

    There seems to be some confusion about how to show the notation for the loop combinedFragment. Some tools show only the minint and maxint for the loop InteractionOperator but do not allow you to show the full specification in the InteractionOperand. This is a limitation that allows for the modeling of simple for loops without an additional guard to model do while and do until types of loop constructs. I would suggest the UML Superstructure 2.0 be updated with the following:

    In Section 14.3.3 in Notation with header Loop:
    Place a simple example of a loop combined fragment with a InteractionOperand guard as well as a minint and maxint
    Add a paragraph that says something like, "In those cases where more control over the number of passes through the CombinedFragment is necessary use a separate InteractionConstraint. This InteractionConstraint is shown in square brackets covering the lifeline where the first event occurrence will occur, positioned above that event, in the containing Loop InteractionOperand. If this separate InteractionConstraint is true, the loop continues, otherwise the loop terminates."

  • Reported: UML 1.4.2 — Thu, 21 Apr 2005 04:00 GMT
  • Disposition: Resolved — UML 2.2
  • Disposition Summary:

    No Data Available

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