Time-aware MDG Technology models

[Uffe]

Hi all,


So I'm thinking about trying time-aware models in my MDG Technology project, where I've got a couple of different technologies.

Let's say I've got a model that I've generated an MDG Technology from, and I clone that model.

If I now generate a profile from a package in my cloned model, going from the project browser and not the diagram, will the generated profile include the non-cloned elements?

Will the generated profile have the same "<Documentation id" attribute as the original?


/Uffe

[Uffe]

... No it won't, and no it won't.

/U

[Paolo F Cantoni]

... No it won't, and no it won't.

/U

Thanks for the "heads up".

As per my reply to the Import/Export topic, I suspect it's working correctly (at present).  I'll have a look (when I get a minute or two) to better understand your point.

Paolo

[Uffe]

Hi Paolo, and thanks for taking the time. I was hoping you would.

MDG Technology development is my use case for time-aware exports. Rather than using the diagram's context menu item to generate a profile (which isn't an XMI export, but still an export of sorts) I've always used the project browser's.¹

Being able to maintain TAM-style version-controlled MDG Technology models would be useful, but it would require that profile generation from cloned models included the non-cloned elements.

I should mention here that I haven't tested generating a profile from a TAM-cloned diagram, which might well work. My overall point is that the TAM functionality should be better integrated, and the generate-profile-from-browser function is an example of how it isn't.²


/Uffe

¹There was something that didn't use to work when you used the diagram's menu. I can't remember what now and I don't know if it's ever been resolved but the two menu items did not yield the same result (!) (!!) (!!!!) (why isn't there an emoji with its hair on end?) so I went with the one that worked for me.

²Also I'm pretty much making this up as I go.

[Geert Bellekens]

I use the generate from project browser as well, first and foremost because I don't want to depend on what is visible on a diagram for my exports.
I don't consider diagrams to be a "real" part of the model and don't like to depend on them for this type of stuff.

Geert

[Uffe]

Yes, and I agree with you, but there was also something that specifically didn't work when you exported from the diagram. Wish I could remember what.

OTOH, if you want to reuse a toolbox page between toolbox profiles you've got to export from the diagram. Unless they've done something with that in recent versions?

/Uffe

[Geert Bellekens]

OTOH, if you want to reuse a toolbox page between toolbox profiles you've got to export from the diagram. Unless they've done something with that in recent versions?

/Uffe

I don't do that anyway, so that is not really an issue for me.
I guess I would even prefer to duplicate the toolbox page over using diagrams.

Geert