|Re: Papyrus and FUML [message #956787 is a reply to message #953431]
||Wed, 24 October 2012 20:10
| Arnaud Cuccuru
Registered: April 2010
Sorry for the delay.
There is actually a Papyrus plug-in providing a straightforward, sequential implementation of the fUML execution model. This is available here: http://dev.eclipse.org/svnroot/modeling/org.eclipse.mdt.papyrus/branches/0.9.X/extraplugins/moka/
Please note that these plug-ins are not part of the build yet. So, to use it, you have to download the three plug-ins, and install them manually (or put them in your development workspace, and laucnh a new run time).
Currently, integration with Papyrus is limited. For example, the class and activity diagrams are not constrained to remain in the fUML subset. It's up to you to produce models that comply with the fUML subset.
To test the execution, just write an activity without parameters (intended to act as a kind of Main), select it in the model explorer, right click, and press execute. Some debug messages show appear in the console, tracing what happened during the execution of the model by the fUML engine.
Note that currently, the fUML library (which defines basic arithmic, comparison, etc. operators) is not a "registered" library. To use it, you have to import the registered Alf library, which itself has an import to the fUML library. Please note that all function behaviors defined in the fUML library are not yet implemented (cf. oep.moka.fuml.standardlibrary for details)
Connection with Alf (i.e., generation of fUML activities from Alf statements) is an ongoing work, not available on Papyrus SVN yet. For your interest, the 0.9.X branch of the SVN also contains an update Alf editor for operations, which is not yet integrated in the build, but corrects a number of bugs that were related to the Extra plugin version.
The precise roadmap/agenda behind all this "executable UML" stuff still needs to be clarified. I can just confirm that we are active to provide a better integration.
Powered by FUDForum
. Page generated in 0.02160 seconds