SysML Activity Diagram to More Fully Meet the Spec

[rothnic]

[size=12]Activity Decomposition in BDD[/size]
Currently there is no relationship between the Activities and the Actions that they invoke.

The SysML spec provides a description of how this should be depicted via a BDD: http://www.omg.org/spec/SysML/1.3/PDF/
See page 121/272 (labled page 99).
An action should have a Composition relationship to the Activity that invokes it, and an association relationship to an object node.

Allocation
When creating partitions in an activity diagram, you should be able to use specific instances instead of the generic classifier for the partition.

When dragging actions into the partitions, the partition should allocate the action to the block. (153/272)

An Activity shown in rectangle style should be able to show an allocatedto or allocatedfrom compartment. Same with a block, it should have allocatedto/allocatedfrom.

That way you can perform functional allocation to system structure and be able to depict that relationship within the element symbol. (152/272)

[rothnic]

I'm struggling to find a way to handle the activity to action relationships manually or via scripting.

Would the process be to find each diagram that is composite for each activity.
Then find each action in that activity diagram.
Then find each Activity called by that action (can't find how to do this via scripting)
Then add the composite associations?

[Eve]

Actions are physically nested within the Activities that invoke them.

The relationship between them is defined in UML by a composition.

The referenced diagram is a link between two activities and not actions at all. If you look at Figure 11.13 you'll see a more concrete example. From that example (and 11.14 for the objects) it's clear to me that the relationships would need to be explicitly defined.

EA allows that kind of diagram to be created, but you'll need to explicitly set the activities to use rectangle notation and the quicklinker doesn't contain composition (but you can create it from the toolbox.)

[rothnic]

Actions are physically nested within the Activities that invoke them.

The relationship between them is defined in UML by a composition.

The referenced diagram is a link between two activities and not actions at all. If you look at Figure 11.13 you'll see a more concrete example. From that example (and 11.14 for the objects) it's clear to me that the relationships would need to be explicitly defined.

EA allows that kind of diagram to be created, but you'll need to explicitly set the activities to use rectangle notation and the quicklinker doesn't contain composition (but you can create it from the toolbox.)

Yeah, I misspoke.

The thing that was confusing for me was that I had to reproduce the functionality that works essentially like blocks and parts. So I ended up creating a script that I could run on a directory that:

• Goes through all the nested activities/actions.
• For each action, i get its classifier
• For each classifier look for existing associations to the composite element
• I look for an existing tag on any found connector
• I add a tag with the action's GUID to the connector if it doesn't exist
• I update the role with the action name