Issue 6075: UML2 super/pg.470/entry and exit points for composite states (uml2-superstructure-ftf) Source: Simula Research Laboratory (Mr. Bran Selic, selic(at)acm.org) Nature: Uncategorized Issue Severity: Summary: Two OCL constraints for entry and exit pseudostates of state machines (numbered [9] and [10]) only allow these psuedostates to be defined for the topmost regions of a state machine. This restriction is completely unnecessary and precludes common design patterns and should be removed. (In fact, from discussions with the authors of the spec, it seems that they were included due to a misunderstanding between two of the authors.) Resolution: see above Revised Text: Actions taken: August 22, 2003: received issue March 8, 2005: closed issue Discussion: The proposed resolution for this is described in the attached PDF file, with the changes indicated by the vertical change bars in the margin. Note that there are a few spurious change bars that were automatically generated when the new figure was inserted and the figure numbers changes – this forced some cross-references to automatically change. Specifically, the following changes are proposed (NB: the page numbers cited refer to the FAS document page and indicate where the change is to be made; the page numbers in parentheses match the page number in the attached PDF file – these were included for easy reference): ??Fig. 354: add a composition from State to Pseudostate to model ownership of entry and exit connectionPoints by a state. (These are further restricted by OCL constraints described below.) Note that there is no need for State to reference any ConnectionPointReferences, since the composite state is a part of the state machine. ??Page 461 (481) create a new subheading “Presentation Options” at the end of the section describing the ConnectionPointReferenceClass ??Page 461 (481): Move figure 360 and the entire paragraph preceding it and figure 362 and the entire paragraph preceding it into the new Presentation Options subsection in that order. ??Pg. 471 (491): extend the definition of entry and exit points to allow composite states to have entry and exit points, not just state machines (submachines) ??Pg. 472 (492): for notation (figures 371 and 372), add references to composite states in addition to state machine s. ??Pg. 473 (493): add a figure that shows the notation of entry and exit points for composite states just before the paragraph that precedes figure 373 ??Pg. 478 (499): add a paragraph at the end explaining the meaning of entry and exit points for composite states. ??Pg. 479 (500): add the new association end entry for ‘State::connectionPoint’ ??Pg. 480 (501): add two new constraints that identify that only composite states can have connection points and that these have to be entry and/or exit pseudostates and no other kinds. ??Pg. 482 (503): describe the semantics of entering and exiting a composite state through an entry/exit point respectively. ??Pg. 485 (506): add note just before fig. 506, explaining the notation of entry and exit points for composite states. ??Pg. 487 (508): clarify that the notation in figure 388 can also be used for composite states (but without the reference to a state machine) ??Pg. 489 (510): provide a reference to the example that shows the notation for entry and exit points for composite states in the Notation section. ??Pg. 493 (515): explain that entry and exit points on composite states can be added when specializing (extending) a state machine. ??Table 20: there were some incorrect references to pseudostates in this table that were fixed (somewhat peripherally related to this issue) 9_StateMachines.isssue-6075.pdf End of Annotations:===== To: issues@omg.org Subject: UML2 super/pg.470/entry and exit points for composite states X-Mailer: Lotus Notes Release 5.0.11 July 24, 2002 From: "Branislav Selic" Date: Fri, 22 Aug 2003 14:09:12 -0400 X-MIMETrack: Serialize by Router on D25ML05/25/M/IBM(Release 5.0.9a |January 7, 2002) at 08/22/2003 02:27:34 PM, Serialize complete at 08/22/2003 02:27:34 PM Two OCL constraints for entry and exit pseudostates of state machines (numbered [9] and [10]) only allow these psuedostates to be defined for the topmost regions of a state machine. This restriction is completely unnecessary and precludes common design patterns and should be removed. (In fact, from discussions with the authors of the spec, it seems that they were included due to a misunderstanding between two of the authors.) Bran Selic IBM Rational Software 770 Palladium Drive Kanata, Ontario, Canada K2V 1C8 ph. (613) 591-7915 fax (613) 599-3912 OMG Issue No: 6075 Title: UML2 super/pg.470/entry and exit points for composite states Source: International Business Machines (Mr. Bran Selic, bselic@ca.ibm.com) Summary: Two OCL constraints for entry and exit pseudostates of state machines (numbered [9] and [10]) only allow these psuedostates to be defined for the topmost regions of a state machine. This restriction is completely unnecessary and precludes common design patterns and should be removed. (In fact, from discussions with the authors of the spec, it seems that they were included due to a misunderstanding between two of the authors.) Discussion: Remove constraints [9] and [10] for the Pseudostate metaclass (pg. 499). This allows entry and exit points to be defined for any composite state, not just for sub-machines. Disposition: Resolved To: uml2-superstructure-ftf@omg.org Subject: Resolution to issue 6075 -- for ballot 19 X-Mailer: Lotus Notes Release 6.0.2CF1 June 9, 2003 From: Branislav Selic Date: Mon, 12 Jul 2004 10:55:03 -0400 X-MIMETrack: Serialize by Router on D25ML01/25/M/IBM(Release 6.0.2CF2|July 23, 2003) at 07/12/2004 10:55:07 This is a proposed resolution to the issue of enabling composite states to have entry and exit points. This was something that was not completed in the original submission. I am planning to post this resolution for ballot 19. Members of the state machine working group who reviewed thsi proposal found it acceptable. Cheers, Bran Issue-6075.040709.doc OMG Issue No: 6075 Title: UML2 super/pg.470/entry and exit points for composite states Source: International Business Machines (Mr. Bran Selic, bselic@ca.ibm.com) Summary: Two OCL constraints for entry and exit pseudostates of state machines (numbered [9] and [10]) only allow these psuedostates to be defined for the topmost regions of a state machine. This restriction is completely unnecessary and precludes common design patterns and should be removed. (In fact, from discussions with the authors of the spec, it seems that they were included due to a misunderstanding between two of the authors.) Discussion: The proposed resolution for this is described in the attached PDF file, with the changes indicated by the vertical change bars in the margin. Note that there are a few spurious change bars that were automatically generated when the new figure was inserted and the figure numbers changes . this forced some cross-references to automatically change. Specifically, the following changes are proposed: · Fig. 354: add a composition from State to Pseudostate to model ownership of entry and exit connectionPoints by a state. (These are further restricted by OCL constraints described below.) Note that there is no need for State to reference any ConnectionPointReferences, since the composite state is a part of the state machine. · Pg. 491: extend the definition of entry and exit points to allow composite states to have entry and exit points, not just state machines (submachines) · Pg. 492: for notation (figures 371 and 372), add references to composite states in addition to state machines. · Pg. 492-493: add a figure that shows the notation of entry and exit points for composite states. · Pg. 499: add a paragraph at the end explaining the meaning of entry and exit points for composite states. · Pg. 500: add the new association end entry for .State::connectionPoint. · Pg. 501: add two new constraints that identify that only composite states can have connection points and that these have to be entry and/or exit pseudostates and no other kinds. · Pg. 503: describe the semantics of entering and exiting a composite state through an entry/exit point respectively. · Pg. 506: add note just before fig. 506, explaining the notation of entry and exit points for composite states. · Pg. 508: clarify that the notation in figure 388 can also be used for composite states (but without the reference to a state machine) · Pg. 510: provide a reference to the example that shows the notation for entry and exit points for composite states in the Notation section. · Pg. 515: explain that entry and exit points on composite states can be added when specializing (extending) a state machine. · Table 20: there were some incorrect references to pseudostates in this table that were fixed (somewhat peripherally related to this issue) Disposition: Resolved Date: Tue, 13 Jul 2004 10:11:51 +0200 (CEST) Subject: Re: Resolution to issue 6075 -- for ballot 19 From: Birger Møller-Pedersen To: "Branislav Selic" Cc: uml2-superstructure-ftf@omg.org Reply-To: birger@ifi.uio.no User-Agent: SquirrelMail/1.4.3a X-Mailer: SquirrelMail/1.4.3a X-MailScanner-Information: This message has been scanned for viruses/spam. Contact postmaster@uio.no if you have questions about this scanning X-UiO-MailScanner: No virus found X-UiO-Spam-info: not spam, SpamAssassin (score=-5, required 12, UIO_MAIL_IS_INTERNAL -5.00) It does not mean anything for the net result, but the thing was not that this was not 'completed in the original submission'. When the original submission was made it was regarded as important that the existing notion of composite state was not changed, so the issue of entry/exit points for composite states was not pursued. /birger > This is a proposed resolution to the issue of enabling composite states to > have entry and exit points. This was something that was not completed in > the original submission. I am planning to post this resolution for ballot > 19. Members of the state machine working group who reviewed thsi proposal > found it acceptable. > > Cheers, > Bran To: uml2-superstructure-ftf@omg.org Cc: mu2i-ftf@omg.org Subject: Proposed resolution to issue 6075 (entry and exit to composite states) X-Mailer: Lotus Notes Release 6.0.1CF1 March 04, 2003 From: Branislav Selic Date: Sat, 24 Jul 2004 20:14:45 -0400 X-MIMETrack: Serialize by Router on D25ML01/25/M/IBM(Release 6.0.2CF2|July 23, 2003) at 07/24/2004 20:17:45 The following is a proposed resolution to issue 6075, for ballot 21. The state machine working group (Eran, Anders, and Birger) have reviewed this and agreed with it. Regards, Bran Issue-6075.040724.bvs.doc OMG Issue No: 6075 Title: UML2 super/pg.470/entry and exit points for composite states Source: International Business Machines (Mr. Bran Selic, bselic@ca.ibm.com) Summary: Two OCL constraints for entry and exit pseudostates of state machines (numbered [9] and [10]) only allow these psuedostates to be defined for the topmost regions of a state machine. This restriction is completely unnecessary and precludes common design patterns and should be removed. (In fact, from discussions with the authors of the spec, it seems that they were included due to a misunderstanding between two of the authors.) Discussion: The original design intent was to allow entry and exit points on composite states as well as on sub-machines. The proposed resolution is included in the appended PDF file with the required changes identified by the change bars in the margin. Disposition: Resolved From: "Thomas Weigert" To: "Branislav Selic" , Cc: Subject: RE: Proposed resolution to issue 6075 (entry and exit to composite states) Date: Sun, 25 Jul 2004 06:30:27 -0500 X-Mailer: Microsoft Outlook IMO, Build 9.0.6604 (9.0.2911.0) X-OriginalArrivalTime: 25 Jul 2004 11:30:52.0200 (UTC) FILETIME=[D77A4280:01C4723A] Bran, comments: 1. The "via" notation for entry and exit points seems to be a presentation option and might best be presented as such. 2. On p.500, why do we limit the connection points to be defined for composite states only? See the discussion with Stephen Mellor. Thanks, Th. -----Original Message----- From: Branislav Selic [mailto:bselic@ca.ibm.com] Sent: Saturday, July 24, 2004 7:15 PM To: uml2-superstructure-ftf@omg.org Cc: mu2i-ftf@omg.org Subject: Proposed resolution to issue 6075 (entry and exit to composite states) The following is a proposed resolution to issue 6075, for ballot 21. The state machine working group (Eran, Anders, and Birger) have reviewed this and agreed with it. Regards, Bran To: "Thomas Weigert" Cc: mu2i-ftf@omg.org, uml2-superstructure-ftf@omg.org Subject: RE: Proposed resolution to issue 6075 (entry and exit to composite states) X-Mailer: Lotus Notes Release 6.0.1CF1 March 04, 2003 From: Branislav Selic Date: Sun, 25 Jul 2004 13:40:59 -0400 X-MIMETrack: Serialize by Router on D25ML01/25/M/IBM(Release 6.0.2CF2|July 23, 2003) at 07/25/2004 13:41:03, Serialize complete at 07/25/2004 13:41:03 Thanks again, Thomas. on point 1, I will fix the proposal. On point 2, we do allow connection points to be on state machines as well. However, that requires a little more complex mechanism with submachine states that have connection point references. However, a regular composite state does not need the references since it is defined in the same context as the actual entry and exit points (so to speak). However, both state machines and composite states can have connection points (although I don't think this is the right solution for Steve's issue). It is only simple (non-composite) states that cannot have connection points. Hope this clears it up, Bran "Thomas Weigert" 07/25/2004 07:30 AM To Branislav Selic/Ottawa/IBM@IBMCA, cc Subject RE: Proposed resolution to issue 6075 (entry and exit to composite states) Bran, comments: 1. The "via" notation for entry and exit points seems to be a presentation option and might best be presented as such. 2. On p.500, why do we limit the connection points to be defined for composite states only? See the discussion with Stephen Mellor. Thanks, Th. -----Original Message----- From: Branislav Selic [mailto:bselic@ca.ibm.com] Sent: Saturday, July 24, 2004 7:15 PM To: uml2-superstructure-ftf@omg.org Cc: mu2i-ftf@omg.org Subject: Proposed resolution to issue 6075 (entry and exit to composite states) The following is a proposed resolution to issue 6075, for ballot 21. The state machine working group (Eran, Anders, and Birger) have reviewed this and agreed with it. Regards, Bran e-mail: bselic@ca.ibm.com