| Transform to SysML Blocks [message #872514] |
Wed, 16 May 2012 05:02  |
 Matteo M.
Messages: 12
Registered: May 2012 |
Junior Member |
|
|
Dear all,
I'm trying to transform a model from a (extremely simple) custom meta-model to SysML, but I'm stuck on creating SysML Blocks.
By opening a simple Papyrus diagram containing a Block (the *.uml file), I noticed that, in its simpler form, a SysML Block is described by the two following entries:
1) a <packagedElement xmi:type="uml:Class" xmi:id="_pNiGwJnwEeG8hYBgdInPzQ" name="Block0">, inside
<uml:Model xmi:id="_tSXsoJnZEeG_XYf4QGS6LA" name="SysMLmodel"> ... </uml:Model>
2) a <Blocks:Block xmi:id="_pQ_qcJnwEeG8hYBgdInPzQ" base_Class="_pNiGwJnwEeG8hYBgdInPzQ"/>, outside of <uml:Model xmi:id="_tSXsoJnZEeG_XYf4QGS6LA" name="SysMLmodel"> ... </uml:Model> and inside <xmi:XMI xmi:version="2.1" ....> ... </xmi:XMI>
In defining my own QVTo transform I used the following target meta-models (I'm not allowed to post links, thus I changed them a little; I hope they are still clear):
modeltype UMLMM uses "http_://www.eclipse.org/uml2/3.0.0/UML";
modeltype BlocksMM uses "http_://www.eclipse.org/papyrus/0.7.0/SysML/Blocks";
and the following (simple) mapping (Component is defined in the source meta-model):
mapping Component::toBlock() : Class {
name := self.name;
}
Now, I'm able to transform components to UML Classes, but I can't stereotype them to SysML Blocks. I'm moving my first steps with QVTo and M2M transformations in general, so I'd really need to be pointed out to the right direction at this point. Any hints?
Thank you in advance,
--
Matteo
|
|
|
] 
Search
Help
Register
Login
Home
