A pseudostate encompasses a number of different transient
vertices on a state machine diagram. They are used, typically,
to connect multiple transitions into more complex state
transitions paths. For example, by combining a transition
entering a fork pseudostate with a set of transitions exiting
the fork pseudostate, we get a compound transition that leads
to a set of concurrent target states. Pseudostates do not have
the properties of a full state and serve only as a connection
point for transactions (but with some semantic value). Within
the UML metamodel, Pseudostate is a
sub-class of StateVertex.
The representation of a pseudostate on a statechart diagram in ArgoUML depends on the particular kind of pseudostate: initial, deepHistory, shallowHistory, join, fork, junction and choice. ArgoUML lets you place any pseudostate directly by tools for the specific types of pseudostate. These are described in separate sections below (see Section 20.12, “ Initial State ”, Section 20.14, “ Junction ”, Section 20.15, “ Choice ”, Section 20.16, “ Fork ”, Section 20.17, “ Join ”, Section 20.18, “ Shallow History ” and Section 20.19, “ Deep History ”).
The details tabs that are active for pseudostates are as follows.
ToDoItemStandard tab.
PropertiesSee Section 20.11.2, “ Pseudostate Property Toolbar ” and Section 20.11.3, “ Property Fields For Pseudostate ” below.
DocumentationStandard tab.
PresentationStandard tab.
StereotypeStandard tab, containing the stereotypes of the pseudostate. In the UML metamodel,
PseudoStatehas the no standard stereotypes defined.Tagged ValuesStandard tab. In the UML metamodel,
Pseudostatehas no standard tagged values defined.
Go upNavigate up through the package structure.
New StereotypeThis creates a new Stereotype (see Section 16.6, “ Stereotype ”) for the selected pseudostate, navigating immediately to the properties tab for that stereotype.
Delete from ModelThis deletes the pseudostate from the model
![[Warning]](images/warning.png)
Warning This is a deletion from the model not just the diagram.
NameText box. The name of the pseudostate. By convention pseudostate names start with a lower case letter and use bumpy caps to divide words within the name.
![[Note]](images/note.png)
Note ArgoUML does not enforce this naming convention.
![[Tip]](images/tip.png)
Tip Pseudostate names are not shown on the diagram and it is not usually necessary to give them a name.
ContainerText box. Shows the container of the pseudostate. This is the state hierarchy.
Button 1 double click on the entry will navigate to the composite state that contains this state (or the top-level state that is the root of the state containment hierarchy).
IncomingText area. Lists any incoming transitions for the pseudostate.
Button 1 double-click navigates to the selected transition.
OutgoingText area. Lists any outgoing transitions for the pseudostate.
Button 1 double-click navigates to the selected transition.