Messages

1

General Board / Re: Block Definition Diagram - Aggregation

« on: March 11, 2015, 04:15:23 am »

Thanks for the prompt reply, and I agree for a part composision this is expected! So then one last question to clarify...

I open a new sys-eng Model with 'New -> SysML -> systems engineering model' then navigate to the 'systems engineering model -> Library -> Blocks -> Blocks' Diagram.

I then want to add another block to the environment, so if I drop Noise and Weather into the bdd diagram they show with a black diamond (expected), if I drop another block and link it by part association to Environment (using the toolbox) EA will add a property to Environment (which is not present for Noise or Weather) also expected as per the previous post.

So therefore, to create the model in the template that links the three blocks Environment, Noise and Weather from scratch I have no choice but to delete the part properties after EA creates them for me?

Hopefully this came out understandable, if not thanks for your concentration.

Chris

2

General Board / Block Definition Diagram - Aggregation

« on: March 11, 2015, 02:37:04 am »

Hi Folks,

Hopefully a simple question, but I've got confused and need another pair of eyes to look at the problem...

I'm constructing a block definition diagram and want to define block Aggrigation / black diamond notation (e.g. as Noise and Weather is to Environment in the Systems Engineering Model template)

I do this by making two blocks and connecting them with the black diamond icon in the toolbox. For some reason this is creating the link and an additional part property in the parent as well which i then delete... what am i doing wrong?

Thanks,
Chris S

3

Automation Interface, Add-Ins and Tools / Documentation Generation Advice

« on: January 15, 2015, 04:08:54 am »

Hi Folks,

I've been developing a sysml model within EA and am looking into how to export to a 'text' format. I have spent some time exploring RTF templates but can not implement what I need. Anyone know where I can find some more / real world examples, and / or how to implement the following pseudo code within a template fragment:

For all <<requirement>>
 if <<requirement>> contains <<requirements diagram>>
    Display requirement info
    Display requirements diagram
    Display info of child requirements
  end
end