SysML Blocks Stereotypes and Automation Interface

[Juan.Navas]

Hi there,

I am using EA 9 and the SysML extension. I will need to define stereotypes of SysML blocks, in order to define a profile and then a MDG Technology of my own.

However, SysML are not available as a meta-class in the profile diagram. Could this be due to blocks being considered as stereotypes of Class meta-class ? Wheter that is true or false, I've thinking about how I could define SysML blocks stereotypes and I could not find an answer...

Later I would like to use the Automation Interface to populate my model with stereotyped blocks, but then again, apparently I can only create Classes and then add a stereotype...

I hope somebody will be able to help me with that... Thanks.

[Stephan Roth]

Hi Juan,

you're right: SysML block is not realized by adding a meta-class to the UML meta model, because the whole SysML language is not realized using this kind of heavyweight extensions.

SysML is realized as a profile applied of a UML subset called "UML4SysML".

If you want to introduce your own stereotypes to extend SysML's block, you have to do this by using a generalization relationship.

At this point, EA is getting flawed, because you can not pick SysML block in the same way like you can pick UML meta classes from the Profile Toolbox to paste them into your profile diagram.

A workaround could be to create a stereotype named "block" as a point of origin to derive your own stereotypes using generalization.

Hope that helps,
Stephan

[Juan.Navas]

Thank you Stephan.

Your workaround would work, but please correct me if I am wrong : if I would like to create my own MDG Technology based on SysML 1.2 (for instance, be able to create "MyOwnBlock" blocks), I would need to do all the work EA fellas did : take the OMG SysML standard and create the SysML profile, then derive "MyOwnBlock"  from the "Block" stereotype I built...

That would be a shame as this profile has been already built (and commercially available).  I think the problem is that SysML is considered only as a plug-in in EA, and not as an universal language for systems development from which we would like to create domain specific languages.

If the EA SysML profile sources would be available, I could create a SysML-based MDG Technology  

[natvig]

I was just about to create an OOSEM-profile that extends the SysML language. (OOSEM is a MBSE method promoted by INCOSE.) Without access to the UML4SysML metamodel this can't be done? Very disappointing! I thing that the profile mechanism of UML/SysML is very important and that the means to extend the SysML language according to SysML specification should be provided by Sparx.