Issue 15989: The fUML subset shuold support the raising and handling of exceptions (fuml-rtf) Source: Model Driven Solutions (Mr. Ed Seidewitz, ed-s(at)modeldriven.com) Nature: Uncategorized Issue Severity: Summary: Specification: Semantics of a Foundational Subset for Executable UML Models, FTF Beta 3 (ptc/10-03-14) The submission team for the Alf action language felt that is was important that the action language be able to support exceptions, since existing class models in UML may include operations that raise exceptions and it should be possible to use the action language to specify methods for such operations without having to change how errors are reported. However, without exceptions being included in the fUML subset, the mapping of the raising and handling of exceptions in the action language to fUML was too complicated and probably semantically questionable. Therefore, support for the raising and handling of exceptions should be included in the fUML subset so that it can properly be included in the surface action language notation. Resolution: Defer The RTF agrees this issue needs resolution but, due to lack of time, is deferring its resolution to the next RTF. Revised Text: Actions taken: January 26, 2011: received issue January 7, 2013: Deferred December 22, 2015: closed issue Discussion: End of Annotations:===== ubject: The fUML subset shuold support the raising and handling of exceptions Date: Wed, 26 Jan 2011 12:35:09 -0500 X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: The fUML subset shuold support the raising and handling of exceptions thread-index: Acu9f2D2Am8MAoR9TPK8MHwmczOQ2A== From: "Ed Seidewitz" To: Specification: Semantics of a Foundational Subset for Executable UML Models, FTF Beta 3 (ptc/10-03-14) The submission team for the Alf action language felt that is was important that the action language be able to support exceptions, since existing class models in UML may include operations that raise exceptions and it should be possible to use the action language to specify methods for such operations without having to change how errors are reported. However, without exceptions being included in the fUML subset, the mapping of the raising and handling of exceptions in the action language to fUML was too complicated and probably semantically questionable. Therefore, support for the raising and handling of exceptions should be included in the fUML subset so that it can properly be included in the surface action language notation.