Element Properties : Creating and Modifying Elements : Properties Window : Creating and Modifying Elements : Graphical Elements

Graphical Elements

The following graphical element types can be created or modified in the Properties dialog box:

State
The State properties dialog box contains the following items:

Reactions - A text box for defining static reactions.

Static reactions describe the behavior that takes place within a specific state. For example:

While in (S1) DO

[POWER_ON]/tr! (LIGHT_ON);

COUNTER:=0

They also describe actions that occur when there’s a transition to enter or exit the associated state. For example:

On entering (S1) DO

/st! (activity_warm_up)

On exiting (S1) DO

/sp! (activity_warm_up)

Separate multiple reactions in the Properties window with a double semicolon (;;). States that have static reactions are distinguished by a ‘>’ symbol after the chart name (e.g., ALARM>).

T/W - Specifies the start/stop correspondence between a state and an activity:
T (Throughout) is equivalent to a static reaction of:

   entering/);;

   exiting/sp!(A)

For a reactive-controlled activity A, exiting the state stops the activity. For a reactive‑self activity, there is usually an exit transition from the state triggered by the event stopped (A) This implies that if and when A stops of its own accord, the state will be exited.

W (Within) indicates that the activity A is activated sometime during the time the system is in the state and is intended to be used as a temporary specification when functional decomposition has not yet reached a point at which Throughout can be used. When the state is exited, A stops (unless, of course, it had stopped earlier for some other reason). However, A does not necessarily start when the state is entered.

Insert - inserts a new line above the selected line.

Delete - deletes the selected line.

Choose - Opens the Activities in State dialog box from which you can select activities to control using the Activities in State list.

Transition
To open the Transition properties dialog box, in the Statechart Graphical Editor, select Tools > Extended Properties.
The Transition properties dialog box contains the following items:

Attributes tab

Design Attributes tab

Description tab - A text box for a long description of the transitions.

Instance State of Generic Chart
The Instance State of Generic Chart properties dialog box contains the following items:

Parameter area - contains the names of actual parameters. An actual parameter is an element or constant, defined in the scope of an instance of a generic chart, that is mapped into a formal parameter of the generic chart during instantiation. The actual binding of an element must match the type of the formal parameter.

Insert - adds a new line above the selected line.

Delete - deletes the selected line.

Auto Binding - determines whether automatic binding is used.

Fill Formats - sets the fill color and type.

Activity
Rational Statemate supports the following activity elements:

Activity

Basic activity

Control activity

External activity

Datastore

Router

Each activity element has its own unique properties, though the operations are essentially the same and designed to be self-explanatory. For the sake of brevity, this manual uses the Basic Activity properties dialog box for the example because it is the most inclusive.
The Activity properties dialog box contains the following items:

Termination Type - A pull-down menu for selecting a type of termination. A termination expresses the activation rules for an activity. This should be reflected in the mini-spec of the activity. The following terminations are supported:

Reactive-Controlled - This type of activity is started by the control activity at the next higher level of the activity chart hierarchy. Once started, it will remain active for one or more steps until it is stopped by the same control activity. This type of activity can itself contain a control activity or mini-spec.
Reactive-self - This type of activity is started by the control activity at the next higher level of the activity chart hierarchy. This type of activity can itself contain a control activity or mini-spec. Once started, it remains active for one or more steps, until it ends by entering a termination connector in its control activity or executing a stop action in its mini-spec.
Procedure-like - This type of activity is started by the control activity at the next higher level of activity chart hierarchy. Once started, it runs to completion in a single step. This type of activity can itself contain a mini-spec, but can not contain a control activity.

Selected Implementation - A pull-down menu for selecting an implementation. The following implementations are supported:

Mini-Spec - Specifies that the activity is to be described by a mini-spec.
Subroutine Binding - Specifies that the activity is to be described by a subroutine.
Truth Table - Specifies that the activity is to be described by a truth table.

For more information on truth tables and for instructions on how to define a truth table in Rational Statemate, see Truth Tables.
Best Match - Directs Rational Statemate to select the implementation to use where more than one has been previously specified. The order in which the analysis tool (Simulation or Code Generation) selects an implementation is the order in which the options appear in the menu listing (as shown here). You can override the Best Match by explicitly selecting an implementation option. If the explicitly selected option has not been previously specified, the analysis tool uses the Best Match selection.
None - No implementation is to be used.

Mini-Spec - If a mini-spec implementation is selected, in this text box, define the fields that contain trigger/action expressions, except for procedure-like activities, which contain action expressions.

Is Activity - A text box to link an activity in one part of a module chart/activity chart hierarchy to another activity in a different activity chart.

Implemented by Module - If linking an activity, in this text box, specify the link from an activity to a lower-level module that implements the functionality of the activity.

Subroutine Binding - Associates a subroutine with the current activity. The subroutine is executed when the activity chart is accessed. The subroutine can be a procedure or a task.

Combinational Assignment - A combinational assignment is the expression used to assign a value to a combinational element with the following syntax:

   X := Y1 when C1 else

        Y2 when C2 else

        ...

        Ynz

where X is a variable condition or data-item, Y1 to Yn are expressions, and C1 to Cn are condition expressions.

Truth Table - If a truth table is selected as an implementation, the truth table is defined here.

Edit - a button that brings up the truth table for editing.
Delete - a button that deletes the truth table.
Note:
Instance Activity
Rational Statemate supports the following instance-activity elements:

Component Chart

Offpage Chart

Each instance-activity element has its own unique properties, though the operations are in many cases the same and designed to be self-explanatory.
The Instance Activity of Generic Chart properties dialog box contains the following items:

Parameter - See Description Tab for a description.

Termination Type - A pull-down menu. See Activity for a description.

Module
Rational Statemate supports the following module elements:

Module

Storage module

For the sake of brevity, this manual uses the Module properties dialog box for the example because it is the most inclusive.
The Module properties dialog box contains the following items:

Chart - displays the name of the chart the element is associated with.

Name - displays the name of the element.

Synonym - A text box for adding an alternate name for the element. The name may be used in other expressions to reference the element.

Description - A text box for adding a brief description of the element (up to 80 characters).

Module Purpose - A pull-down menu for selecting from the following:

Regular (default)

Described by Activity Chart - Specifies the activity chart the module is linked to.

Use Case
The use cases in a use case diagram can be described and linked with a Rational Statemate model through the use-case properties.
The Use Case properties dialog box contains the following items:

Use-Case External Description - Describes the use case, using a customizable template.

Scenario - List of scenarios associated with the use case. Each scenario can be linked to a sequence diagram and a set of attributes describing it.

The Scenario matrix includes full spreadsheet capabilities, including:

Scalable cell width and height

Cell dimensions saved with matrix

Cell text wrapping