Relationship matrix is skipping one element!

[Richard Freggi]

I have a relationship matrix showing use cases vs. actors and it works fine except that the very first use case in my package is missing from the matrix!  Tried a few times in different ways, tried editing the missing use case, reset IDs, integrity check etc...
The use case shows up in searches, queries etc.  It's just missing from the relationship matrix
Has anyone had this issue and is there a solution?  Thanks!

[PeteC]

An obvious question - is it in the right package? A search may find it but it could be in a different package to that specified in the relationship matrix.

A less obvious one is whether it is actually the same type and stereotype as intended? I have seen relationship matrices miss elements because they were subtly different (even if visually the same). I think I figured that one out by changing the Type in the Relationship Matrix from the type we thought it was to <All> and the missing elements appeared. You might of course also end up with other elements that you don't want but it might help work out the cause.

[Modesto Vega]

Which version of Sparx? Does it happen with anything else - e.g. classes, package elements? Are the axis sorted?

The only way around I can think of is creating a dummy use case and somehow force it to show first, for example by starting its name with 0 (the number zero) or something like AAAA. If that workaround does it, this looks like a bug where the 1st use case is skipped.

[Paolo F Cantoni]

An obvious question - is it in the right package? A search may find it but it could be in a different package to that specified in the relationship matrix.

A less obvious one is whether it is actually the same type and stereotype as intended? I have seen relationship matrices miss elements because they were subtly different (even if visually the same). I think I figured that one out by changing the Type in the Relationship Matrix from the type we thought it was to <All> and the missing elements appeared. You might of course also end up with other elements that you don't want but it might help work out the cause.

(my emphasis)  Excuse me for hijacking this thread, but this is another example in my quest to get Type+Stereotype supplanted by Metatype.  Even though you can apply a stereotype to any underlying type (and, usually, the shapescript will work well enough to fool you), there won't be a metatype intersector for the spurious combination.  So although the stereotype may appear to be correct, the metatype will fail!

Paolo

[Richard Freggi]

An obvious question - is it in the right package? A search may find it but it could be in a different package to that specified in the relationship matrix.

A less obvious one is whether it is actually the same type and stereotype as intended? I have seen relationship matrices miss elements because they were subtly different (even if visually the same). I think I figured that one out by changing the Type in the Relationship Matrix from the type we thought it was to <All> and the missing elements appeared. You might of course also end up with other elements that you don't want but it might help work out the cause.

1. Yes
2. Yes. also tried with <All>, it does not show
Cheers

[Richard Freggi]

Which version of Sparx? Does it happen with anything else - e.g. classes, package elements? Are the axis sorted?

The only way around I can think of is creating a dummy use case and somehow force it to show first, for example by starting its name with 0 (the number zero) or something like AAAA. If that workaround does it, this looks like a bug where the 1st use case is skipped.

1. Version 13.10
2. No only happens with this use case

[Modesto Vega]

Which version of Sparx? Does it happen with anything else - e.g. classes, package elements? Are the axis sorted?

The only way around I can think of is creating a dummy use case and somehow force it to show first, for example by starting its name with 0 (the number zero) or something like AAAA. If that workaround does it, this looks like a bug where the 1st use case is skipped.

1. Version 13.10
2. No only happens with this use case

I cannot reproduce it on V13 build 1310, I have create a project with 4 actors and 6 use cases and they all appear in the matrix. This leads me to think that there is a problem with the particular UseCase you are missing

[Richard Freggi]

Thank you, I tried everything and eventually I had to create a new use case, copy all tagged values and move all associations to it, then delete the old one.  It was the only thing that would work.
If anyone has experience identifying this kind of failure to show an element (must be a foreign key issue in the underlying Sparx tables, BUT the use case was showing up OK in all my queries...) please let me know!  Thanks!