UML22 — behavior packages (Interactions, Statemachines

Several of the behavior packages (Interactions, Statemachines) are dependent on actions, and consequentially, on the activity package. However, they rely only on a very small part of the action model. Primitive, non-structured, actions need to be independent of the activity model. This can be solved by: (a) Create an Actions::Action metaclass that is independent of Activities::Action. In the activity chapter, Activities::Action should subclass this new action. (b) Move Activities::InputPin and Activities::OutputPin into the Actions package, again adding additional features in the Activities package later. (c) Move Figure 178 "Actions" to the Actions package. This would give the two other behavior types independence of activities in a minimal way. Preferably we would also allow connection of actions: (d) Move figure 177 "Flows", minus the ownership by activity to the Actions chapter (it would be best to rename the abstract node names to something less refering to Activities, but that is no big deal). Add that ActivityEdge is owned by Behavior, and specialize that ownership in the Activity package to activities only.

see above first, then continue below