Issue 11635: getAppliedStereotype OCL construct does not exist (updm-ftf) Source: No Magic, Inc. (Mr. Andrius Strazdauskas, andriuss(at)nomagic.com) Nature: Uncategorized Issue Severity: Summary: getAppliedStereotype OCL construct does not exist Resolution: Revised Text: Actions taken: October 30, 2007: received issue Discussion: End of Annotations:===== sues From: Andrius Strazdauskas This is issue # 11635 getAppliedStereotype OCL construct does not exist To: uPDM-ftf@omg.org Subject: Issue 11635 X-Mailer: Lotus Notes Release 7.0 HF277 June 21, 2006 From: Fred Mervine Date: Fri, 15 Feb 2008 09:33:00 -0800 X-MIMETrack: Serialize by Router on D03NM115/03/M/IBM(Release 8.0|August 02, 2007) at 02/15/2008 10:33:02, Serialize complete at 02/15/2008 10:33:02 When I prepared the Deferred ballot, I put the Issue 11635 on it. When I did the FrontMaterial ballot, I included 11635 because that is where the definition of the OCL operations should go. After Andrius' response to the definition of OCL statement, I did some more research.In e-mail correspondence, I was told that the OCL RTF is working on the issue of OCL being able to access stereotypes that are applied to model elements. UML 2 greatly enhanced the concept of stereotypes and profiles, so now OCL has to catch up. In the UML 2.1 spec, and in the OCL spec, itself, there are numerous references to the stereotype attribute: For example on pg 57 of the OCL Spec: An additional class operation is added to Parameter to return a Parameter. context Parameter::make(n : String, c : Classifier, k : ParameterDirectionKind) :Parameter post: result.name = n post: result.kind = k post: result.type = c post: result.stereotype.name = â..OclHelperâ.. Replacing the two OCL defintions with the following will provide definition for stereotype access in UPDM constraints using the convention in OCL and UML 2.1 specification. Also the operation "getAllAttributes" is not defined in OCL spec, but the operation allAttributes is. Since the clause, getAppliedStereotype(), is used throughout it is necessary to define its meaning, at least in the context of UPDM: Please replace this part of 11635 in the FrontMatter ballot .doc with the following: 4 Terms and Definitions 4.1 OCL Definition def: getAllAttributres():OrderedSet=self.allAttributes() def: getAppliedStereotype(qualifiedName:String):Stereotype = self.stereotype->select(name=qualifiedName) _______________________________ Fred Mervine Executive IT Architect Federal CTO Strategic Technology Team IBM Software Group Federal Phone: 707-468-8460 Cell: 707-816-6218 Date: Sat, 16 Feb 2008 15:18:14 +0200 From: Andrius Strazdauskas User-Agent: Thunderbird 2.0.0.9 (Windows/20071031) To: Fred Mervine Cc: uPDM-ftf@omg.org Subject: Re: Issue 11635 Fred, it is probably getAllAttributes instead of getAllAttributres. Andrius -- Andrius Strazdauskas Product Research and Development Manager No Magic Lithuanian Development Center Savanoriu pr. 363, LT 49425 Kaunas Phone: +370 37 705889 Fax: +370 37 320670 E-mail: andriuss@nomagic.com WWW: http://www.magicdraw.com -- MagicDraw - Architecture Made Simple Fred Mervine wrote: When I prepared the Deferred ballot, I put the Issue 11635 on it. When I did the FrontMaterial ballot, I included 11635 because that is where the definition of the OCL operations should go. After Andrius' response to the definition of OCL statement, I did some more research.In e-mail correspondence, I was told that the OCL RTF is working on the issue of OCL being able to access stereotypes that are applied to model elements. UML 2 greatly enhanced the concept of stereotypes and profiles, so now OCL has to catch up. In the UML 2.1 spec, and in the OCL spec, itself, there are numerous references to the stereotype attribute: For example on pg 57 of the OCL Spec: An additional class operation is added to Parameter to return a Parameter. context Parameter::make(n : String, c : Classifier, k : ParameterDirectionKind) :Parameter post: result.name = n post: result.kind = k post: result.type = c post: result.stereotype.name = .OclHelper. Replacing the two OCL defintions with the following will provide definition for stereotype access in UPDM constraints using the convention in OCL and UML 2.1 specification. Also the operation "getAllAttributes" is not defined in OCL spec, but the operation allAttributes is. Since the clause, getAppliedStereotype(), is used throughout it is necessary to define its meaning, at least in the context of UPDM: Please replace this part of 11635 in the FrontMatter ballot .doc with the following: 4 Terms and Definitions 4.1 OCL Definition def: getAllAttributres():OrderedSet=self.allAttributes() def: getAppliedStereotype(qualifiedName:String):Stereotype = self.stereotype->select(name=qualifiedName) _______________________________ Fred Mervine Executive IT Architect Federal CTO Strategic Technology Team IBM Software Group Federal Phone: 707-468-8460 Cell: 707-816-6218