Behavior StateMachines can be used to specify any of the following

Gallery
Tutorial
TRAIL: Webel's ultimate guide to Systems Modeling Language (v1) with MagicDraw/Cameo
Section
01:03: UML Behavior: StateMachines quick start
Topic level
ESSENTIAL
UML keywords
Class
Behavior
StateMachine
BehavioredClassifier
BehavioredClassifier::classifierBehavior
BehavioredClassifier::ownedBehavior
BehavioralFeature::method
Operation
Reception
Keywords
Slide kind
UML Class Diagram
Click on the image to view it full size
Up next
StateMachines - simplified metaclass hierarchy
Notes
Snippets (quotes/extracts)
Visit also
Visit also (backlinks)
SysMLv1: Cameo Simulation Toolkit: Cases for StateMachine Transitions with 'effect' Behaviors and/or States with 'entry' Behaviors triggered by a Signal with an attribute [with mini video]
Related slides (includes other tutorials)
StateMachine diagram for comparing action language access to an operation for a guard
StateMachine for the Dialer class
Overview: Controller class (and its Activity), Dialer Class (and its StateMachine), Number class
UML2 StateMachine - metaclasses - ADVANCED REFERENCE ONLY
StateMachines - simplified metaclass hierarchy
Figure 14.7 Composite State with two States
Figure D.8 - Finite State Machine Associated with “Drive the Vehicle”
Figure 13-1: Block definition diagram with state machines as blocks associated with submachines and types of parameters
The number.print Activity as exit Behavior for the PartialDial State
The number.print Activity as exit Behavior for the PartialDial State
Related slides (backlinks, includes other tutorials)
StateMachines - simplified metaclass hierarchy
UML Event types for triggering Transitions
uml101 - StateMachines - NOTATION REFERENCE CARD
Kinds of States
State configurations
Effect, Entry, Do, Exit
Composite state entry and exit points
Submachines: entryPoint and exitPoint
Using submachines
Pseudostates - initial, fork, join, terminate
Pseudostates - junction
Pseudostates - choice