Associating activities with partitions

[whizzo]

I've looked at swimlanes but they just seem to be a region on a diagram and have no entry in the dictionary.
What I want to do is to have a pool of partitions that I can have in a package and then drag them onto activity digarms in other packages. I've suceeded in doing this but then I drag activities (instantiations) into these partitions but there is no visible association between the activity and partition. In the long term what I want to do is to be able to query "give me all the activities associated with a partition across the whole model" Anyone else tried to do this and had any success? I know if the partition is in the samepackage as the activity the association is made but dragging a partition into a diagram from another package (simple link or instantiation) does not even show up in the target package.

[Geert Bellekens]

I don't think you are supposed to re-use an activity partition on different diagrams (especially not if they are in different packages).
I think the link between the actions and the activitypartition is "nesting".
So if you really wanted to re-use the same partition in different places I guess you'll have to move all actions as nested element under the activity partition in the project browser.

If this is what you want then you can always "copy / paste as new element" the actitivy partitions into the new diagrams.

Geert

[whizzo]

Yes I've seen the "nesting" which is what I want. However if you are modelling use cases using activity diagrams then you are likely to want to use the same partitions across many diagrams. It seems logical (to me anyway) that you may want to analyse the use of these partitions eg which use cases are the applicable to. Anyway - thanks for your advice.

[Geert Bellekens]

In that case you should probably define one classifier (such as an Actor) and link the (new) Activity Partitions to this single classifier.

Geert

[Paolo F Cantoni]

Yes I've seen the "nesting" which is what I want. However if you are modelling use cases using activity diagrams then you are likely to want to use the same partitions across many diagrams. It seems logical (to me anyway) that you may want to analyse the use of these partitions eg which use cases are the applicable to. Anyway - thanks for your advice.

FWIW, I think "Nesting" is wrong...

I also think that "Partition" should be a form of rendering not (necessarily) an element in itself...

Paolo