Issue 13279: Page 89: Figure 8.6 (qvt-rtf)
Source: Open Canarias, SL (Mr. Adolfo Sanchez-Barbudo Herrera, nobody)
Nature: Revision
Severity: Minor
Summary: Problem's text: 
    1.ReturnExp::value association my have multiplicity [0..1] in the diagram
    2.TryExp::catchClause association should be called exceptClause
Discussion: 
    1. It seems that the returned value of a return expression might be optional.
    2. Since the diagram and textual descriptioon are different, I'm not sure which was the original intention of the name of this reference. Reading the description's text
and the opposite role name (exceptOwner), I guees that the name must be "exceptClause".
suggestion: 
    1.In ReturnExp::value association replace mutiplicity 1 by multiplicity [0..1]. In the text is well described.
    2.In TryExp class change change the "catchClause" by "exceptClause"
- Page 90: Section 8.2.2.3 ComputeExp
Problem's text:    body : OclExpression [1] {composes, ordered}
Discussion: Ordered doesn't make sense in a univalued reference.
Suggestion: remove "ordered".

Resolution: Yes.
Yes.
Yes.
Already correct in the QVT 1.1 models
Revised Text: In Figure 8.6 replace the “catchClause” role from TryExp by “exceptClause”.
In Figure 8.6 replace the “1” multiplicity on ReturnExp.value by “0..1”.
In 8.2.2.3 ComputeExp replace
body : OclExpression [1] {composes, ordered}
by
body : OclExpression [1] {composes}
Actions taken:
January 15, 2009: received issue
July 15, 2014: closed issue
Discussion: 


End of Annotations:=====
ssues From: Adolfo Sánchez-Barbudo Herrera <adolfosbh@opencanarias.com>

This is issue # 13279

Page 89: Figure 8.6

Problem's text: 
    1.ReturnExp::value association my have multiplicity [0..1] in the diagram
    2.TryExp::catchClause association should be called exceptClause
Discussion: 
    1. It seems that the returned value of a return expression might be optional.
    2. Since the diagram and textual descriptioon are different, I'm not sure which was the original intention of the name of this reference. Reading the description's text
and the opposite role name (exceptOwner), I guees that the name must be "exceptClause".
suggestion: 
    1.In ReturnExp::value association replace mutiplicity 1 by multiplicity [0..1]. In the text is well described.
    2.In TryExp class change change the "catchClause" by "exceptClause"
- Page 90: Section 8.2.2.3 ComputeExp
Problem's text:    body : OclExpression [1] {composes, ordered}
Discussion: Ordered doesn't make sense in a univalued reference.
Suggestion: remove "ordered".