I checked with my model, and my "swimlanes" are in fact partitions (thus the reason they exist as their own objects), but when I create one... they are in fact placed under the object that the activity diagram is associated with (in my case a Use Case.)
Another one of the advantages of "re-using" a partition would be the ability to "list" all of the activities or actions associated with it. So if my UC activity diagram includes partitions that represent two actors (say a contributor & a editior), and these partitions are linked across several use cases, you would then be able to list the actions and activities that a contributor participates in and those that a editor does.
This seems to me to be VERY VERY helpful in the generation of both training material, operational docuements, etc. As a BIG part of my effort is toward generation of system documentation from the model (Sys Req Spec, External Sys Interface Spec, High-level Design Documents, Test Plans, etc. THIS IS VERY POWERFUL... Take the time to model well upstream during req. engineering effort, and reap the benefits downstream in Design, Test, Training, & Deployment/Operations documentation...
=========================================================
How do you create "Swimlanes" as part of a diagram? NOT that I want to... but trying to understand HOW the problem was created in the first place?
