Hi there,Hi Denis,
I'm trying to produce "responsibility diagrams" showing the relationships of a given actor. Now when a swimlane in an activity diagram (or BPMN diagram in my case) is used as an instance of an Actor. The instance does not appear in the project view and can therefore not be dragged to a responsibility diagram.
If I drag the Actor instead, it shows no relationships. The fact that an activity or task is drawn within a swimlane should however be considered as having a relationship with the Actor (or Actor instance?).
I would like the possibility to reuse Actors (or Actor instances?) as swimlanes in some diagrams and as the usual Actor icon in other diagrams.
Denis.
AFAIK, neither EA nor UML imply a relationship between swimlanes and elements.
As far as instances showing up in the Project Browser, check your settings for tree depth. It is possible for elements - particularly instances - to be at too low a level in the model to show up. You'll find the right settings from the main menu via Tools | Options. They are at the bottom of the main Options page.
Hi David,Hi Denis,
The UML 2.0 and 2.1 specs really show an association named "represents" from ActivityPartition to Element. Please also take a look at the semantics section for ActivityPartition.
[size=13][SNIP][/size]
Denis
If I drag the Actor instead, it shows no relationships. The fact that an activity or task is drawn within a swimlane should however be considered as having a relationship with the Actor (or Actor instance?).
I would like the possibility to reuse Actors (or Actor instances?) as swimlanes in some diagrams and as the usual Actor icon in other diagrams.
The UML 2.0 and 2.1 specs really show an association named "represents" from ActivityPartition to Element. Please also take a look at the semantics section for ActivityPartition.
As I understand it, the various "represents" relationships you mention are between swimlane headers class or attribute elements. These relate a particular swimlane to a given element in the sense that the element is the 'topic' of the swimlane. The element must appear elsewhere in the model. The "represents" relationship is not meant to relate the swimlane to other elements 'between the lines' as it were. If you want to define relationships between the 'header' element and other elements in the model, use the appropriate UML connectors. Simply including them within a swimlane does not constitute a semantically meaningful relationship.I do believe, Sir David, that you are contradicting me... ??? ;D
David
I do believe, Sir David, that you are contradicting me... ??? ;D
I did imply that including one classifier within a a partition representing another created some semantically meaningful relationship... However, I did observe that I was at a loss to formally define it... So maybe we are both right...
Unfortunately step 2 is not working.
If you define a swimlane in an Activity diagram for instance and the Classifier refers to an Actor, Ctrl-U on that actor does not show the usage in your activity diagram...
If you use activity partitions instead of swimlanes then Ctrl+U does find the classifiers. Custom searches can find activity partitions too. I would recommend you use activity partitions instead of swimlanes.
If you use activity partitions instead of swimlanes then Ctrl+U does find the classifiers. Custom searches can find activity partitions too. I would recommend you use activity partitions instead of swimlanes.