Chapter 19. Statechart Diagram Artifact Reference

Table of Contents

19.1. Introduction
19.1.1. Limitations Concerning Statechart Diagrams in ArgoUML
19.2. State
19.2.1. State Details Tabs
19.2.2. State Property Toolbar
19.2.3. Property Fields For State
19.3. Action
19.3.1. Action Details Tabs
19.3.2. Action Property Toolbar
19.3.3. Property Fields For Action
19.4. Composite State
19.5. Transition
19.5.1. Transition Details Tabs
19.5.2. Transition Property Toolbar
19.5.3. Property Fields For Transition
19.6. Event
19.6.1. Event Details Tabs
19.6.2. Event Property Toolbar
19.6.3. Property Fields For Event
19.7. Guard
19.7.1. Guard Details Tabs
19.7.2. Guard Property Toolbar
19.7.3. Property Fields For Guard
19.8. Pseudostate
19.8.1. Pseudostate Details Tabs
19.8.2. Pseudostate Property Toolbar
19.8.3. Property Fields For Pseudostate
19.9. Initial State
19.10. Final State
19.10.1. Final State Details Tabs
19.10.2. Final State Property Toolbar
19.10.3. Property Fields For Final State
19.11. Junction
19.12. Branch
19.13. Fork
19.14. Join
19.15. Shallow History
19.16. Deep History

19.1. Introduction

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]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.

Figure 19.1. Possible artifacts on a statechart diagram.

Possible artifacts on a statechart diagram.

19.1.1. Limitations Concerning Statechart Diagrams in ArgoUML

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]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.