Book a Demo

Author Topic: QuickLinker "<none>" new link type  (Read 5428 times)

Paolo F Cantoni

  • EA Guru
  • *****
  • Posts: 8617
  • Karma: +257/-129
  • Inconsistently correct systems DON'T EXIST!
    • View Profile
QuickLinker "<none>" new link type
« on: November 03, 2015, 11:29:18 am »
The ArchiMate QuickLinker specifications includes the value "<none>" for the New Link Type column.  Anyone know what it means?  Are there any other Extrinsic Values that could be useful?

Paolo
Inconsistently correct systems DON'T EXIST!
... Therefore, aim for consistency; in the expectation of achieving correctness....
-Semantica-
Helsinki Principle Rules!

KP

  • EA Administrator
  • EA Expert
  • *****
  • Posts: 2919
  • Karma: +54/-3
    • View Profile
Re: QuickLinker "<none>" new link type
« Reply #1 on: November 04, 2015, 09:26:49 am »
It's how you tell the quicklinker not to inherit the default menu when there isn't an overriding menu. (You would normally put TRUE in the "Exclusive to stereotype" column, but if there are no possible connections between stereotypes then you don't have that option.)
The Sparx Team
[email protected]

Paolo F Cantoni

  • EA Guru
  • *****
  • Posts: 8617
  • Karma: +257/-129
  • Inconsistently correct systems DON'T EXIST!
    • View Profile
Re: QuickLinker "<none>" new link
« Reply #2 on: November 04, 2015, 11:06:15 am »
Quote
It's how you tell the quicklinker not to inherit the default menu when there isn't an overriding menu. (You would normally put TRUE in the "Exclusive to stereotype" column, but if there are no possible connections between stereotypes then you don't have that option.)
Thanks KP,

Are there any other "specials".  For example, I think it would be good to be able to specify that :
 Class , stereotype: <any>, Class, Stereotype: <Same>, Aggregation, , Aggregates

To imply you can aggregate  stereotype tot he same stereotype.

Paolo
« Last Edit: November 04, 2015, 11:06:35 am by PaoloFCantoni »
Inconsistently correct systems DON'T EXIST!
... Therefore, aim for consistency; in the expectation of achieving correctness....
-Semantica-
Helsinki Principle Rules!

qwerty

  • EA Guru
  • *****
  • Posts: 13584
  • Karma: +396/-301
  • I'm no guru at all
    • View Profile
Re: QuickLinker "<none>" new link type
« Reply #3 on: November 04, 2015, 11:31:12 am »
Oh please no. I'm already struggling with describing the current capabilities. It would be so much easier if that were programmable conditions in a common language rather than this crude table format.

q.

KP

  • EA Administrator
  • EA Expert
  • *****
  • Posts: 2919
  • Karma: +54/-3
    • View Profile
Re: QuickLinker "<none>" new link
« Reply #4 on: November 04, 2015, 11:33:03 am »
We don't have that specific example, but we have introduced a few new ones with EA 12.1 Beta, e.g. specify the name or classifier of the (unstereotyped) source and/or target element. They use the previously unused "Complexity" field and are documented in the help.
« Last Edit: November 04, 2015, 02:31:28 pm by KP »
The Sparx Team
[email protected]

Paolo F Cantoni

  • EA Guru
  • *****
  • Posts: 8617
  • Karma: +257/-129
  • Inconsistently correct systems DON'T EXIST!
    • View Profile
Re: QuickLinker "<none>" new link
« Reply #5 on: November 04, 2015, 03:10:41 pm »
Quote
We don't have that specific example, but we have introduced a few new ones with EA 12.1 Beta, e.g. specify the name or classifier of the (unstereotyped) source and/or target element. They use the previously unused "Complexity" field and are documented in the help.
Thanks,

I'll check out the help.
Inconsistently correct systems DON'T EXIST!
... Therefore, aim for consistency; in the expectation of achieving correctness....
-Semantica-
Helsinki Principle Rules!

Paolo F Cantoni

  • EA Guru
  • *****
  • Posts: 8617
  • Karma: +257/-129
  • Inconsistently correct systems DON'T EXIST!
    • View Profile
Re: QuickLinker "<none>" new link type
« Reply #6 on: November 04, 2015, 03:11:51 pm »
Quote
Oh please no. I'm already struggling with describing the current capabilities. It would be so much easier if that were programmable conditions in a common language rather than this crude table format.

q.
Indeed, but any improvement is better than no improvement...

Paolo
Inconsistently correct systems DON'T EXIST!
... Therefore, aim for consistency; in the expectation of achieving correctness....
-Semantica-
Helsinki Principle Rules!

Paolo F Cantoni

  • EA Guru
  • *****
  • Posts: 8617
  • Karma: +257/-129
  • Inconsistently correct systems DON'T EXIST!
    • View Profile
Re: QuickLinker "<none>" new link
« Reply #7 on: November 04, 2015, 04:17:51 pm »
Quote
Quote
We don't have that specific example, but we have introduced a few new ones with EA 12.1 Beta, e.g. specify the name or classifier of the (unstereotyped) source and/or target element. They use the previously unused "Complexity" field and are documented in the help.
Thanks,

I'll check out the help.
Will the examples be extended to show the use of the new complexity column?  I see what the definition says, but I'm not sure I can visualise the outcomes.

Paolo
Inconsistently correct systems DON'T EXIST!
... Therefore, aim for consistency; in the expectation of achieving correctness....
-Semantica-
Helsinki Principle Rules!