Cameo Simulation Toolkit: You can assign the results of simulations calculations on instances to the default values of properties of the Classes/Blocks that type the instance.
AmbientConvectionCapacitance (combined) Gallery Tutorial TRAIL: SysML+SysPhS vs Modelica By Example in MagicDraw/Cameo SysML [tested with the Wolfram SystemsModeler for Modelica] Section 07. Components [MOST] Slide kind hybrid diagram SysML Block Definition Diagram (BDD) SysML Internal Block Diagram (IBD)
Cameo Simulation Toolkit v19SP3: The "hover" feature for showing values of objects may show duplicates if there are redefined value properties.
Figure 27: Default values and initial value in SysML Gallery Tutorial TRAIL: SysPhS-1.1 specification body figures in MagicDraw/Cameo SysML vs Modelica [using Wolfram SystemsModeler] Section Slide kind hybrid diagram SysML Block Definition Diagram (BDD) SysML Parametric Diagram
UML/SysML: During modelling it can really help to create little instance (object) diagrams as you go! This can also help communicate with non-SysML stakeholders.
21: Example instances for 'asset' This content has been marked as discussing an ADVANCED topic! Gallery Tutorial TRAIL: A SysML Pattern for Digital Twinning Section Slide kind hybrid diagram SysML Package Diagram UML Object diagram
13: PipeDigitalTwin instances Gallery Tutorial TRAIL: A SysML Pattern for Digital Twinning Section Slide kind SysML Block Definition Diagram (BDD) UML Object diagram
05: Twin instances Gallery Tutorial TRAIL: A SysML Pattern for Digital Twinning Section Slide kind SysML Block Definition Diagram (BDD) UML Object diagram
Trade(-off) study for Client with A1 and A2 instances (dependency injection) Gallery Tutorial TRAIL: HOWTO simulate Dependency Injection of SysML Parametric calculations Section Slide kind hybrid diagram SysML Block Definition Diagram (BDD) SysML Internal Block Diagram (IBD)
Executable instance tables for Client with A1 and A2 instances (dependency injection) Gallery Tutorial TRAIL: HOWTO simulate Dependency Injection of SysML Parametric calculations Section Slide kind MagicDraw/Cameo: table table
Executable instance tables for A1 and A2 (concrete implementations of I_A) Gallery Tutorial TRAIL: HOWTO simulate Dependency Injection of SysML Parametric calculations Section Slide kind MagicDraw/Cameo: table table
Updated focus BDD for Lepton including charge Gallery Tutorial TRAIL: Webel SysML Parsing Analysis example: A particle physics taxonomy from Wikipedia Section Slide kind SysML Block Definition Diagram (BDD)
InstanceSpecifications with links and Slots 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 Class Diagram
Visual nesting of InstanceSpecification symbols has no meaning in the underlying model, only assignment to a Slot does!
InstanceSpecification::specification : ValueSpecification [0..1] ... A specification of how to compute, derive, or construct the instance. Source Unified Modeling Language 2.5.1
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
InstanceSpecification::classifer : Classifier [0..*] ... The Classifier or Classifiers of the represented instance. If multiple Classifiers are specified, the instance is classified by all of them. Source Unified Modeling Language 2.5.1
An InstanceSpecification can act as a DeploymentTarget in a Deployment relationship, in the case that it represents an instance of a Node. It can also act as a DeployedArtifact, if it represents an instance of an Artifact. Source Unified Modeling Language 2.5.1
An InstanceSpecification is a model element that represents an instance in a modeled system. Source Unified Modeling Language 2.5.1
MagicDraw/Cameo: When you create an InstanceSpecification in a diagram it will a Select Classifier dialog. It is often faster to Cancel that and then just drag a Classifier onto the instance symbol from the diagram or model tree.
In contrast to Associations, which specify links between any instance of the associated Classifiers, Connectors specify links between instances playing the connected parts only. Source Unified Modeling Language 2.5.1
A Connector specifies links that enables communication between two or more instances. Source Unified Modeling Language 2.5.1
A ConnectorEnd is an endpoint of a Connector, which attaches the Connector to a ConnectableElement. Source Unified Modeling Language 2.5.1
Each Connector may be attached to two or more ConnectableElements, each representing a set of instances that contribute to the instantiation of the containing StructuredClassifier. Source Unified Modeling Language 2.5.1
In contrast to Associations, which specify links between any suitably-typed instance of the associated Classifiers, Connectors specify links between instances playing the connected roles only. Source Unified Modeling Language 2.5.1
Each link may be realized by something as simple as a pointer or by something as complex as a network connection, and may represent the possibility of instances being able to communicate because their identities are known by virtue of being passed in ... Source Unified Modeling Language 2.5.1
A Connector specifies links ... between two or more instances playing owned or inherited roles within a StructuredClassifier. Source Unified Modeling Language 2.5.1
If the properties at the ends of a binding connector are typed by a Block, the connector specifies that the instances of the properties shall refer to the same block instance. Source OMG Systems Modeling Language (SysML) 1.6
ObjectNodes may also specify an inState set of States. If such a set is specified, then any object token held by the ObjectNode shall have a value with a type that has or inherits a StateMachine as its classifierBehavior that has all of the states .. Source Unified Modeling Language 2.5.1
