Table of Contents
This chapter describes each artifact that can be created within a statechart diagram. Note that some sub-artifacts of artifacts on the diagram may not actually themselves appear on the diagram.
There is a close relationship between this material and the Properties Tab of the Details Pane (see Section 12.4, “Properties Tab”). That section covers Properties in general, in this chapter they are linked to specific artifacts.
![]() | Note |
---|---|
The whole area of behavioral modeling is still under development in ArgoUML. Many of the facilities described in the UML standard have yet to be implemented or are not fully implemented in the current release. |
Figure 19.1, “Possible artifacts on a statechart diagram.” shows a statechart diagram with all possible artifacts displayed.
The statechart diagrams are generally well drawn, but the 4 event types supported (CallEvent, SignalEvent, ChangeEvent and TimeEvent), are purely textual, with no way to link them back to their associated operations. Also the various kinds of Actions are only supported in the same way.
Code generation from statechart diagrams is not properly developed yet.
In the current version of ArgoUML, it is not possible to draw dashed lines
which indicate regions within a it composite state.
Or, in more formal terms, there is no distinction in the
diagram between a CompositeState with the (derived) attribute
isRegion
true or false.
![]() | Tip |
---|---|
The advisable work-around is, to draw regions as composite states. That way, the diagram would not look like it is supposed to be, but the underlaying model will be correct according the UML standard, an exported XMI file will be usable by all tools, and the project file will be loaded and displayed correctly in future versions of ArgoUML. |