SysML: maintaining BDD and IBD diagrams

[Dave.B]

Blocks that are related to a parent block with a composite aggregate relationship (black diamond) on a block defintion diagram (BDD) are available as parts on that block's internal block diagram (IBD). Moreover the role names allocated on the relationship in the BDD are the part names in the IBD.

So far, I have not found a straightforward way of moving from a block's BDD to it's IBD (or even vice versa), such that the aggregated blocks on the BDD become parts on the IBD with the role names being the linked to the part names. (And cardinality should be respected also.)

About the only method that I have found to move from the BDD to the IBD is to add each aggregate block as a part and manually name it after the BDD's role name. Not only is this very tedious, but it would also seem that the model's integrity is not being enforced since part names and role names can be completely different.

Any suggestions? Is there a better way? Is a script available to at least add the aggregate blocks as parts?

Thanks
Dave B.

[JoFo]

I'm fairly new to EA and have used both Artisan Studio and IBM Rhapsody amongst others. These tools maintain coherency between the BDD and IBD and I'm finding EA's support for SysML very frustrating.

Has anyone found a way around this significant limitation?

[Guillaume]

Hi

I also have the same issue
- I defined the BDD with my blocks, aggregates and flowPorts
- I created the IBD for one of the blocks (SysML internal block)
 * I copied my block and flowports to the diagram
 * Within this class, I added my parts (instances of the other blocks to use)l like Dave said I don't have the flow ports available and have to manually add them.

I found a sample of SysML projet showing that this is indeed the case i.e. the flow ports of parts aren't automatically available

I tried the Open Source TopCased SysML tool yesterday and this feature is supported.

SysML plug in should support this as well, especially as this is a chargeable add'on

thanks