Where are quicklinks of an MDG stored in the database?

[Eve]

Define Metamodel Constraints

The relationships you see in the ArchiMate technology are (mostly) the ones that are defined in the metamodel diagrams in the specification. Using this method allows you to define both quicklinkers and model validation using exactly the same information.

[Geert Bellekens]

Hi,

In v14 they made a change in the way the quicklinks are populated.
Before v14 you had to fill in a massive CSV file with every possible combination.
Now the quicklinks are apparently derived from the UML profile in some way.

I still have to dive into it myself but I would guess that this probably how the new quicklink works.

Geert

[pieter.steyn]

Yep.

Got this response from support:
The ArchiMate 3 MDG technology in EA 14 is using the metamodel functionality introduced in EA 14 to define quicklinks.
http://www.sparxsystems.com/enterprise_architect_user_guide/14.0/modeling_tools/metamodelconstraints.html

This method is a little less flexible than defining quicklinker rules explicitly, but allows you to model the relationships instead, and is much simpler when you have a set of stereotypes with inheritance between them. It also has the advantage that the rules you define can also be used by model validation.

Thanks!

[matthew.james]

The relationships you see in the ArchiMate technology are (mostly) the ones that are defined in the metamodel diagrams in the specification. Using this method allows you to define both quicklinkers and model validation using exactly the same information.

So the Archimate MDG has been built using metamodel constraints, which drive the quicklinks ?
What about the 'model validation' mentioned above?  Is there a way I can validate a package for compliance to the MDG (ie Archimate) as opposed to base UML validation (using 'Validate Current Package')?

I started a post on this a few days ago if you'd rather use that to respond:
http://www.sparxsystems.com/forums/smf/index.php?topic=40041.0

[Geert Bellekens]

The relationships you see in the ArchiMate technology are (mostly) the ones that are defined in the metamodel diagrams in the specification. Using this method allows you to define both quicklinkers and model validation using exactly the same information.

So the Archimate MDG has been built using metamodel constraints, which drive the quicklinks ?
What about the 'model validation' mentioned above?  Is there a way I can validate a package for compliance to the MDG (ie Archimate) as opposed to base UML validation (using 'Validate Current Package')?

I started a post on this a few days ago if you'd rather use that to respond:
http://www.sparxsystems.com/forums/smf/index.php?topic=40041.0

I think Simon is talking about the strict connector syntax option here.

Geert

[matthew.james]

I think Simon is talking about the strict connector syntax option here.

Leave me with my hopes and dreams for a little bit longer ...
It feels like the framework is there for 'proper' model validation and that it should be possible. Maybe ?

[Eve]

I think Simon is talking about the strict connector syntax option here.

The same rules that drive Strict Connector Syntax are checked during model validation. So it's both.

Having said that, I know that the rules defined for ArchiMate haven't been refined as much as I would like them to be.

[matthew.james]

The same rules that drive Strict Connector Syntax are checked during model validation. So it's both.

So ... is there a way to do a package level model validation against a UML profile (as opposed the base UML validation which the "Validate Current Package" does) ? Specifically for Archimate ?
If so, how does one do that ... ?

[Eve]

What build of EA are you using?

Build 1422 validation reports validation errors in the same situations as strict connector syntax prevents.

[matthew.james]

What build of EA are you using?

Build 1422 validation reports validation errors in the same situations as strict connector syntax prevents.

Build 1420 ...
Strict connector syntax is working (mostly) as expected (there are some scenarios where I think it is valid Archimate but Sparx is saying no, need to dig into those bit further)

So - if I update to 1422 I get something different with validation ?  Can you describe / explain how it works ? (is it something I control through "Configure Validation Rules" ?)

Thanks