Issue 1790: Lack of features commonly used in OCL (ocl2-rtf) Source: (, ) Nature: Enhancement Severity: Significant Summary: Summary: The current specification for OCL lacks many of the features we commonly use when doing formal specification of class interfaces, e.g. the ability to specify the frame condition, the ability to specify postconditions case-wise, the ability to specify when exceptions are thrown, etc. To bring OCL closer to the state of the art, I would like to see these considered as future extensions. Resolution: This issue was forked off from UML 1.x 15 years ago. It doesn't seem to have anything to do with OCL at all. But rather than throw the issue back to UML, let's address it anyway. One could imagine a UML extension that introduced a Frame class and an Operation.ownedFrameCondition to host it. OCL expressions could then impose the semantics. However a Frame would be specific to a particular implementation approach, and so it would seem more appropriate to use stereotypes to model the implementation characteristics. Perhaps one of the standard UML profiles already provides this capability. Disposition: Closed, no change Revised Text: Actions taken: August 10, 1998: received issue July 22, 1999: Deferred:UML 1.4/2.0 December 2, 2004: Transferred to OCL 2.0 FTF December 23, 2013: closed issue Discussion: This issue needs to be resolved by the OCL 2.0 Finalization Task Force. This is an UML 1.x issue transferred to the OCL 2 FTF. Not all the extra facilities suggested by the text of this issue have been incorporated to the OCL2 specification. Specific facilities for specifying constraints on class interfaces could be considered within the context of an RTF. Disposition: Deferred End of Annotations:===== Return-Path: Date: Sat, 8 Aug 1998 16:19:59 -0400 From: www To: juergen@omg.org, web-incoming@omg.org Subject: WWW Form output Name: Gary Daugherty Company: Rockwell Email: gwdaughe@collins.rockwell.com Notification: Yes Specification: OCL specification Section: Formal #: ad/97-08-08 Version: 1.1 Revision_Date: 1 Sept 1997 Page: Nature: Enhancement Severity: Significant full_desc: The current specification for OCL lacks many of the features we commonly use when doing formal specification of class interfaces, e.g. the ability to specify the frame condition, the ability to specify postconditions case-wise, the ability to specify when exceptions are thrown, etc. To bring OCL closer to the state of the art, I would like to see these considered as future extensions. A good summary of what we are looking for can be found in Gary T. Leavens and Albert L. Baker. Enhancing the Pre- and Postcondition Technique for More Expressive Specifications. Department of Computer Science, Iowa State University, TR #97-19, September 1997. available from http://www.cs.iastate.edu/~leavens/main.html Drs. Leavens and Baker have developed a notation (JML) that supports these concepts and uses the normal syntax of Java expressions. We hope to use this notation in our specification of Java interfaces and classes but would like corresponding support for these concepts in OCL so there is a natural progression (mapping) from OCL assertions appearing in analysis and design model to JML assertions (when the target language is Java). Also (even though it is possible to define this by referencing the meta model) I would like to see OCL adopt a short hand for the expression necessary to specify that a new object was created by an operation. submit: Submit Issue Report