-
Key: UMLR-85
-
Legacy Issue Number: 9406
-
Status: open
-
Source: International Business Machines ( Mr. Jim Amsden)
-
Summary:
Section 7.3.36 specifies the notation for Operation, but there is no notation for denoting raisedExceptions. Section 12.3.41 introduces Parameter::isException and suggests exception parameters are indicated out parameters with
{exception}after the parameter type to indicate Parameter::isException=true.
However, Operation::raisedException is not a Parameter, it is a reference to a Type. So a raisedException is not a TypedElement like parameter, has no multiplicity or ordering, etc. Raised exceptions are quite different than parameters and even in activities, RaiseExceptionAction and ExceptionHandlers do not exchange exception data through parameters.
Consider adding <oper-property> ::= 'throws' '('<type-list>')' in section 7.3.36 for denoting exceptions that could be raised by an operation. This is a significant part of the specification of an operation indicating information clients must know in order to use the operation and should be clearly visible in the operation's signature.
-
Reported: UML 2.5 — Wed, 1 Mar 2006 05:00 GMT
-
Updated: Fri, 6 Mar 2015 20:57 GMT
UMLR — UML2: No notation for indicating Operation::raisedException
- Key: UMLR-85
- OMG Task Force: UML 2.6 RTF