Foreign Object Highlighting - differentiation

[Paolo F Cantoni]

If the foreign object name appears more than once (including duplicating the actual object name) there needs to be additional qualifiers (such as the package name) to differentiate them.

Paolo

[«Midnight»]

I take it you are referring here to instances. [Yes, you did say "object" but I'm being sure.]

Then we are talking about something analogous to "Highlight Foreign Objects" (which seems to generally mean "classifiers" rather than "instances") for instances. This would allow the reader to understand that the object "X100:Washer" is an instance of Washer from the HardwareFasteners package rather than from HomeAppliances or HumanResourceJobCategories, for example.

Sounds reasonable to me.

[Paolo F Cantoni]

I take it you are referring here to instances. [Yes, you did say "object" but I'm being sure.]

Well, I actually meant Element - but EA's unique user interface strikes again...  

I meant whatever, setting the Foreign Object Highlighting checkbox affects.  This seems to be Classifiers, but I'm not certain...

Paolo

[«Midnight»]

Well, it certainly affects classifiers. As to whether this was the intent, or the sole intent, it's difficult to say. And that very uncertainty is an issue - CCC!

I just looked again. Foreign objects (instances) are indicated by a "from <wherever>" note in italics below the object. Foreign [i[classifiers[/i] are shown by a text indicator in the header. I think each of these are in line with the UML standard, and thus consistent in that sense. Unfortunately the text in the Options dialog is a little vague in this respect.

However, I suspect Sparx has got it pretty close to correct given the UML take on this. I do think that CCC would apply and be beneficial there (UML) as well Paolo.

EDIT:
BTW, I used to use a tool that showed a foreign Class with the text "(from <wherever>)" above the object, much like some of the OMG documents show in metamodel fragments. When I first used EA I really missed this. Perhaps a bit of nostalgia is softening my opinions about how instances are displayed in EA. However, I've come to prefer the way EA shows foreign classifiers.

I wouldn't mind having the choice (in either case) though. Take that with a few grains of salt; I've not checked the spec or guides.

[Paolo F Cantoni]

Associated with this topic is the observation that the foreign object highlight only documents the immediate generalizations.

This is appropriate.  However, it would be neat to indicate that there are higher levels on the foreign object by means of an ellipsis (...) after the name.

Thus if the hierarchy is:

Namespace->TreeGraphNode->HierarchicalGraphNode->DirectedGraphNode->GraphNode

Namespace would show:  TreeGraphNode...
(... indicating: But wait, there's more!   )
while
DirectedGraphNode would show GraphNode (only)

Paolo

[«Midnight»]

Or perhaps even (as an option) to show the hierarchy. This could be done one line at a time, fitting with the visual paradigm that is there now.

Something roughly along the lines of the hierarchy when you show inheritance details for attributes, etc. on classes.

Then we can start talking about making these into hyperlinks to the ancestor elements. Wow!

[Paolo F Cantoni]

Or perhaps even (as an option) to show the hierarchy. This could be done one line at a time, fitting with the visual paradigm that is there now.

I thought of that, but many of my hierarchies are extremely deep and wide (as I work a lot in the Computationally Independent and Domain Independent^TM models).  However, I thought a context menu item allowing you to open the Hierarchy Window could do the trick...

[size=13][SNIP][/size]Then we can start talking about making these into hyperlinks to the ancestor elements. Wow!

You read my mind!  I'd also like to be able to select the ancestor item and ALT-G to select in browser.

Paolo

[SF_lt]

register^tm   (register as the enhancement)

[Paolo F Cantoni]

register^TM   (register as the enhancement)

Actually, I have a new pattern for requests and suggestions to Sparx.  I post a new thread in the forum and then email Sparx with a reference to the thread.  That way, they can see any on-going discussion.

As an Architect, I know I don't always come up with the best ideas¹.  Getting input from the community (especially an enthusiastic one like this one), is a great way to refine/refactor/improve ideas into great ones!

I commend this approach to you all...

Paolo
¹I DO try to think them through...

[SF_lt]

some time ago I have come to the same idea - using BUG word for bug report thread topic & so on

[Paolo F Cantoni]

However, I thought a context menu item allowing you to open the Hierarchy Window could do the trick...
You read my mind!  I'd also like to be able to select the ancestor item and ALT-G to select in browser.

It would also be really handy to be able to have a context menu item to add the parent to the diagram!

Paolo

[sargasso]

Context  - Add|Insert Related Element using 1 level link type generalization?
b

[Paolo F Cantoni]

Context  - Add|Insert Related Element using 1 level link type generalization?
b

No, that picks up ANY generalization.  I just want that specific one added.

Remember, this is in the context of the UI being altered so that we can actually select a particular parent.

Paolo

[sargasso]

Hmmmm... self imposed rule of single inheritance chains....

Am I still missing the point or

1) double clicking on the parent item in the hierarchy pops up the info on the selected parent.
2) bit messy but - select desired parent in heirarchy window (which I have autodocked on the LHS)right click on it and use locate related object, which pre-selects the element in the browser (which I have docked on the RHS) and cna then be dragged into the model.

bruce

[Paolo F Cantoni]

Hmmmm... self imposed rule of single inheritance chains....

Am I still missing the point or

No and yes...
What you suggest will work, in principle.  In practice, with my complex latticed hierarchies, updating the Hierarchy window can take a considerable time (even on my 3G Dell).  So I'm just trying to avoid using the Hierarchy window.

Paolo