Book a Demo

Author Topic: SD Interaction states Bug  (Read 5299 times)

Guillaume

  • EA Practitioner
  • ***
  • Posts: 1405
  • Karma: +42/-2
    • View Profile
    • www.umlchannel.com
SD Interaction states Bug
« on: February 29, 2012, 02:29:55 am »
Hi,

I'm using interaction states in a sequence diagram to show when an object's state changes following receipt of a message.

I noticed that all interaction states are not stored in the diagram itself as expected (similarly to notes) but in the package that contains the diagram (having moved the diagram to a different package)
So if I move my SD and all UML elements to a different package and delete the original package, I lose all my interaction states!

This bug was found in EA 7.5 but also in EA 9.2

This is a scary bug ...!
Best way to resolve by Sparx is to materialise interaction states in the project browser (like fragments, endpoints, etc.)

« Last Edit: February 29, 2012, 02:31:58 am by gfuk »
Guillaume

Blog: www.umlchannel.com | Free utilities addin: www.eautils.com


Paolo F Cantoni

  • EA Guru
  • *****
  • Posts: 8626
  • Karma: +259/-129
  • Inconsistently correct systems DON'T EXIST!
    • View Profile
Re: SD Interaction states Bug
« Reply #1 on: March 01, 2012, 02:02:20 pm »
Quote
Hi,

[size=18]...[/size]

This is a scary bug ...!
Best way to resolve by Sparx is to materialise interaction states in the project browser (like fragments, endpoints, etc.)

Yes, Guillaume

There are a LOT of objects that are NOT exposed in the browser!

There needs to be a setting to allow ALL such objects to be exposed if the use needs to see them.

I get caught by the same type of problem often!

Please submit a BUG report (or Feature Request) to expose these hidden items.

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

Guillaume

  • EA Practitioner
  • ***
  • Posts: 1405
  • Karma: +42/-2
    • View Profile
    • www.umlchannel.com
Re: SD Interaction states Bug
« Reply #2 on: March 01, 2012, 06:14:05 pm »
Hi Paolo,

I will notify this as a bug report.
Although I agree with you about the issue on elements hidden from the project browser, my worry is really about this issue with interaction states being stored in the package instead of the diagram (leading to the problems I mentioned)

Thanks
Guillaume
Guillaume

Blog: www.umlchannel.com | Free utilities addin: www.eautils.com


Paolo F Cantoni

  • EA Guru
  • *****
  • Posts: 8626
  • Karma: +259/-129
  • Inconsistently correct systems DON'T EXIST!
    • View Profile
Re: SD Interaction states Bug
« Reply #3 on: March 01, 2012, 06:54:10 pm »
Quote
Hi Paolo,

I will notify this as a bug report.
Although I agree with you about the issue on elements hidden from the project browser, my worry is really about this issue with interaction states being stored in the package instead of the diagram (leading to the problems I mentioned)

Thanks
Guillaume
Guillaume,

NOTHING is stored in the diagrams.  All the states are held in objects in the model.  The diagram is merely a way of rendering the model contents onto a "canvas".

If you "Copy and Paste" the interaction state in to a couple of diagrams (even in different packages) and then change the name you'll see them ALL change.  You can even delete the diagram and the other copies will remain.
(BTW: THAT's one of the differences between a diagrammer (eg Visio) and a Modeller (eg Sparx EA))

The problem (as I indicated) is that you can't see where in the browser the interaction state is - because you can't select it in the browser.

HTH,
Paolo

« Last Edit: March 01, 2012, 06:55:31 pm 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: +397/-301
  • I'm no guru at all
    • View Profile
Re: SD Interaction states Bug
« Reply #4 on: March 02, 2012, 05:00:03 am »
I agree that these hidden elements are bad. I guess they were invented this way to reduce the listed elements in the browser. But there are better ways to group and hide such elements (e.g. the Interaction elements). I vote for showing ALL elements.

What do you think of this one: http://www.sparxsystems.com/cgi-bin/yabb/YaBB.cgi?num=1329918455

q.
« Last Edit: March 02, 2012, 05:04:53 am by qwerty »