I received even more feedback about the IBD using object instances rather than properties. Both are legal on an IBD, but object instances are a poorer choice because they don't express the context inherent in a property. The context is the block (ex, "Carl's Bass Effects") and it can be applied to part properties, shared properties, and reference properties.
The corrected IBD is here. I retained the original IBD, but marked it as obsolete in this post.
START ORIGINAL POST
In the previous post, I created a Block Definition Diagram of my bass guitar effects. A reader suggested I push the details of that particular BDD onto an IBD. The revised BDD appears at the bottom of the post; this is the continuation of the effort which introduces another SysML diagram type.
A SysML Internal Block Diagram is used to show the internal structure of a block. In Sparx Systems EA, an IBD is associated with the block that it is describing. Starting with a block "Carl's Bass Effects" on a BDD, right click and select New Diagram > Internal Block Diagram.
|Adding a New Diagram to a Block|
To add blocks to the IBD, drag from the Project Explorer. When prompted about how you'd like the block represented, select "Instance (Object)" so that any ports are displayed with the block. Use "All" for the Structural Elements which includes the Ports.
|Select Instance(Object) to Display Ports with the IBD Blocks|
|Internal Details Relating Blocks of Bass Effects: Shouldn't Use Object Instances|
Many thanks to Stephan for the suggestion to divide these up.
Instance usage from the spec.
|IBD Example from SysML !.3|