Book a Demo

Author Topic: SysML Requirements - <<copy>> dependency  (Read 3297 times)

Hans-Uwe Brackel

  • EA Novice
  • *
  • Posts: 2
  • Karma: +0/-0
    • View Profile
SysML Requirements - <<copy>> dependency
« on: September 28, 2012, 07:23:53 pm »
1st problem:
When dragging out a "copy" relationship  from a SysML 1.2 requirement to create a new req, the new requirement is csetup as a SysML 1.1 type

2nd problem:
according to the SysML spec, the ID and text of a requirement must not be changeable for the copy - just the name. EA seems to handle the "copy" referenced requirement just as a new one.

Regards, Hans-Uwe

qwerty

  • EA Guru
  • *****
  • Posts: 13584
  • Karma: +397/-301
  • I'm no guru at all
    • View Profile
Re: SysML Requirements - <<copy>> dependency
« Reply #1 on: September 28, 2012, 09:18:21 pm »
1. You should check the MDG settings whether you have both profiles (SysML1.1 and 1.2) active. That might cause the confusion.
2. This is an EA limitation. Each element created from the quick linker is created as new. You might raise a bug report if you think this is not SysML compliant. (I'm not a real expert here)

q.

Hans-Uwe Brackel

  • EA Novice
  • *
  • Posts: 2
  • Karma: +0/-0
    • View Profile
Re: SysML Requirements - <<copy>> dependency
« Reply #2 on: September 28, 2012, 09:36:54 pm »
querty: your suggestion on the first problem solved it. Since I disabled SysML 1.1 the new requirement is of type 1.2. Great hint. Thanks!

For the second it seems to be necessary to file a bug. Anybody from Sparx to comment on this?

Thanks and regards, Hans-Uwe

qwerty

  • EA Guru
  • *****
  • Posts: 13584
  • Karma: +397/-301
  • I'm no guru at all
    • View Profile
Re: SysML Requirements - <<copy>> dependency
« Reply #3 on: September 28, 2012, 10:02:17 pm »
Use the link at the bottom of this page to file the bug. This is a user forum, although Sparxians read and comment often.

q.