The BDD you can somehow regard as a structured bill of material, it focuses on what a thing consist of.

IBD focuses on how the different things within a thing interact with each other.

Let’s say you have a block representing a special kind of wheel. This wheel will be part of a car type A typically with multiplicity 4. Further on this wheel could be part of many other car types.

If you want to express how wheels interact e.g. with the power train, you need to differentiate the four wheels somehow like left-font, right-rear,…, and these are the “instances” or more correct in SysML "the right-front wheel is a property of car type A with the role to be the right front wheel of type "Wheel".

If you would only use BDD you would need to duplicate the "Wheel Types" (Blocks) as many times as wheels you have. The wheel block could even be a complex thing (wheel rim, tire, valve,…), you would need to double as well. In other words BDD and IBD is all about OO in SysML.

I'm not sure, what you mean with Context. Is it context menu? If it is, I can't imagine, where the About option would appear. Our add-in is a window for editing properties of tables. It replaces standard EA window, so it has no special option in the context menu, because it responds to standard Properties option or simply double-click.

I usually work with ArchiMate, but the last 6 month switch to UAF, which can be implemented with SysML.

The main difference, for me, between ArchiMate and SysML is the idea with definition and usage which SysML implements. Although I get the concept and know how to use it, I don't fully get the purpose of this.

Great, now I know the main components of the car. If I have a look in the traceability window I see the relations to these subsystems.

What I don't get, is WHY do I create part properties/instances of these blocks where they are used. Have a look at the internal block diagram:

Why not use the blocks from the previous diagram? If I would like to see the relations I have to find the instance of the block and then look at the relations, instead of just going straight to the block definition. Some relations, like reference associations are documented in the block diagram.

All the examples I looked at, also read Delligatti's SysML Distilled, use this pattern:

If the instance have the same name as the block, why not just use the block? I get the obvious examples like:

Block: Volvo XC90Instance: myVolvoXC90:VolvoXC90

I think what is confusing me a bit if the go down yet another level, have a look at the block diagram for the PowerSubsystem:

Lets say that the ElectricalPowerController also is used in the LigthningSubsystem (see fig 16). In the IBD:s, do I re-use the instance of ElectricalPowerController, epc, or do I create a new, epc2? If I re-use the instance, why not use the block definition?

I guess what I want is an explanation motivating me to create part properties/instances of blocks to use in IBD:s instead of mindlessly create and use them. And also when I should re-use/create new these.

Compared to ArchiMate, where I create an element and only use that element. Why is instances better?