Issue 13068: Not all expected ESE state changes are described (amsm-ftf) Source: THALES (Mr. Willy Boenink, willy.boenink(at)nl.thalesgroup.com) Nature: Revision Severity: Significant Summary: Not all expected ESE state changes are described State changes that are initiated by the managed process are not described in the state diagram. For instance a managed process can terminate with returning a code indicating an error. There is no state change from RUNNING to ERROR however. Resolution: Add a state change from RUNINNG to ERROR. This state change doesn't imply a new method since it's caused by the crash of the process. Specify that the state change "STOP" can be initiated by the process itself. Revised Text: eplace Fig 7.27 ("Executable Software Element state diagram") with the following one: In the table of the paragraph 7.1.14.1.4 ("Running"): Replace the second line with the following one: STOP Stop the Software Element. This Transition is also automatically followed when the Executable Software Element normally stops. Add the following line: error This transition is automatically followed when the Executable Software Element crashes. Actions taken: November 12, 2008: received issue July 23, 2009: closed issue Discussion: End of Annotations:===== m: webmaster@omg.org Date: 12 Nov 2008 07:54:56 -0500 To: Subject: Issue/Bug Report -------------------------------------------------------------------------------- Name: Willy Boenink Company: Thales Nederland mailFrom: willy.boenink@nl.thalesgroup.com Notification: No Specification: AMSM Section: 7.1.14.1 FormalNumber: dtc/2008-02-02 Version: Beta 2 RevisionDate: 02/02/2008 Page: 118 Nature: Revision Severity: Significant HTTP User Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-GB; rv:1.9) Gecko/2008051206 Firefox/3.0 Description Not all expected ESE state changes are described State changes that are initiated by the managed process are not described in the state diagram. For instance a managed process can terminate with returning a code indicating an error. There is no state change from RUNNING to ERROR however.