Rate ... When the stereotype is applied to a parameter, the parameter shall be streaming, and the stereotype gives the number of objects or values that flow in or out of the parameter per time interval while the behavior or operation is executing. Source OMG Systems Modeling Language (SysML) 1.6
Rate ... It does not refer to the rate at which a value changes over time. Source OMG Systems Modeling Language (SysML) 1.6
When the «rate» stereotype is applied to an activity edge, it specifies the expected value of the number of objects and values that traverse the edge per time interval, that is, the expected value rate at which they leave the source node and arrive at ... Source OMG Systems Modeling Language (SysML) 1.6
... a copy is made of the removed object token, with the same value, and this is immediately placed back onto the DataStoreNode. Thus, the values held by a DataStoreNode appear to persist for the duration of each execution of its containing activity, even Source Unified Modeling Language 2.5.1
An OpaqueExpression specifies the computation of a set of values either in terms of a UML Behavior or based on a textual statement in a language other than UML. Source Unified Modeling Language 2.5.1
The String value of a StringExpression is obtained by concatenating, in order, the String values of either the operands or the subExpressions, depending on which is given. Source Unified Modeling Language 2.5.1
The substrings are given as either a list of LiteralString operands or as a list of StringExpression subExpressions (but it is not allowed to mix the two). Source Unified Modeling Language 2.5.1
A StringExpression is an Expression that specifies a String value that is derived by concatenating a list of substrings. Source Unified Modeling Language 2.5.1
Scientific notation consists of decimal notation followed by either the letter “e” or “E” and an exponent consisting of an optional sign character followed by one or more digits. ... Source Unified Modeling Language 2.5.1
Decimal notation consists of an optional sign character (+/-) followed by zero or more digits followed optionally by a dot (.) followed by one or more digits. Source Unified Modeling Language 2.5.1
A LiteralReal is shown in decimal notation or scientific notation. Source Unified Modeling Language 2.5.1
Note that “unlimited” denotes the lack of a limit on the value of some element (such as a multiplicity upper bound), not a value of “infinity.” Source Unified Modeling Language 2.5.1
A LiteralUnlimitedNatural is shown either as a sequence of digits or as an asterisk (*), where an asterisk denotes unlimited. Source Unified Modeling Language 2.5.1
A LiteralBoolean is shown as either the word “true” or the word “false,” corresponding to its value. Source Unified Modeling Language 2.5.1
A LiteralInteger is shown as a sequence of digits representing the decimal numeral for the Integer value. Source Unified Modeling Language 2.5.1
A LiteralString is shown as a sequence of characters within double quotes. The String value is the sequence of characters, not including the quotes. The character set used is unspecified. Source Unified Modeling Language 2.5.1
The notation for a LiteralNull varies depending on where it is used. It often appears as the word “null.” Other notations are described elsewhere for specific uses. Source Unified Modeling Language 2.5.1
A LiteralReal specifies a constant value of the PrimitiveType Real. Source Unified Modeling Language 2.5.1
A LiteralUnlimitedNatural specifies a constant value of the PrimitiveType UnlimitedNatural. Source Unified Modeling Language 2.5.1
A LiteralBoolean specifies a constant value of the PrimitiveType Boolean. Source Unified Modeling Language 2.5.1
A LiteralInteger specifies a constant value of the PrimitiveType Integer. Source Unified Modeling Language 2.5.1
A LiteralString specifies a constant value of the PrimitiveType String. Though a String is specified as a sequence of characters, String values are considered to be primitive in UML, so their internal structure is not specified as part of UML semantics. Source Unified Modeling Language 2.5.1
LiteralNull: In the context of a MultiplicityElement with a multiplicity lower bound of 0, this corresponds to the empty set (i.e., a set of no values). It is equivalent to specifying no values for the Element. Source Unified Modeling Language 2.5.1
A LiteralNull is intended to be used to explicitly model the lack of a value. Source Unified Modeling Language 2.5.1