StructuralFeature

Screencast: Cameo Simulation Toolkit: v19SP3: Analysis: When a Property is typed by an abstract Block an instance of a concrete specialising Block will automatically be created and assigned even when the lower multiplicity is 0

Keywords

Video style

This screencast video is an analysis of this suspected issue:

Cameo Simulation Toolkit: v19SP3: GOTCHA/BUG: When a Property is typed by an abstract Block an instance of a concrete specialising Block (where available) will automatically be created and assigned even when the lower multiplicity is 0

It also includes a nice demo of using an Activity and Actions to simulate instance creation and assignment in Magic Model Analyst^® (Cameo Simulatio

Read more about Screencast: Cameo Simulation Toolkit: v19SP3: Analysis: When a Property is typed by an abstract Block an instance of a concrete specialising Block will automatically be created and assigned even when the lower multiplicity is 0

Cameo Simulation Toolkit: v19SP3: GOTCHA/BUG: When a Property is typed by an abstract Block an instance of a concrete specialising Block (where available) will automatically be created and assigned even when the lower multiplicity is 0

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

Source

Unified Modeling Language 2.5.1

Slot::owningInstance : InstanceSpecification [1..1] ... The InstanceSpecification that owns this Slot.

Source

Unified Modeling Language 2.5.1

Slot::definingFeature : StructuralFeature [1..1] ... The StructuralFeature that specifies the values that may be held by the Slot.

Source

Unified Modeling Language 2.5.1

A Slot designates that an entity modeled by an InstanceSpecification has a value or values for a specific StructuralFeature.

Source

OMG Systems Modeling Language (SysML) 1.6

InstanceSpecification::slot : Slot [0..*] ... It is not necessary to model a Slot for every StructuralFeature, in which case the InstanceSpecification is a partial description.

Source

Unified Modeling Language 2.5.1

InstanceSpecification::slot : Slot [0..*] ... A Slot giving the value or values of a StructuralFeature of the instance. An InstanceSpecification can have one Slot per StructuralFeature of its Classifiers, including inherited features. ...

Source

Unified Modeling Language 2.5.1

Each block defines a collection of features to describe a system or other element of interest. These may include both structural and behavioral features, such as properties and operations, to represent the state of the system and behavior ...

Source

OMG Systems Modeling Language (SysML) 1.6

MagicDraw/Cameo 19SP3: Does not yet handle Feature-wise validation of provided/required DirectedFeature contracts (it only handles them at the level of entire Block types). Webel asserts the spec is inconsistent w.r.t. ProxyPort connection compatibility.

SysMLv1.6 Provided/required DirectedFeature contracts for ProxyPorts SHOULD be satisfiable Feature-wise (including as subsets of Features) not necessarily just at the level of entire Blocks (types)! [See also the SysMLv1.7 spec changes.]

Using an InstanceValue in a ValueSpecificationAction is similar to creating an instance using a CreateObjectAction, except that values may be given for the StructuralFeatures of the instance using slots on the InstanceSpecification of the InstanceValue.

Source

Unified Modeling Language 2.5.1

SysML: Naming: Always use either anonymous or first letter lower case for Property, ObjectNode and InstanceSpecification names; no exceptions (unless using names to "quote text")! Valid: 'lowerCamelCase' OR 'tla' vs TLA acronym OR 'uCC' vs UpperCamelCase

The append(n:int) operation and its Activity method Append

Gallery

Tutorial

HOWTO simulate UML-2.5.1 'Figure 14.7 Composite State with two States' in Cameo Simulation Toolkit - Operation-driven Transition case study

Section

Slide kind

UML Activity Diagram

The Connect Activity

Gallery

Tutorial

HOWTO simulate UML-2.5.1 'Figure 14.7 Composite State with two States' in Cameo Simulation Toolkit - Operation-driven Transition case study

Section

Slide kind

UML Activity Diagram

The semantics are undefined for adding a value that violates the upper multiplicity of the StructuralFeature, and for adding a new value to a StructuralFeature with isReadonly=true after initialization of the object that would have the value.

Source

Unified Modeling Language 2.5.1

The insertion point is ignored if it is used when isReplaceAll=true.

Source

Unified Modeling Language 2.5.1

Reinserting an existing value at a new position in an ordered, unique StructuralFeature moves the value to that position (this works because such StructuralFeature values are ordered sets).

Source

Unified Modeling Language 2.5.1

The semantics are undefined for a value of 0 or an integer greater than the number of existing values

Source

Unified Modeling Language 2.5.1

A value of unlimited (“*”) for the insertion point means to insert the new value at the end of the sequence.

Source

Unified Modeling Language 2.5.1

An insertion point that is a positive integer less than or equal to the current number of values means to insert the new value at that position in the sequence of existing values, with the integer 1 meaning the new value will be first in the sequence.

Source

Unified Modeling Language 2.5.1

If the insertAt InputPin is present, it has type UnlimitedNatural and multiplicity 1..1

Source

Unified Modeling Language 2.5.1

NOTE. Values of StructuralFeatures may be ordered even if the upper multiplicity is 1.

Source

Unified Modeling Language 2.5.1

Adding a value to an ordered StructuralFeature requires an insertion point for the new value given in the insertAt InputPin, which is required for ordered StructuralFeatures when isReplaceAll is false and omitted for unordered StructuralFeatures.

Source

Unified Modeling Language 2.5.1

If isReplaceAll is false and the StructuralFeature is unordered and unique, then adding a value that is already contained in the StructuralFeature has no effect.

Source

Unified Modeling Language 2.5.1

If isReplaceAll is true ... The StructuralFeature always has a single value when the Action completes, even if the lower multiplicity of the StructuralFeature is greater than 1.

Source

Unified Modeling Language 2.5.1

If isReplaceAll is true, then the existing values of the StructuralFeature are removed before the new value is added, except if the StructuralFeature already contains the new value, in which case it is not removed under this option.

Source

Unified Modeling Language 2.5.1

If the StructuralFeature is an Association end, the semantics are the same as for a CreateLinkAction ..., where the participants in the link are the object being acted on and the new value.

Source

Unified Modeling Language 2.5.1

The value to be added is given on the value InputPin, which is required. This InputPin has the same type as the StructuralFeature and a multiplicity of 1..1 (that is, a single value is added).

Source

Unified Modeling Language 2.5.1

16.8.3.3 Add Structural Feature Value Actions: An AddStructuralFeatureValueAction is a StructuralFeatureAction for adding a value to a StructuralFeature of an object.

Source

Unified Modeling Language 2.5.1

Features represent structural and behavioral characteristics of Classifiers.

Source

Unified Modeling Language 2.5.1

Subscribe to StructuralFeature