Afaik, Rhapsody does support the graphical notation of an "Accept Event Action" on statechart diagrams in v7.5 and later (I've checked for v7.5.1). It would also allow to do that on activity diagrams (in both design and analysis mode).
However, Rhapsody also allows using the textual notation in order to show, that a transition waits for an event on a statechart.
The textual format allows to show the triggering event, an optional guard and an optional action (which could be a send action) associated with that transition.
The textual format looks like that:
Event [Guard] / Action
The nice thing about Rhapsody... it does not only show that on a diagram, it can also generate corresponding code (including an automatically generated event class definition on package level and an event reception on class level).
In system analysis mode, the graphical notation may be better understandable and so probably preferable (see on the left):
Attachment:
StatechartAcceptEvent.png [ 8.86 KiB | Viewed 327 times ]
For target code / deployable code generation I'd recommend using the textual notation, because it generates more efficient code (avoiding implicit "sendaction" and "accepteventaction" helper states in the code - see on the right).
-Luke.
