Issue 15501: bodyCondition and isQuery (uml2-rtf)
Source:  (Dr. Maged Elaasar, melaasar(at)gmail.com)
Nature: Uncategorized Issue
Severity: 
Summary: Constraint [7] in Kernel::Operation says:

"A bodyCondition can only be specified for a query operation"

Let us look at the definition of isQuery and bodyCondition:

bodyCondition: Constraint[0..1] 
An optional Constraint on the result values of an invocation of this Operation. 

isQuery : Boolean 
Specifies whether an execution of the BehavioralFeature leaves the state of the system unchanged (isQuery=true) or whether side effects may occur (isQuery=false).


Question:

I am not sure why specifying a condition on the result of an operation is only limited to operations with no side effects. What is wrong with specifying a condition on the result of a non-query operation?

Resolution: 
Revised Text: 
Actions taken:
September 13, 2010: received issue
Discussion: 

End of Annotations:=====
ubject: bodyCondition and isQuery
To: uml2-rtf@omg.org
X-Mailer: Lotus Notes Release 7.0 HF277 June 21, 2006
From: Maged Elaasar <melaasar@ca.ibm.com>
Date: Sun, 12 Sep 2010 21:53:05 -0400
X-MIMETrack: Serialize by Router on D25ML03/25/M/IBM(Release 8.0.1|February 07, 2008) at
 09/12/2010 21:53:05


Constraint [7] in Kernel::Operation says:

"A bodyCondition can only be specified for a query operation"

Let us look at the definition of isQuery and bodyCondition:

bodyCondition: Constraint[0..1] 
An optional Constraint on the result values of an invocation of this Operation. 

isQuery : Boolean 
Specifies whether an execution of the BehavioralFeature leaves the state of the system unchanged (isQuery=true) or whether side effects may occur (isQuery=false).


Question:

I am not sure why specifying a condition on the result of an operation is only limited to operations with no side effects. What is wrong with specifying a condition on the result of a non-query operation?

Maged