Generating sequence diagrams from use cases

[andykennelly]

Within a use case I have created a structured specification (within the Rules/Scenarios option).
The available Context References reflect relationships defined elsewhere in the model, of course. When I type in the name of one
of these context references it is "recognized", i.e. shown as underlined.

So far, so good.

Now, when I generate a sequence diagram from here, the context reference elements are created as instances, rather than
links. This means my project browser gets very cluttered, since I'm creating a number of sequence diagrams each of which include the
same context reference elements.
Is there a way to define 'link' as the default representation of elements within a use-case generated sequence diagram?

[qwerty]

There are a number of good reasons for using instances in sequence diagrams. First, it's not classes, but instances communicating. Second see first. Finally EA will simply kill your model if you are using classes instead of instances in sequence diagrams when you use version control or ex-/import via XMI.

q.

[Ian Mitchell]

I agree with Qwerty.
Sequence diagrams show specific interactions between instances of classes/components or Actors. EA is great at letting you quickly go from the specifics of the SD to generality of creating Operations on the Classes.
Yes, it'll make a bit of a mess in your model, but just hide the instances as part of your 'working out', and don't ever print them.