Author Topic: Satisfy Dependency Stereotype behaviour  (Read 759 times)

Polymorph

  • EA User
  • **
  • Posts: 120
  • Karma: +4/-0
    • View Profile
Satisfy Dependency Stereotype behaviour
« on: January 16, 2017, 07:36:17 pm »
When I create a satisfy relationship between a block (as the source) and requirement (as the target), using the SysML 1.3 toolbox, EA applies the following stereotype: «sysML1.3::satisfy»

This seems to be the only relationship from the Requirements Toolbox that has this behaviour. All other relationships are rendered with they stereotype name only (no mention of the version of SysML they are taken from. Does anyone know why this happens and how it can be turned off?

If I turn off the SysML 1.3 MDG and enable SysML 1.4 then the problem seems to disappear but I don't want to change to SysML 1.4 if I can avoid it as we are mid-way through a project.

Geert Bellekens

  • EA Guru
  • *****
  • Posts: 7742
  • Karma: +165/-21
  • Make EA work for YOU!
    • View Profile
    • Enterprise Architect Consultant and Value Added Reseller
Re: Satisfy Dependency Stereotype behaviour
« Reply #1 on: January 16, 2017, 08:07:10 pm »
have you checked the general list of stereotypes?
There might be a «satisfy» stereotype running in the wild, forcing EA to qualify the other stereotype

... or it might be a plain and simple bug  :-\

Geert

Polymorph

  • EA User
  • **
  • Posts: 120
  • Karma: +4/-0
    • View Profile
Re: Satisfy Dependency Stereotype behaviour
« Reply #2 on: January 16, 2017, 09:09:41 pm »
Geert - you are, as always, awesome 8)

There was a random stereotype defined for a note link. Once removed all is well.

Thanks - that was driving me mad!!!