Re-use of swimlanes

[KP]

2.) SHOULD I create the association between the partition and the corresponding actor? (I believe it would be helpful to achieve some of what I posted earlier) And what should the assoication type be? Trace, Dependency, or?

It's a matter of taste but I would have the actor classify the partition: right-click the partition and "Advanced | Instance Classifier".

Neil

[bioform]

That sounds like a good approach. However how would I name the partition object or would I just leave it blank.

Example:
Actor - Site Contributor (SC), set Partition's classifier to Site Contributor and leave the partition's name blank... Partition's displayed name would then ":Site Contributor"

Previously, I just named the Partition the same name as the actor it was associated with (for clarity on the activity diagram), but that now would lead to rather odd redundant looking results (Site Contributor :Site Contributor.)

It just seems "wrong" to leave the object's instance name blank... Is that true? <Looking over my shoulder for the UML Modeling police!>

Right now, I am developing project models to support requirement engineering involving Use Cases, Business Object Classes, Features, Requirements, Traces to other items such as Stakeholder Needs, Acceptance Criteria, UC dependencies, logical UI (prototypes) screen, tests, and test cases, expressed as UML objects or instances... BUT the underlying goal is to make sure that the model and it's elements have value to the downstream consumers (customer, testers, designers, developers, trainers, etc.)

I want to make sure that an approach I choose now, will not lead to unexpected issues later...

[bullet]

from my understanding swimlane do express business units or departments and/or whole or part of a system: I would name the partition(s)/swimlane. Example: SiteConstructor->WebDev Department or SiteConstructor->CMS(ContentManagementSystem)

clear

[bioform]

so for my example what would you suggest?

[bullet]

so for my example what would you suggest?

ok something like: (Site Content :Site Contributor.)

customer=actor,corporate=partition/swimlane
testers=actor,staging=partition/swimlane
designers=actor/developers=actor,development=partition/swimlane
trainers=actors,HR=partition/swimlane

etc.

[bioform]

But that is NOT the intent of the partion in the activity diagram... It is to show those actions and activities that are associated with the actor "Site Contributor" that occur in the Usecase that the activity diagram is documenting...

I guess using the instance classifier is NOT what I want to do, since this is NOT an instance of the actor, but the representtion of the actor's potential choices of actions or activities within the scope of the use case...

Any idea how to REMOVE this now that I have created it like that?

[bullet]

not 100%, since I am bloody new to EA, but I guess if as partition as part of model(2.0), right click/delete or via diagram (1.0) right click/configure swimlanes and delete from list

[bioform]

Bullet, don't worry EA has sometimes left me bloody too! (Or maybe it's more my ignorance of UML and EA combined... but I'll just blame it on EA... Seems the american thing to do!  <wink>)