ValueSpecification

Cameo Simulation Toolkit includes a (basic) TimeEvent, but fUML-1.3/1.4 does not. There are many different supported time units for duration constraints, and you can also use property values in durations.

A ValueSpecification is the specification of a (possibly empty) set of values. A ValueSpecification is a ParameterableElement that may be exposed as a formal TemplateParameter and provided as the actual parameter in the binding of a template.

Source

Unified Modeling Language 2.5.1

Property::defaultValue : ValueSpecification [0..1] Specifies a ValueSpecification that represents a value to be used when no argument is supplied for the Parameter.

Source

Unified Modeling Language 2.5.1

If the joinSpec ValueSpecification is given by a textual expression, then the names of the incoming edges may be used to denote ... the value associated with an object token offered from an ObjectFlow (if any).

Source

Unified Modeling Language 2.5.1

If the joinSpec ValueSpecification is given by a textual expression, then the names of the incoming edges may be used to denote a Boolean value indicating the presence (true) or absence (false) of an offer from a ControlFlow ...

Source

Unified Modeling Language 2.5.1

joinSpec ... This evaluation shall not be interrupted by any new tokens offered during the evaluation, nor shall concurrent evaluations be started when new tokens are offered during an evaluation. The ValueSpecification shall evaluate to a Boolean value.

Source

Unified Modeling Language 2.5.1

Join nodes may have a joinSpec, which is a ValueSpecification that determines the condition under which the join will emit a token. If a JoinNode has a joinSpec, then this ValueSpecification is evaluated whenever a new token is offered to the JoinNode ...

Source

Unified Modeling Language 2.5.1

UML2 Types of Pins - metaclasses

This content has been marked as discussing an ADVANCED topic!

Gallery

Tutorial

TRAIL: Webel's ultimate guide to Systems Modeling Language (v1) with MagicDraw/Cameo

Section

01:04: UML Behavior: Activities quick start

Slide kind

UML Profile Diagram

Starting an Action that has a ValuePin - LIMITED SUPPORT

Gallery

Tutorial

TRAIL: Webel's ultimate guide to Systems Modeling Language (v1) with MagicDraw/Cameo

Section

01:04: UML Behavior: Activities quick start

Slide kind

UML Activity Diagram

A ValuePin provides a value by evaluating a ValueSpecification ... When the Action is enabled by other means, the ValueSpecifiation of the ValuePin is evaluated, and the result is provided as an input to the Action when it begins execution.

Source

Unified Modeling Language 2.5.1

A ChangeEvent models a change in the system configuration that makes a condition true.

Source

Unified Modeling Language 2.5.1

UML2 ValueSpecification - metaclasses - ADVANCED REFERENCE ONLY

This content has been marked as discussing an ADVANCED topic!

Gallery

Tutorial

TRAIL: Webel's ultimate guide to Systems Modeling Language (v1) with MagicDraw/Cameo

Section

01:02: UML 101 for model-based systems engineering with SysML

Slide kind

UML Profile Diagram

Slot::value : ValueSpecification [0..*]{ordered, subsets Element::ownedElement} ... The value or values held by the Slot.

Source

Unified Modeling Language 2.5.1

InstanceSpecification::specification : ValueSpecification [0..1] ... A specification of how to compute, derive, or construct the instance.

Source

Unified Modeling Language 2.5.1

ObjectNode::upperBound : ValueSpecification [0..1] The maximum number of tokens that may be held by this ObjectNode. Tokens cannot flow into the ObjectNode if the upperBound is reached. If no upperBound is specified, then there is no limit on how many ...

Source

Unified Modeling Language 2.5.1

If an output-argument does not have an explicit assignment-target specified, it is considered to have an unknown assignment target. In this case, it is required to include a value-specification, which denotes the returned value for the argument.

Source

Unified Modeling Language 2.5.1

An output-argument with an explicit assignment-target given may also optionally include a value-specification. If a value-specification is given, then this denotes the returned value for the argument. Otherwise the argument has no modeled returned value

Source

Unified Modeling Language 2.5.1

Note that the parentheses are not considered part of the output-argument list, so a reply-message-label without an output-argument-list may still optionally include an empty set of parentheses (“()”) after the message-name.

Source

Unified Modeling Language 2.5.1

If a reply-message-label does not include an output-argument-list and the Message has a signature, then this denotes that the Message has wildcard arguments corresponding to all out and inout ownedParameters of the signature Operation (if any).

Source

Unified Modeling Language 2.5.1

An output-argument always explicitly names the parameter to which it is to be matched. Any parameters that are not named are considered to have implicit wildcard arguments. (There is thus no need for an explicit wildcard notation for output-arguments.)

Source

Unified Modeling Language 2.5.1

If a reply Message does not have a signature, then the only argument that may be specified for it is a return argument as specified above. However, if the Message has a signature that is an Operation with out or inout ownedParameters, then ...

Source

Unified Modeling Language 2.5.1

If a reply Message does not have a signature, then the only argument that may be specified for it is a return argument as specified above.

Source

Unified Modeling Language 2.5.1

If the Message has a signature without a return parameter, then no assignment-target or value-specification may be given for the reply-message-label as a whole.

Source

Unified Modeling Language 2.5.1

If the Message has a signature that is an Operation with a return parameter, then this assignment-target and/or value-specification corresponds to the argument for that parameter (if no assignment-target is given, it is considered to be unknown).

Source

Unified Modeling Language 2.5.1

A reply-message-label may optionally have an assignment-target given to the left of the message-name, with a corresponding returned value denoted by the optional value-specification given after a colon at the end of the reply-message-label.

Source

Unified Modeling Language 2.5.1

decisionInputFlow : ObjectFlow [0..1] ... An additional ActivityEdge incoming to the DecisionNode that provides a decision input value for the guards ValueSpecifications on ActivityEdges outgoing from the DecisionNode.

Source

Unified Modeling Language 2.5.1

decisionInput : Behavior [0..1] ... A Behavior that is executed to provide an input to guard ValueSpecifications on ActivityEdges outgoing from the DecisionNode.

Source

Unified Modeling Language 2.5.1

In general, a ValueSpecification is a model element that is considered semantically to yield zero or more values.

Source

Unified Modeling Language 2.5.1

There is no ElementValue in UML-2.5.1 (although one has been proposed) it is an extension used by the MagicDraw tool family for handling tagged values

If the upperBound evaluates to *, then there is no limit on the number of tokens the ObjectNode may hold.

Source

Unified Modeling Language 2.5.1

If the removal of one or more tokens brings the number of tokens held below the evaluated upperBound, then the ObjectNode may accept any pending offers up to the limit of the upperBound.

Source

Unified Modeling Language 2.5.1

If the number of tokens already held by the ObjectNode is greater than or equal to the evaluated upperBound, then the ObjectNode shall not accept any further tokens until some of the ones it is holding are removed.

Source

Unified Modeling Language 2.5.1

An ObjectNode may not contain more tokens than specified by its upperBound, if any. If an ObjectNode has an upperBound, then this ValueSpecification shall evaluate to an UnlimitedNatural value. The upperBound is evaluated each time a token is offered ...

Source

Unified Modeling Language 2.5.1

Expressions are ValueSpecifications that specify values resulting from a computation.

Source

Unified Modeling Language 2.5.1

HOWTO set a ValueSpecificationAction to use the * LiteralUnlimitedNatural to drive an 'insertAt' InputPin on an AddStructuralFeatureValueAction in Cameo Simulation Toolkit and Cameo Systems Modeler

ValuePin – Value pins are excluded from fUML because they are redundant with using value specifications to specify values.

Source

Semantics of a Foundational Subset for Executable UML Models 1.4

Subscribe to ValueSpecification