Hello Vincent,
regarding your first question, I have used Rhapsody in the past (if I remember
correctly up to version 7.5). In Rhapsody, it was no problem to assign values
to the properties in the parts. Translated to Topcased, when you create a part
you would be able to expand it in the outline and would see all properties that
are defined in the block typing that part, and would enter the values in the
parts, not in the block.
I think that besides from Rhapsody, other SysML editors are able to do this as
well. If I look e.g. at the models created by Tim Weilkiens in the telescope
project, it seems that he is able to do the per-instance value assignment as
well. He is using MagicDraw (refer e.g. to the "Cookbook for MBSE with SysML"
Figure 52 "Assembling the parts to a system"). The Cookbook can be found by
accessing the following link: http://mbse.gfse.de/documents/Cookbook.pdf . But
this is just an assumption, since I have not used the tool myself.
The example I attached to my posting to the topcased list shows that it is
possible to show a property in a part, and the example shows strings but we can
use any other type, but still we have the problem with the instance-specific
values.
Best regards
Rodrigo
________________________________
Hello,
Well, the thing I manage to do at present (without extending Topcased/SysML)
is the following, but that’s not really great :
Consider Block1.
Consider Block2 with Property p : Real
Consider an IBD for Block1 : with b : Block2 as a part of Block1.
In the Model Outline, right-click on Block1/b and select DefaultValue/Literal
String
And place a char string : “{ p = 23.5 }”.
Then, these values appear in the part “b” in internal block diagram.
The trouble is that there is absolutely no control on the names used for
properties in the char string, also no control on the string format.
I have also tried “Instance Value” and connect that to Instance Specification,
but that’s not really better.
Still, this allows to place the information on the properties values in the
model, and in the diagram. But that’s not associated to the subbox for “p”
property.
But in the end, I’m still unsure about how the model should really look in the
Outline to enable realize a diagram as we are wishing.
Best,
Vincent.
Hello,
Thanks for your contact. I concur to the fact that such diagram having
properties with assigned values is a “must have”.
I’m not sure how far this will lead to properly implement these things in
Topcased.
Technically speaking : I’m not sure if the problem initially lies in the SysML
metamodel/ecore in Topcased. To be fair, I need to investigate the SysML spec
to see if there are discrepancies in that regard. Still, I can’t manage to
reproduce something having the semantics of “per-instance” values in the
Topcased model Outline.
I’m going to take a look at that this afternoon if I can and give you my
feelings.
Do you already have dealt with such diagrams in other SysML editors ? Just to
check / understand fully how it is supposed to be done.
I had downloaded Rhapsody/SysML eval version in the past, but the license has
expired.
Best,
Vincent._______________________________________________
Topcased-users mailing list
[email protected]
http://lists.gforge.enseeiht.fr/cgi-bin/mailman/listinfo/topcased-users
