Problems with SysML

[Paul Ebert]

I'm having some problems with creating SysML models.

First, I do not seem to be able to add values to blocks.  I can add attributes and give them the stereotype "values", but that does not seem to be the correct way to do it (or is it?).  There just doesn't seem to be a values compartment and/or means of entering them.

Second, I'm unable to add or modify dimensions or units of valuetypes.  When I try to do so, the 'Set Element Classifier' dialog appears, but it always lists <none> as the available classifiers, regardless of the namespace.  At first I thought I was not using packages correctly, but the same thing happens with the example models.

Can someone please help me with these issues?

Thanks.

[«Midnight»]

What about setting the Run State? [See the EA help index for this entry.] I don't remember if that is how the SysML add-in sets these up.

[Paul Ebert]

Thanks for the reply.

Are you suggesting setting the run-time state to deal with the block values problem?  I received a reply from support saying block values are currently not implemented - they caused database performance issues.  So, I guess I'll add them as stereotyped attributes for now.

I've figured out how to add parts to the blocks, so that's a step in the right direction.  I still cannot do anything with valueTypes, nor can I add items to a flow spec.  Both of these are pretty fundamental to what I need to do.

I hope I haven't purchased a tool that's not far enough along to be useful.

[connector]

Ca you share how you add parts to blocks?

[Paul Ebert]

To add parts to a block, create an internal block diagram for the block.  Then, add properties to the diagram.  Give the properties the stereotype "BlockProperty".  It will then appear as a part in the block.

You will need to save the internal block diagram and, possibly, refresh the block definition diagram to have the new part(s) displayed.