Sparx Systems Forum

Enterprise Architect => Automation Interface, Add-Ins and Tools => Topic started by: Mesple on September 25, 2018, 03:16:19 am

Title: MDG Technology : Quicklink examples?
Post by: Mesple on September 25, 2018, 03:16:19 am
Hi all,
I'd like to manage quicklinks in my MDG and I'm looking for examples.
It could be useful to illustrate the help web pages.
Thanks a lot!
Olivier
Title: Re: MDG Technology : Quicklink examples?
Post by: Geert Bellekens on September 25, 2018, 03:53:54 pm
Olivier,

Don't invest too much in the "old" quicklink CSV format as it has been deprecated in versioin 14.
You can now control the quicklink using some kind of meta modelling.

Geert
Title: Re: MDG Technology : Quicklink examples?
Post by: Mesple on September 25, 2018, 05:11:53 pm
ok Geerts, where can I find information on the new way to define quicklinks in V14?
Title: Re: MDG Technology : Quicklink examples?
Post by: Arshad on September 25, 2018, 08:26:28 pm
Hi all,
I'd like to manage quicklinks in my MDG and I'm looking for examples.
It could be useful to illustrate the help web pages.
Thanks a lot!
Olivier


Hi Mesple

If you had a meta model\blue print defined in your model  then you can follow this tutorial
(Quick Link Definition Simplified) (https://www.sparxsystems.in/blogs/quick-link-definition-simplified/) for generating an automated Quick Link .



HTH
Arshad
Title: Re: MDG Technology : Quicklink examples?
Post by: Geert Bellekens on September 25, 2018, 08:53:29 pm
ok Geerts, where can I find information on the new way to define quicklinks in V14?
In the manual: https://www.sparxsystems.com/enterprise_architect_user_guide/14.0/modeling_tools/metamodelconstraints.html (https://www.sparxsystems.com/enterprise_architect_user_guide/14.0/modeling_tools/metamodelconstraints.html)

Geert
Title: Re: MDG Technology : Quicklink examples?
Post by: Eve on September 26, 2018, 08:37:42 am
If you had a meta model\blue print defined in your model  then you can follow this tutorial
(Quick Link Definition Simplified) (https://www.sparxsystems.in/blogs/quick-link-definition-simplified/) for generating an automated Quick Link .
I can't imagine that being easier to manage than using the spreadsheet. You end up with one connector on the one diagram for every row in your target file. In most cases I've seen, that's hundreds of entries. Best case, that I can think of is that you organize the diagram with each source element having a list of target elements with the corresponding connector types. But that's just as achievable using the spreadsheet, except it's easier to sort on different columns etc.

I'm sorry, but it would be easier to manage my quicklinks by directly editing a CSV file in a text editor.
Title: Re: MDG Technology : Quicklink examples?
Post by: Mesple on September 28, 2018, 09:49:18 pm
Thanks a lot!
Olivier
Title: Re: MDG Technology : Quicklink examples?
Post by: adepreter on October 06, 2018, 07:58:15 pm
The architecture discipline requires frequent and dynamic updates to the metamodel.
Therefore having to rebuild and redeploy the mdg for each little change (as currently implemented by Sparx) is inadequate.

Therefore we are using a language metamodel, stored in the production repository, as language constraints.
When Sparx starts, an addin loads this metamodel and dynamically builds the language constraints in memory. These prevent users from creating the wrong connectors.
The exact same language metamodel is also used as documentation.
http://www.labnaf.one/guidance/index.html?guid=688CA55E-E24A-4561-B272-775DDAA01A08

When the metamodel is changed in the repository, the validation rules are changed instantly.

Quicklinks are also generated automatically from this metamodel.
The same validation rules can also be loaded from the quicklinks.
Title: Re: MDG Technology : Quicklink examples?
Post by: qwerty on October 06, 2018, 09:03:02 pm
I did something similar on a light weight basis. The problem with these meta-models is that they tend to become dinosaurs quite easily because they are very complex. You need a (large) team to keep that model alive and you need extra training for all users since they have to stick to the rules modeled therein. I'm more a fan of smaller MDGs developed for just one domain. They are harder to change, but that beats you to do it right (or less sloppy) the next time. It does not help much if you have a tool to change and then check the semantics of a change if you have lots of changes.

q.
Title: Re: MDG Technology : Quicklink examples?
Post by: Glassboy on October 08, 2018, 07:46:03 am
The architecture discipline requires frequent and dynamic updates to the metamodel.
Therefore having to rebuild and redeploy the mdg for each little change (as currently implemented by Sparx) is inadequate.

If your meta-model is changing that often it's either not a meta-model or something is going badly wrong in your architecture team.