SYSML Building Instances for a group of blocks and packages

[maselhappy]

Hi,

I try to design a network structure to build up a complete documentation and of cause a lot of graphics to know there you have to connect a device.

I use a hierarchy level which with 6 levels.
1.   Object
2.   Location
3.   Switchcabinet position (up to three different places)
4.   Cabinet
5.   Device (Up to 30 devices)
6.   Configuration (IP Address, Device ID, Routing, etc.) (Up to 10 configurations)

I have one design completely finished with all relevant configuration information as default.
What is the best way to build instances or children of the Object?
I don’t want to model the complete object 80 times again. In the children or instance I want only to change the Name on level 2 and the configuration based on level 6. The rest will be every time the same.
The devices are not defined inside the object – they are defined in another Package, where I organized parts which are used more than 2 times.
Inside the Object the devices will be children from the organized part of the model.

Br
Marcel

 

[qwerty]

I have only little experience with SysML. In UML I'd probably use Template Parameters from what I understand of your question.

q.

[PeterHeintz]

Hi Masehappy,
SysML talk more about roles rather than instances. There is a slight difference between roles and instances, but this might not matter in your case.
I am not really sure if I understand what you want to achieve, but probably I would have just 3-6 SysML Blocks (1 Object,  2 Location???, 3 Switch cabinet position???, 4 Cabinet, 5 Device, 6 Configuration???).
Further on I would have a SysML Block called Objects to contain as many objects you have as parts later.

All of those blocks I would add some properties like Object.name, Device.type, ….. Probably also what is marked above, would not be a SysML Block but properties of a SysML Block.

Instead of adding SysML properties (name, type, …) to the blocks, I would use UML attributes (just because of some missing EA features to overwrite and visualize property values).

After doing so, I would mount the stuff together (e.g. The Device block gets as many  part association as exist in a cabinet). Use role source name to differentiate the devices.
I your object structure is always the same, just do it once and make for each “object role” a part association from your "one and only Object Block" to the Objects Block. Again use role source names.
Finally use Structural Elements though all your elements and set the attribute values to your needs.

[maselhappy]

Hi all,

Thanks for your answers.  I think a picture is easier zu understand but this forum is not allow to provide pictures.

i think that my model is finished designed but now i want to provide the parameter diagrams for the 50 Objects.

i will upload a picture later that day.

Br
Marcel

[PeterHeintz]

Yes, a picture might help.

[maselhappy]

But a good question is, how to add a picture. i will try to provide a link if it is allowed.

[maselhappy]

All on the right will be childs from the left.

On the right part of location I want to build 50 to 100 instances which are a copy of the first part but with different configurations.

Be
Marcel

[PeterHeintz]

Hi maselhappy,
I do not see you image.

[qwerty]

And I can't see it, because it's too large xD

Peter, you are probably behind a firewall. Try to open the link of the picture in a separate window. Or when you're at home.

q.

[maselhappy]

I think I have solve the problem. I should not integrate all configuration parts into the model where I show the communication ways.

I think to build up the configuration details I should work with requirements or I try my best with template parameters.

Thanks

Marcel