Hi, For the first point, I agree with your propostion of syntaxe which is compliant with OCL specification. However Topcased auto-completion doesn't work with it. UML element are still not proposed.
For the last point, I note the answer. It explains why I cann't manage OCL and SysML. Thank for your fast response. Samuel -----Message d'origine----- De : [email protected] [mailto:[email protected]]de la part de [email protected] Envoyé : mercredi 21 octobre 2009 11:57 À : [email protected] Cc : [email protected] Objet : Re: [Topcased-users] OCL and SysML Hi, First point : in ocl_rule_sysml.ocl file, I would write something like : context Block inv r3 : self.ownedMember->size() inv r4 : self.name = 'Block1' context uml::Class inv r1 : self.ownedMember->size() inv r2 : self.name <> 'Block1' Concerning the last point you mentioned, actually it is really problematic since SysML extends the UML2 metamodel. The difficulty with SysML is that we are regularly switching between SysML Package and UML Package according to the rule, the context set and so on... If you don't manage to evaluate rules on SysML model elements, it is only because the package is set on UML package which is clearly a bug. So the notion of 'Block' becomes unknown in an UML context. I see the issue and will do my best to solve it for next releases. Regards, Sebastien [email protected] a écrit : > I'm also interested by this topic. > > Actually I was enable to check a SysML with OCL rules defined from SysML > metamodel (http://www.topcased.org/2.0/sysML). > > More precisely, I encounter the following problems : > * First, I have a strange behavior with OCL auto-completion. > As only SysML elements are directly accessible, I use the syntaxe > "package sysml::uml context UML_ELMT inv RULE_X : MY_RULE endpackage" in > order to accede at UML elements. Auto-completion works correctly but only on > one of my two boots. I explain me. I have a dual boot PC. When I editing OCL > rules with the first boot auto-completion is correct. UML elements are well > proposed. When I edit these same rules (same topcased.exe, same workspace...) > with the second boot auto-completion list only OCL operations and UML > elements are not listed. > Does anyone can explain this strange behavior ? > * Secondly, it seems there is a problem of parsing with the > syntaxe above. Even if auto-completion works, this not induces that rules can > be parsed (see ocl_rule_sysml.ocl <<ocl_rule_sysml.ocl>> ). > * Last, and may be the more problematic, even if rules concern > only SysML elements these rules cannot be evaluated through OCL evaluator nor > in an OCL check(see ocl_rule_sysml2.ocl <<ocl_rule2_sysml.ocl>> ). > > As I not encounter problems for validate UML models with OCL rules, I ask me > if in current version (Topcased 3.1.0) SysML models can be validated ? > Are these problems specific to me ? Is there a way to apply OCL rules on > SysML model ? > > Thanks for your help. > > > Samuel Rochet > > > > Samuel Rochet > On behalf of TEUCHOS > Subcontractor for Avionics and Simulation Products - EDYYAI > ' : +33 (5) 61 93 80 76 > 6 : +33 (5) 61 93 08 83 > * : [email protected] <mailto:[email protected]> > > > The information in this e-mail is confidential. The contents may not be > disclosed or used by anyone other than the addressee. Access to this e-mail > by anyone else is unauthorised. > If you are not the intended recipient, please notify Airbus immediately and > delete this e-mail. > Airbus cannot accept any responsibility for the accuracy or completeness of > this e-mail as it has been sent over public networks. If you have any > concerns over the content of this message or its Accuracy or Integrity, > please contact Airbus immediately. > All outgoing e-mails from Airbus are checked using regularly updated virus > scanning software but you should take whatever measures you deem to be > appropriate to ensure that this message and any attachments are virus free. > > > ------------------------------------------------------------------------ > > _______________________________________________ > Topcased-users mailing list > [email protected] > http://lists.gforge.enseeiht.fr/mailman/listinfo/topcased-users -- Sébastien GABEL MDA/MDE Engineer Département Systèmes d'Information Division Aéronautique Energie Industrie Communication & Systèmes ZAC de la Grande Plaine. Rue Brindejonc de Moulinais F-31506 Toulouse Cedex 5 +33 (0)5.61.39.46.16 _______________________________________________ Topcased-users mailing list [email protected] http://lists.gforge.enseeiht.fr/mailman/listinfo/topcased-users This mail has originated outside your organization, either from an external partner or the Global Internet. Keep this in mind if you answer this message. The information in this e-mail is confidential. The contents may not be disclosed or used by anyone other than the addressee. Access to this e-mail by anyone else is unauthorised. If you are not the intended recipient, please notify Airbus immediately and delete this e-mail. Airbus cannot accept any responsibility for the accuracy or completeness of this e-mail as it has been sent over public networks. If you have any concerns over the content of this message or its Accuracy or Integrity, please contact Airbus immediately. All outgoing e-mails from Airbus are checked using regularly updated virus scanning software but you should take whatever measures you deem to be appropriate to ensure that this message and any attachments are virus free. _______________________________________________ Topcased-users mailing list [email protected] http://lists.gforge.enseeiht.fr/mailman/listinfo/topcased-users
