Sparx Systems Forum
Enterprise Architect => Bugs and Issues => Topic started by: Guillaume on September 06, 2016, 08:06:29 pm
-
Hi,
I defined a custom SysML value type in a UML profile for a client (extends UML data type, generalizes SysML ValueType).
Having created flow properties on a block, I cannot set my Value Type as the property type based on the filters that are applied by EA.
A workaround is possible but this looks like a bug.
thanks
-
Hi Guillaume,
I know it is quite old but the behavior is back in EA 15.2.
We also use our own stereotypes "Flow" in our MBSE toolbox to highlight the semantic and it we were able to choose with EA13.5 'til 15.1 any classifier type.
EA filter was
Types : Classifiers such as Classes, Actors, Activities etc.
Now SPARX changed the filter to
Types : 'Class','DataType','Signal'
Stereotypes : SysML1.4::block,SysML1.4::ValueType
Now we are not able to select our own stereotypes which are even a generalization of SysML1.4::Block.
The workaround for us is to use drag and drop from the project browser on the block and select
Drop as: SysML1.4::FlowProperty (Part)
However to my mind Sparx interpreted the SysML1.5
Constraints
[1]A FlowProperty shall be typed by a ValueType, Block, or Signal.
too strictly as the stereotype Block is in fact an extension of UML4SysML::Class and FlowProperty is an extension of UML4SysML::Property which binds classifies.
That would avoid to use own toolboxes for SysML, and I doubt that shall be the intention of SysML1.5!
Roman
-
I found out another solutions (currently EA 15.2.1557) which leads to same definition as with drag and drop mentioned before.
Instead of using the Property->Type in tab Properties
you can select the Part->Type in tab Element
then the filter is open for standard Property types again ;) :
Types : 'Port','Activity','Class','DataType','Interaction'...
Stereotypes : ...
If you want to restrict the filter for Part->Type regarding your MDG stereotypes, you need to redefine SysML1.4::FlowProperty with FlowProperty and add metaconstraints (umlRole=classifier) to your own stereotypes. [ref. to EA MDG Help chapter "Redefine Stereotypes in Another Profile","Define Metamodel Constraints"]
Maybe with future SysML the change the definition again and as long as SPARX keep the existing workarounds, I am fine with that.