sysML-Displaying supertype Block Values in subtype

[joeT]

I am new to the world of sysML and am struggling with some concepts that seem to work well in UML however don't seem to relate to sysML.

I would like to create a Block Diagram in Enterprise Architect using sysML 1.3 with a parent block to define the properties of the family of block (or class) and then create child blocks for each specific use of that block, in which I want to display and override the inherited property values in a fashion similar to what I can do in UML with attributes.

For example I could create an asynchronous channel block with baud-rate properties, stop-bits, bits per word etc as a parent and define two child blocks with one channel specified at 1250000 bps and another at 512000 bps.

In terms of a process, I would like to perform the following generalization and be able to display the inherited parent values with the specific default values as applied to the child block, i.e.:
1) create a block - Block1, with a property - Prop1, and type it with a valueType such as bps.
2) create another block - Block2 and add a generalization relationship to Block1.
3) create another block - Block3 and add a generalization relationship to Block1.
4) modify the default value of Block2's inherited property - Prop1 as 1250000 bps.
5) modify the default value of Block3's inherited property - Prop1 as 512000 bps.

When viewing the child blocks, Block2 and Block3, I would like to be able to see the block on a diagram with Prop1 showing the values specific to each block.

Is this possible in Enterprise Architect or am I missing something that is a fundamental difference between sysML and UML regarding the parent child relationship.

Thankyou for you help in understanding sysML

Regards,
JoeT

[Gary]

Joe

What you want to do is often done in the context of parametric diagrams for performing trade-offs. Try having a read around that area.

What you are doing is perfectly valid although you do not have to use generalization to achieve it. I have included an excerpt from the SysML spec that shows the idea.

SysML also allows each usage to define context-specific values and constraints associated with the individual
usage, such as 25 psi for the front tires and 30 psi for the rear tires

So properties of a block can be typed by another block. If your asynchronous channel block is a property of a communications block you can type the property with the asynchronous block and assign values at that time, or keep the value unset and use a parametric trade off to find the value that works for the system design.

Gary