action pin transformation composit case

[Paul Lotz]

In an activity diagram we may have two actions, one with an action pin for object output that is connected to the other's action pin for object input.  If the two pins do not refer to the same object (common in cases of decomposition) we can indicate this through a transformation.  The decomposition case is shown, for example, in fig. 12 here: http://www.jot.fm/issues/issue_2004_01/column3/.

OK, so how do we indicate the opposite case (composition)?

[Paul Lotz]

OK, here is a pictorial representation of what I am trying to do: .

The decomposition transformation is well-documented in various places, but I haven't found a good source to describe the composition case.  (I would think this case would be pretty ubiquitous!)  The solution I have here may in fact be correct, but I haven't found any reliable documentation to support this.

Paul

[«Midnight»]

Just curious... Why not a composite structure or collaboration diagram, or perhaps both?

[Paul Lotz]

Just curious... Why not a composite structure or collaboration diagram, or perhaps both?

Hmm... well, I will take a look at these.  The plan to date has been to focus on the behavioral aspects of the model using use cases-->activity diagrams-->interaction diagrams, a workflow that seems to fit my current objectives well (derive the interface definitions based on the required system user features).  Activity diagrams are designed to handle object flow, according to the examples--there are just these couple issues that seem to impede the modeling process....