Rational Statemate supports the graphical elements (types, sub-types, and structures) described in the following table.
The primary graphical element used in statecharts. States represent behavior of the system, or part of the system. States in a statechart differ from states shown in more traditional state diagrams, or finite state machines (FSM), in two ways: they can be divided into sub-states hierarchically and they represent parallel state behavior. There are two types of states:
• Or-states are similar to states in traditional FSM. The statechart can be in only one Or-state at the same level of hierarchy at one time. Or-states are represented with a rounded rectangle. The primary graphical element used in activity charts. Activities represent functions in the functional view of the system. An activity represents something that transforms inputs into outputs.Activities can be allocated to modules (structure) and can contain statecharts. You can specify the behavior of an activity by connecting it to a subroutine.
• Internal primitive activities (reactive-controlled and reactive-self) can be connected to tasks (no mini-specs or decomposition is allowed). The primary graphical element used in module charts. Modules are used to represent the structure of the system. There are two types of modules: internal (solid rectangle) and external (dashed rectangle). Any entity (person or system) that performs certain roles in the system defined by a boundary box. An actor is depicted as a stick figure and only interacts with a use case One of two types of states that can be used in a statechart. The Or-state enables a user to represent sequential behavior. The Or-state is similar to the states used in traditional state diagrams or finite state machines.The statechart can be in one, and only one, Or-state at any one time (at a particular level of the state hierarchy). Or-states can be subdivided into smaller states (decomposed). And-states (sometimes called concurrent or orthogonal states) enable a user to represent parallel behavior. When a statechart enters one And-state, it simultaneously enters all other And-states at that level of the state hierarchy. And-states can be subdivided into smaller states (decomposed). Any activity outside the scope of the topmost activity in a particular activity chart. Because activity charts are hierarchical, an external activity is usually resolved to a box in a chart higher in the chart hierarchy.However, an external activity can be resolved to a box that is an internal activity at a higher level. In this case it remains simply an external activity when referenced in the lower chart.The General Preference “Strict External-Activity Resolution” allows more flexibility while resolving External Activity to its definition Activity. Set the preference: “General Preferences...” -> “Strict External-Activity Resolution” to “No” to allow more flexibility and to “Yes” to keep the previous behavior. Describes the behavior of the activity in which it resides, and controls activities on the same hierarchical level. An activity can have only one control activity. An @ symbol precedes the title of a control activity. Stores information on activities for later use. Data stores can also be used to total large volumes of data, continuously accumulating over time. Data stores are always basic; they cannot contain other data stores or activities. See Working with the Router (External Router). See Working with the Router (Internal Router). Analogous to a data store in an activity, except it is used in a module. Stores information on modules for later use. Data stores can also be used to total large volumes of data, continuously accumulating over time. Data stores are always basic; they cannot contain other data stores or modules.The relationships between graphical types, sub-types, and structures are shown in following table.
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•