Composite Elements - A Question

[kamil.svoboda]

Just to confirm: you drag the package onto the open diagram window - not onto the diagram icon in the browser? If yes: what release do you use?

yes I drag the package onto the open diagram window (sequence diagram) and the package is added as a element of the diagram. I use build 729 of the corporate edition.

[Bruno.Cossi]

Hi Kamil,

I think that what Thomas is getting at is the concept of hyperlinks - you can drag a diagram on top of another diagram and create a hyperlink (much like an HTML one). This way, you can create a diagram underneath one Use Case, create an empty diagram (ideally "custom") underneath another Use Case, drag the first diagram onto the second one, create hyperlink to it, and thus, you have the diagram accessible via both Use Cases.
There is probably a better way of doing this, you can for example duplicate diagrams (without creating duplications of all of the elements on them) etc. Anyway, try this and let me know if that is what you wanted.

Bruno

[sargasso]

Kamil,
Perhaps it would help us follow what you are trying to achieve if you would answer the following...

If you do achieve what you are trying to do, what will you do with the resulting package?

It seems to me that what you are trying to end up with is a package "Sequence model" containing a single diagram, say "Sequence model diagram" containing hyperlinks to all the other sequence diagrams in the model. In other words, a sort of index to all the sequence diagrams under the use cases.  If this is the case then I think(!) you are attempting to do it backwards - you should be dragging the use case sequence diagram (from the project browser) onto the diagram under the package, not the other way around.


?hth
Bruce

[kamil.svoboda]

Hi Kamil,

I think that what Thomas is getting at is the concept of hyperlinks - you can drag a diagram on top of another diagram and create a hyperlink (much like an HTML one).

YES! Now I understand! I have to create new diagram in the Sequence package and then create hyper link from the original sequence diagram (child of use case) to that new created.
This is solution of my problem, but I have expected more elegant concept – like ms windows shortcuts. It would be nice to create simple shortcut from the original sequence diagram directly to the package Sequence model. This model would contain shortcuts of all sequence diagrams of the project.
Thanx!
Kamil
BTW: sorry for my terrible English

[Bruno.Cossi]

Hi,

I am not sure if the shortcut-type solution would not create only more mess. Anyway, what you can also do is to link the diagram back to the Use Case using the <<realize>> relationship (i.e. the Use Case is implemented by the Sequence Diagram). This way it will also appear in the Links section of the Use Case.
I am trying to wrap my mind around what is it that you are trying to achieve, maybe the Relationship Matrix would resolve your problems?

Bruno

P.S. Do not worry about your English, it sounds better than mine - and you have not even heard my accent!

[angel-o-sphere]

I would use a "realize" relation but with stereotype <<refines>> and not <<relize>> as a sequence or activity diagram "describes" or "refines" parts or the whole flow of a use case.

angel'o'sphere