Re-use existing MDG diagrams within a custom MDG?

[peterc]

I am creating a custom MDG, with some custom diagrams.

I would like to include some SysML diagrams in my custom MDG - I don't need to customise them (which the user guide implies is not possible anyway as only built-in diagrams can be extended). Is it possible to do this?
I realise that I might need to add a customisation (I found that was the only way to get a base diagram to be included - my customisation was simply to override the description with the same words as the original!).

I'm trying to make it easy for the user, so that they only need to select the diagram types that I have selected as relevant rather than sometimes selecting diagrams from my custom MDG Technology and sometimes selecting diagrams from the SysML Technology.

I note that it is possible to extend SysML elements (although I don't intend to do that) - I am unsure why I would want to extend SysML elements if I can't specify the SysML diagrams in a custom MDG, so possibly can somehow include the SysML diagram types.

[Geert Bellekens]

Good question, if it isn't possible then I would certainly send in a feature request.

Geert

[PeterHeintz]

Hi peterc,
I used SysML to derive new stereotypes, to create own diagrams using SysML toolboxes and to create own toolboxes but having SysML stuff in as well.
So it is possible.

Basically it works by putting in, strings somewhere (ok right place) with SysML1.4 prefix.

Examples:
To create a own requirement stereotype, I point my own stereotype by generalization to another stereotype I created, which I gave the name SysML1.4::requirement
To use e.g. in my own diagram type a SysML toolbox, I set the "toolbox" parameter to e.g. SysML1.4_Activity
And to use SysML stuff in my toolboxes I added e.g. an attribute called SysML1.4::Refine

[Geert Bellekens]

Hi peterc,
I used SysML to derive new stereotypes, to create own diagrams using SysML toolboxes and to create own toolboxes but having SysML stuff in as well.
So it is possible.

Do you think it works for diagram types as well? I wouldn't know how to do that.

Geert

[PeterHeintz]

Hi Geert,
what do you exactlly mean with that?

What I did for example is creating my own diagram type called "System Use Case".

As Extension Type I set "Use Case".
As Alias I set "SysML Use Case" (I do not remember if this has some relevance)
As Frame ID I set "uc"(to comply with SysML)
As Frame Format String I set "DGMID# [#DGMOWNERTYPE#] #DGMOWNERNAME# [#DGMNAME#]" (to comply with SysML)
As Toolbox Profile I set "SysML1.4_UseCase"

All the rest I left empty.

What I have now is a diagram type which in fact is a SysML use case diagram but called "System Use Case".

Is that what you are looing for?

[Geert Bellekens]

I wouldn't be 100% the same as a regular SysML diagram, but I guess it would probably be close enough as the main purpose for a diagram type is to link it to a toolbox.

Geert

[peterc]

Thanks Peter

I was hoping to be able to use the SysML diagrams as-is (i.e. not have to redefine all the settings), but your parameters give me enough to re-create the diagram and pickup the toolbox so that is great thanks. Importantly that would then pickup any fixes put in by Sparx (as well as being less customisation).

The Alias becomes the Type on the diagram properties (which otherwise defaults to the base diagram) so probably is important in the long term for making diagrams as close as possible to the standard SysML.

At least I can create diagrams and re-use the SysML toolboxes, which is probably most important.

Actual SysML diagrams have the diagram frame on-screen (and a new option on the right-click menu "Hide Diagram Frame"), completely separate from the options to include the diagram frame on published/printed images. I'm not overly bothered about having the frame on screen, but wondered how that is replicated?

[KP]

In EA14, you can use diagram views to modify SysML diagram types without losing their associated SysML functionality.

http://www.sparxsystems.com/enterprise_architect_user_guide/14.0/modeling_tools/custommetamodelview.html

[peterc]

KP - I've tried replicating the custom metamodel, but am not getting very far. I think where the example page shows SysML1.5 that it should be SysML1.4 to start with, but even then it doesn't work. Is there an example model that could be downloaded?

[KP]

I notice there's nothing in the Example Model. I don't know if Sparx Support have anything more substantial than what's in the help, but if you get in touch then the least they can do is record a feature request for additions to the Example Model.