Issue 12354: Section: 15.3.7 Constraint [2] (uml2-rtf) Source: (, ) Nature: Enhancement Severity: Significant Summary: Constraint [2] says: A protocol transition never has associated actions. My problem is that this constraint makes it impossible to specify a consistent pair of a server protocol state machine (PSM) and a client PSM. The server PSM has call events as triggers. It also has internal events causing autonomous state transitions. However, the latter transitions must be notified to the client PSM. This can only be done by actions in which signal events are generated to the client FSM. Such signals are the triggers in the client FSM; and in fact the same problem happens here. Since the call events to the server PSM are caused by internal events at the client PSM, that force call events to the server PSM in the actions. I hope this issue can be solved or at least clarified. Thanks. Resolution: Revised Text: Actions taken: March 23, 2008: received issue Discussion: End of Annotations:===== m: webmaster@omg.org Date: 23 Mar 2008 15:17:47 -0500 To: Subject: Issue/Bug Report -------------------------------------------------------------------------------- Name: Tis Veugen Company: Logica mailFrom: Tis.Veugen@gmail.com Notification: Yes Specification: UML Superstructure Specification Section: 15.3.7 FormalNumber: formal/2007-11-04 Version: v2.1.2 RevisionDate: 11/04/2007 Page: 536 Nature: Enhancement Severity: Significant HTTP User Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; nl; rv:1.8.1.7) Gecko/20070914 Firefox/2.0.0.7 Description Constraint [2] says: A protocol transition never has associated actions. My problem is that this constraint makes it impossible to specify a consistent pair of a server protocol state machine (PSM) and a client PSM. The server PSM has call events as triggers. It also has internal events causing autonomous state transitions. However, the latter transitions must be notified to the client PSM. This can only be done by actions in which signal events are generated to the client FSM. Such signals are the triggers in the client FSM; and in fact the same problem happens here. Since the call events to the server PSM are caused by internal events at the client PSM, that force call events to the server PSM in the actions. I hope this issue can be solved or at least clarified. Thanks.