ISSUE

Some identified tool and specification issues are tracked here by Webel IT Australia as public pages for educational purposes, linked to relevant content such as tutorial slides. In most cases, issues are also reported to the tool vendors and specification bodies. The public tracking of selected issues is performed here with the most constructive intentions. The relevant tool vendors and specification bodies are not responsible for the accuracy of claims made on this site concerning tool performance or specification consistency.

SysML1.7: ISSUE: Claim that 'Datastore already has an overwrite semantics' is inconsistent w.r.t. UML2.5.1

SysMLv1: CAUTION: The notation and recommended use for PropertySpecificType changed significantly between SysMLv1.2 and SysMLv1.7. And the spec itself does not seem to use the new notation (which is also not supported by Cameo Systems Modeler v2024x)

ISSUE: Mathematica (v14.1): Known Apple BUG: macOS Ventura: M1 Max/Silicon: Export to ProRes is buggy! WORKAROUND: To use transparency, export to PNG then use Mac Compressor or Handbrake to convert to ProRes4444

ISSUE: Postman (v11.27.4): The (Mac) Desktop version does not always offer the Output block in a Flow patch

ISSUE: Postman (v11.27.4): You can access the underlying Request settings of a Request block in a Flow easily using the little angled arrow at the top of the Request block title, but getting back to the client Flow is cumbersome.

ISSUE: Postman (v11.27.4): Sometimes "stalls" with an incomplete flashing view of the loaded API after uploading a new OpenAPI v3.1 JSON definition file. WORKAROUND: Restart Postman

ISSUE: Postman (v11.27.4): An OpenAPI v3.1 JSON definition file upload does not always "catch". WORKAROUND: Toggle to OpenAPI v3.0 mode then back to OpenAPI v3.1

ISSUE: Cameo Simulation Toolkit: v2024x: Although does not respect inheritance of attributes of Signals on SendSignalAction or un-marshalling AcceptEventAction DOES require them on 'effect' Behaviors.

SysMLv1: Cameo Simulation Toolkit: GOTCHA: Do not use Associations with Signal attributes, they will become null when fed as argument values for Parameters of 'effect' Behaviors of Transitions

SysMLv1.7/fUMLv1.4: Cameo Simulation Toolkit v2024x: Using an extending Enumeration literal as a parameter argument value runs but a WARN is issued.

ISSUE: Cameo Simulation Toolkit: v2024x: Does not show argument Pins corresponding to inherited attributes of Signal on SendSignalAction or an un-marshalling AcceptEventAction. No known UML2.5.1 or fUML-1.4 constraint; no obvious tool display option.

Webel: SysMLv1: MagicDraw/Cameo: CON: Using anonymous property and/or action names is not ideal for Element Compartment and Note callout displays when Usage level allocation is used. But allocation table and matrix views are better anyway.

Mathematica: GOTCHA: The Problems Analysis review system of Mathematica Plugin for IntelliJ IDEA reports a declared Module variable used as a Table loop variable as an "Used local variable". DO NOT SIMPLY DELETE IT!

UML/SysML: MagicDraw/Cameo: Edit Compartments: ActivityParameterNode: Can't select the 'parameter::multiplicity'? Run the synchronisation between the Activity in the direction Synchronize Activity Parameter Nodes by Activity Parameter then try again!

Mathematica: TIP: Notebooks: Automatic Cell Grouping driving you up the wall? Try Manual Grouping and make it part of your workflow!

ISSUE/GOTCHA: MagicDraw/Cameo v2022x: UML/SysML: If you "rename" an ActivityParameterNode symbol on the frame of an Activity Diagram it actually renames the underlying Parameter (only) NOT the name of the ActivityParameterNode element!

Webel: SysML4Mathematica: Cameo Systems Modeler: Can perform calculations with a custom Quantity ValueType (for Mathematica) directly, but DOES NOT perform units-aware algebra (no automatic conversions)

Mathematica: Notebooks: Automatic Cell Grouping mode can be a "royal pain", turn it off by setting Cell > Grouping > Manual Grouping

ISSUE: MagicDraw/Cameo: v2022x Golden, v2022xRefresh1: Comment can't connect anchor to another Comment as annotatedElement

[FIXED in v2022Refresh1]: BUG: MagicDraw/Cameo: 19SP3/v2022xGolden: Activity Diagrams: Pin display mode 'Position of Labels' does not stick, label positions in Diagrams have sometimes moved after re-opening a project [and "FIX"]

Mathematica: Wolfram Player Pro 13.1: NotebookDelete[] does not work

Mathematica: GOTCHA: Print[] from Manipulate always goes to the Messages console notebook

MagicDraw SysML: [v2022xGolden,v2022xRefresh1]: ISSUE: Automatic assignment of the Type of the 'result' of a ReadStructuralFeatureAction not working with drag & drop.

The integration between Wolfram Workbench and Mathematica is partly gammy (as of latest versions 2022-08-23)

Mathematica: ISSUE with all Entity operations on MMAv13.0.0.0 vs macOS Monterey 12.3 or 12.4 ["solved" by upgrade to MMA 13.1.0.0]

MagicDraw/Cameo: 2022xGolden: TIP/GOTCHA: Mac: HOWTO Load the available plugins in the Resource/Plugin Manager

CoolProp: Mathematica: Mac: HOWTO get CoolProp for Mathematica running on Apple M1 Max and Mathematica13

Mathematica: Use of UnitConvert (or even just multiplication or division by a unit Quantity) MASSIVELY slows the calculations down!

Mathematica: Compile won't work with a Quantity with units

CoolProp: HOWTO reproduce a pressure vs specific enthalpy chart in Mathematica. Example: R32 refrigerant.

CoolProp: LIMITATION: DOES NOT accept specific enthalpy 'H' and vapor quality 'Q' as input pairs

Mathematica: CoolProp wrapper binaries don't seem to be maintained past CoolProp 5.1.1 (and the PhaseSI and 2-args Props1SI functions do not work)

Mathematica: MTools: Argument Pattern strong type matching does not intrinsically respect inheritance (makes implementing design-by-contract and some Design Patterns less convenient). But you can use PatternTests with Webel MAll extensions.

Mathematica: Wolfram Workbench: Basic variable name refactoring is not supported. (Or just use the IntelliJ IDEA Plugin for Mathematica, which does variable and function renaming well.)

Mathematica: Wolfram Workbench: Sometimes the Outline view gets completely out of sync with the .m or .wl Package code

Mathematica: Wolfram Workbench: Sometimes the code syntax checking goes haywire (with red nearly everywhere) for no good reason (even when the code load and runs fine in Mathematica). WORKAROUND: Just restart Eclipse.

Wolfram Workbench for Mathematica: Limitation: Using more than one '$' sign within function names blocks navigation on function usages.

Mathematica: GOTCHA: EntityFunction can only return a scalar.

Mathematica: Some links on Object-Orientation (or the lack thereof)

GOTCHA/BUG: Cameo Simulation Toolkit v2021xR1 + Mathematica: Delegation to Mathematica from ConstraintBlocks FAILS if any of the input or output parameters are larger than 99999 because they get interpreted as 1.0e5 and that trips something! Aarrrggggh!

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

MagicDraw/Cameo 19SP3/v2022xGolden: [FIXED in v2022xRefresh1]: Activity Diagrams: Pin display mode 'Position of Labels' does not work correctly for 'Name And Type Labels Inside', only shows the Name inside (not the Label) [and WORKAROUND]

UML/SysML: MagicDraw/Cameo: 19SP3: Instance Table Diagram sometimes does not display the values for nested value properties

MagicDraw/Cameo: 19SP3: Although a 0..* or 1..* Property can carry more than one value, the interface only permits assignment of a single Property::defaultValue through the specification dialog

UML: Cameo Simulation Toolkit 19SP3: GOTCHA: CreateObjectAction ignores an Artifact as 'classifier' even though Artifact is a Classifier

UML/SysML: Cameo Simulation Toolkit 19SP3: A parent Activity with a DecisionNode that uses a Activity as a decisionInput Behavior terminates immediately after the decisionInput terminates (but OpaqueBehavior works)

UML/SysML: Cameo Simulation Toolkit 19SP3: GOTCHA: Will not evaluate a guard using a token from a decisionInputFlow UNLESS a decisionInput Behaviour is explicitly defined (but Alf does)

UML/SysML: MagicDraw/Cameo: WARNING: If you assign a value to a Slot for an untyped Property then assign a ValueType later it will DELETE your assigned value! Assign a type first .

The SysML1.6 derived /tracedTo is only available on AbstractRequirement (but in MagicDraw/Cameo you can use derived relationships to achieve the same thing on other kinds of NamedElement).

The UML «Trace» and SysML Trace can't be applied to a Slot as target (because Slot is just an Element, not a NamedElement).

MagicDraw/Cameo v19SP3: The display of units can't be disabled on the initialValues compartment for context-specific values, which can lead to inconsistencies when an OpaqueExpression that references value property names is used.

MagicDraw/Cameo v19SP3: vs SysPhS-1.1: OpaqueExpression for Slot value exports to Modelica as 'null' if only uses a single variable. WORKAROUND/HACK prefix the variable with '1 *' [FIXED in v2021x]

SysPhS vs Modelica: If you redeclare a PhSConstant (Modelica parameter) as a PhSVariable (Modelica variable) Modelica still treats it as a 'parameter'. You can end up with an unbalanced system with one equation too many!

SysPhS-1.1: Does not support Modelica's encapsulated enumeration.

SysPhS-1.1: Does not support Modelica's conditional declaration form.

MagicDraw/Cameo v19SP3: vs SysPhS-1.1: Modelica export: Direct binding from a PhSVariable value property within a FlowProperty of a Port to an inner value property does not flatten. WORKAROUND: Use an intermediate constraint property.

MagicDraw/Cameo v19SP3: Does not support display of context-specific values on a FlowProperty symbol within a Port in an IBD

MagicDraw/Cameo v19SP3+SysPhS-1.1: On export to Modelica sometimes repeats parts of an equation into an extending model.

MagicDraw/Cameo v19SP3+SysPhS-1.1: Does not cleanly export INLINE Modelica 'if/then/else' statements (a.k.a. "switching" form)

MagicDraw/Cameo v19SP3+SysPhS-1.1: Does not cleanly export Modelica 'when/then' statements

Webel vs SysPhS-1.1: Modelica: Suggest need option to NOT always set a 'start' value also as 'fixed' (especially where 'initial equation' is not supported)

SysPhS: MagicDraw/Cameo v19SP3: Export to Modelica does not interpret as 'start' the default on a PhSVariable assigned via ElementValue to a PhSConstant

MagicDraw/Cameo: GOTCHA: When applying a numerical default to a value property make sure the value property has already been typed by Real or Integer (or a ValueType that extends one of them) otherwise it will assign a LiteralString as default.

SysPhSLibrary and ISO-80000 ModelLibrary: Some ValueType names and Unit symbols are not Modelica-friendly

SysPhS-1.1: Does not support Modelica's 'min' or 'max' on type declarations

MagicDraw/Cameo v19SP3: SysPhS: If you have a custom ValueType it MUST extend Real either directly or indirectly or it will not be seen on export to Modelica.

SysPhS-1.1: Does not support Modelica's 'experiment' annotations

SysPhS-1.1: Does not support Modelica's 'initial equation'. WORKAROUND: One can often achieve the same by directly setting a default on a variable and/or by using additional variables/parameters with 'start' and additional equations.

Cameo Simulation Toolkit v19SP3: The "hover" feature for showing values of objects may show duplicates if there are redefined value properties.

Webel: Cameo Simulation Toolkit v19SP3/v2024x: Could not get ReclassifyObjectAction to work (yet)

Wolfram SystemModeler: Not clear how to draw a connect that already exists in the Modelica code

MagicDraw/Cameo v19SP3 vs SysML&SysPhS: Export to Modelica: The exported layout annotations appear to be completely broken (at least vs Wolfram SystemModeler) just de-select generation of them on export.

GOTCHA: MagicDraw SysML/Cameo 19SP3: Export to Modelica: The name of a redefining Property must be exactly the same as the Property it redefines or it will not export properly!

Webel vs SysPhS-1.1: Annex A.5: Humidifier: The water temperature from TemperatureIncreaseConstraint and HeatingCalculationConstraint starts at 0 °C (should probably be the environment temperature 20 °C). Needs an additional parameter and initial value.

Webel vs SysPhS-1.1: Annex A.5: Humidifier: Dimensional analysis of VaporPressureCalculationConstraint implies each 1 mL of water is equated with EXACTLY 1 g of produced vapor.

Webel vs SysPhS-1.1: Annex A.5: Humidifier: Dimensional analysis of VaporPressureCalculationConstraint implies the output is a pressure rate, which makes no sense as consumed by RelativeHumidityCalculation and is inconsistent with the rest of the system.

SysPhS-1.1: Annex A.5: The BDD Figure 74 and Parametric Diagram Figure 84 for block RelativeHumidityCalculationConstraint are missing PhSConstant 'c2'. Compare with the constraint {der(x)=((press/satVap)-change)/c2} in BDD Figure 79.

MagicDraw SysML/Cameo 19SP3: Sometimes on application of an ItemFlow to a Connector with Ports typed by Blocks or InterfaceBlocks that have a FlowProperty of the same type (but different direction) it shows two ItemFlow arrows

SysPhS-1.1: Annex A.5: p.89: Figure 75: Humidifier blocks, ports, & component properties. Typo in name of value property 'litpSec2mLiptHr:Real' on WaterTank should be 'litpSec2mLitpHr:Real' (breaks export of redefining Property with correct name).

MagicDraw/Cameo v19SP3 vs SysML&SysPhS: The sample project for the Humidifier example uses DEPRECATED FlowPorts (and sets values directly on them in the StateMachines).

MagicDraw/Cameo v19SP3 vs SysML&SysPhS: GOTCHA: Will NOT correctly export a SysML-1.6 «~interfaceBlock» to Modelica (but does cope with a tilde ~ prefix in the name of a plain InterfaceBlock)

MagicDraw/Cameo vs SysML&SysPhS: GOTCHA: Will NOT export a non-normative System «system» block to Modelica, it only recognises a plain Block «block»!

SysPhS-1.1: Annex A.5: Typo in Figure 98 redefining value property 'C2 : Time = 1.0{redefines C2,unit = second}', should be lower case 'c2' (compare with BDD Figure 79)

SysPhS-1.1: Annex A.5: 'Figure 101: Heating Scenario Initial Values': HeatingCalculation1: no such value to redefine 'C1 : Time = 1.0{redefines C1,unit = second}', should be 'xIntg : Real' (compare with BDD Figure 77 and Parametric diagram Figure 88)

SysPhS-1.1: Annex A.5: redefinition 'humidifierSystem {redefines humidifierSystem}' incorrect in Figure 96: Humidifier System Scenario Initial Values

SysPhS-1.1: RelativeHumidityScenario1: Figure 98: Relative Humidiity Scenario Initial Values: RelativeHumidity should be RelativeHumidity1

SysPhS-1.1: Annex A.5: Humidifier: Constraints on HeatingCalculationConstraint not consistent between BDD Figure 79 and Par Figure 88 (does not have 'c1')

SysPhS-1.1: Annex A.5: Humidifier: Constraints on RelativeHumidityCalculationConstraint not consistent between BDD Figure 79 and Par Figure 84 (does not have 'c2')

SysPhS-1.1: Annex A.5: Humidifier: Use of UML-style direct Port conjugation not permitted since SysML-1.6, prefer ~InterfaceBlock type-based conjugation (example requires migration)

SysPhS-1.1: Annex A.5: Humidifier: Naming not very consistent across parts, input/output Port name, value properties, or constraint parameters

MagicDraw/Cameo: v19SP3: Property created by dragging onto a Class or Block a symbol of a Classifier named with a single letter capital name 'N' has a poor name 'N:N'

There is no «port» stereotype keyword for Port or Property in UML-2.5.1 or SysML-1.6. It is assumed to be introduced in some SysML and SysPhS specification diagrams as a custom or user-defined stereotype for special illustration purposes.

SysPhS-1.1: Apparent use of part Property with «port» keyword (instead of standard SysML Port) leads to property path symbols appearing inside the boundary of context blocks (instead of within a Port symbol on the boundary) in IBDs and Parametric Diagrams

SysPhS-1.1: p.81: 'resistance:ViscousResistance' (in Figure 60) has to be treated as a PhSVariable not a PhSConstant, otherwise get an invalid system with 6 variables and 7 equations.

SysPhS-1.1: The correct ValueTypes should be used throughout instead of just Real for constraint parameters in 'Figure 61: Hydraulics model constraint blocks'

SysPhS-1.1 spec version of 'Figure 48: Internal structure of the signal processor' shows an ItemFlow for Real on an overlapping Connector line section, which is impossible to interpret.

SysPhS-1.1: The correct ValueTypes for Current, Voltage, Resistance, Capacitance, and Inductance should be used throughout instead of just Real in 'Figure 40: Circuit constraint blocks'

SysPhS-1.1 spec version of 'Figure 38: Internal structure of the circuit example' shows some bi-directional ItemFlows for Charge on overlapping Connector line sections, which are impossible to interpret.

GOTCHA: A SysML/SysPhS Connector (or Modelica connection) in an electronics model is NOT a wire! It's a contract between connected Ports.

Webel vs SysPhS-1.1: Diagramming style: DO NOT recommend overlapping Connectors as shown in 'Figure 38: Internal structure of the circuit example'

SysPhS-1.1: Suggest use connector forms 'Modelica.Blocks.Interfaces.RealInput u;' and 'Modelica.Blocks.Interfaces.RealOutput y;' not 'input Real u;' and 'output Real y;' in Modelica code examples (otherwise not connectable).

SysPhS-1.1: p.38: 10.9.4 Modelica modeling, signal flow: Suggest kick start Spring with something like 'position=5' (otherwise get flat line when run).

SysPhS-1.1: p.38: 10.9.4 Modelica modeling, signal flow: Modelica code: the equation 'der(velocity)=(u-springcst*position)/m;' should use variable 'mass' not 'm'

MDSysML/Cameo 19SP3: SysPhSLibrary vs SysPhS-1.1: RealVectorSignalIn2Element extends RealVectorSignalElement not RealVectorSignalInElement, RealVectorSignalOut2Element extends RealVectorSignalElement not RealVectorSignalOutElement (and so on)

MDSysML/Cameo 19SP3: Showing stereotype keywords on FlowProperty rows is UNSUPPORTED

MDSysML/Cameo 19SP3: The SysPhS versions of Conductance, Frequency, siemens, and hertz, are not explicitly provided in the MagicDraw/Cameo model library

MDSysML/Cameo 19SP3: SysPhSLibrary vs SysPhS-1.1: Does not represent the elements in 'Figure 32: Elements for signal flows of electrical quantities'

SysPhS-1.1: p.60: table for routing components: row for Switch: equivalents Modelica.Blocks.Logical.Switch (for Modelica) and Switch (for Simulink) missing

SysPhS-1.1: Use of 'Criteria = u2~=0' for Simulink for Real.Routing.Switch::u2 inconsistent with BooleanInput of control port Modelica.Blocks.Logical.Switch::u2

SysPhS-1.1 (and MDSysML/Cameo 19SP3 SysPhSLibrary): Use of RealSignalInElement for Real.Routing.Switch::u2 inconsistent with BooleanInput of control port Modelica.Blocks.Logical.Switch::u2

MDSysML/Cameo 19SP3: SysPhSLibrary vs SysPhS-1.1: SourceAndSink.Constant: Wrong Real (UML version not SysML version) has been used for 'k', so sorts in the 'properties' compartment instead of the 'values' compartment

SysPhS-1.1: p.57: Table 11.3.2.5 Mathematical components: Modelica Parameters for the Subtraction row should indicate (k1 and) k2 required to achieve subtraction via Math.Add (or the correct exported values should be explained).

MDSysML/Cameo 19SP3: SysPhSLibrary vs SysPhS-1.1: Mathematical.Subtraction: Wrong Real (UML version not SysML version) has been used for 'k2', so sorts in the 'properties' compartment instead of the 'values' compartment

MDSysML/Cameo 19SP3: SysPhSLibrary vs SysPhS-1.1: Mathematical.Gain: Wrong Real (UML version not SysML version) has been used for 'gain', so sorts in the 'properties' compartment instead of the 'values' compartment

MDSysML/Cameo 19SP3: SysPhSLibrary vs SysPhS-1.1: SPELLING/TYPO: VariableDelay: parameter 'maxDelay' should be 'delayMax'

MDSysML/Cameo 19SP3: SysPhSLibrary vs SysPhS-1.1: Continuous.Integrator is missing the 'init' PhSConstant (maps to y_start in Modelica)

MDSysML/Cameo 19SP3: SysPhSLibrary vs SysPhS-1.1: NonLinear.Saturation: Wrong Real (UML version not SysML version) has been used for 'lower' and 'upper', so sorts in the 'properties' compartment instead of the 'values' compartment

MDSysML/Cameo 19SP3 vs SysPhS-1.1: The Continuous.TransferFunction and Discrete.TransferFunction have Ports 'u : RealVectorSignalInElement [1]' or '[]' and 'y : RealVectorSignalInElement [1]' or '[] instead of RealSignalInElement/RealSignalOutElement

SysPhS-1.1: p.30: text and Figure 22: Incorrect references to 'RealInSignalElement' and 'RealOutSignalElement' (should be RealSignalInElement, RealSignalOutElement)

SysPhS-1.1: p.53: Figure 30: Incorrect references to RealInSignalElement, RealOutSignalElement, IntegerInSignalElement, IntegerOutSignalElement, BooleanInSignalElement, BooleanOutSignalElement (should be RealSignalInElement, RealSignalOutElement, ...)

As of 2021-01-11 OpenModelica no longer has DMG install bundles for Mac, and currently does NOT install on Mac Big Sur using MacPorts!

SysPhS-1.1: p.47: 10.12.2 SysML modeling: The states StandBy and On in 'Figure 29: State machine in SysML' should probably use 'entry' not 'doActivity'.

SysPhS-1.1: p.47: 10.12.2 SysML modeling: References to 'u.sigsp' and 'y.usigsp' should be 'u.rSig' and 'y.rSig'.

SysPhS-1.1: p.47: 10.12.2 SysML modeling: TYPO: Incorrect spelling of RealInSignalElement (should be RealSignalInElement) and RealOutSignalElement (should be RealSignalOutElement)

SysPhS-1.1: 10.12.2 SysML modeling: p.47, p.48: References to .sig and .rsig in 'Figure 29: State machine in SysML' and Modelica code example should be .rSig

SysPhS-1.1: 10.12.2 SysML modeling: p.47: Name of StateMachine in 'Figure 29: State machine in SysML' should be ComputerSM (not Computer) for consistency with the Modelica code example

SysPhS-1.1: p.45: 10.11.2 SysML modeling: Reference to 'the units library in Figure 20, Subclause 11.2.2' is wrong

SysPhS-1.1: p.44: 10.10.3 Modelica modeling: Reference to 'The following Modelica code corresponds to Figure 15' should probably be 'to Figure 27'.

SysPhS-1.1: p.42: 10.9.8 Modelica modeling, physical interaction: Modelica code has 'forcediff=springcstlengthchg;' should be 'forcethru=springcstlengthchg;'

GOTCHA: MagicDraw SysML/Cameo 19SP3: Export to Modelica: 'entry', 'doActivity', or 'exit' Behaviors of a State must be directly owned (not just "wrapped") or they won't be seen on export!

SysPhS-1.1: p.41: 10.9.8 Modelica modeling, physical interaction: Reference to 'the bindings in Figure 14' should probably be 'the bindings in Figure 26'.

SysML-1.6: p.43: 8.3.1.2.1 Property types 'Four general categories of properties of blocks are recognized in SysML ...' does not cover FlowProperty

SysML-16: Taken literally the text and OCL of constraint 'Block::6_valueproperties_composite' imply that every FlowProperty typed by a ValueType should have AggregationKind 'composite'

MDSysML/Cameo: 19SP3: SysPhSLibrary: Has value properties with aggregation kind 'none'

MDSysML19SP3: Validation engine does not report value properties with AggregationKind other than composite

SysPhS-1.1: Typos: Numerous references to 'rsig' lower case should be 'rSig' (including Figure 25 and Figure 29)

SysPhS-1.1: p.38: 10.9.4 Modelica modeling, signal flow: Modelica code: the keyword should be 'equation' not 'equations'.

SysPhS-1.1: p.38: 10.9.4 Modelica modeling, signal flow: Example Modelica model should be for SpringMassSys not Spring

SysPhS-1.1: [TRIVIAL] p.11: If property 'm:Mass' is named then ':Ground' should also be named for consistency in 'Figure 2: Association block with internal structure and connector properties in SysML'

SysPhS-1.1: p.28: 10.6.3 Modelica modeling: An assigned value “...” is shown for v3 in the Modelica code but none is shown in the SysML model in 'Figure 21: PhSVariables and PhSConstant in SysML' (and “...” is not compatible with Real).

MagicDraw SysML/Cameo: 19SP3: Does not seem to support export to Modelica from a Package [use a SysML Block as root instead]

SysPhS-1.1: p.32: 10.7.8 Modelica modeling, physical interaction: Type Real for 'f' and 'lV' in example Modelica code for Spring do not correspond to 'Figure 23: Ports for physical interaction in SysML', should be Force and Velocity.

SysPhS-1.1: p.30: 10.7.4 Modelica modeling, signal flow: Example Modelica code for Spring corresponding to 'Figure 22: Ports for signal flow in SysML' is invalid [should probably be 'input Real u;' and 'output Real y;' not 'in ...' and 'out ...']

MagicDraw SysML/Cameo: 19SP3: Export to Modelica from TestBed (for SignalProcessor) sample does not validate in Wolfram SystemModeler

MagicDraw SysML/Cameo: 19SP3: Export to Modelica from SysPhS sample for HumidifierSystem does not execute in Wolfram SystemModeler Simulation Centre

SysML-1.6: Figure 8-17: Redefined properties in Vehicle Model 1 and Vehicle Model 2 break constraint: 'BoundReferences shall not be applied to properties that are related by redefinition to other properties with BoundReference applied'

BUG: Cameo Simulation Toolkit 19SP3: StateMachine: Crashes with an irrelevant "memory error" report if you fire a signal Trigger during execution of an 'entry' Activity with a timer

UML-2.5.1 does NOT permit a trigger or guard on a Transition from an initial pseudostate in a StateMachine but Cameo/MagicDraw does (please avoid).

The markup of Snippet page titles on this CMS web site is sometimes restricted (especially concerning subscripts and superscripts such as used in mathematical and scientific notation). Visit the linked Snippet page for the quote with full markup.

MagicDraw/Cameo: The tagged values HTML editor can't handle overlines or all macrons.

MagicDraw/Cameo: HOWTO share a "Block-to-Block" ItemFlow - that was created by 'Between Part Types' mode - between two Connectors. (FYI only, not a Webel-recommended technique.)

SysMLv1: MagicDraw/Cameo: If redisplay of an Association with an InformationFlow or ItemFlow creates a strange extra dashed line with «ItemFlow» keywords (separate from the Association) just remove (only) that extra dashed line from the diagram.

UML-2.5.1 refers to 'isTestFirst' in 16.11.3.4 but to isTestedFirst in the attributes list for LoopNode under 16.14.30.4 Attributes

SysML-1.6: The provided/required Interfaces indicated in the spec version of D.19 for 'connector c1 in Figure D.19.' are not defined on the corresponding Block in Figure D.20 (known issue)

UML-2.5.1: Has an incorrect local Transition with same source and vertex in 'Figure 14.34 Local Transitions'

MagicDraw/Cameo: The ordering of feature in a SysML IBD :features compartment may differ from that in its defining Block (and there are no corresponding display options for controlling sorting).

MagicDraw/Cameo: BUG: Sometimes the 'Show Inherited' display feature does not work immediately on Class and Block compartments or SysML IBD :features compartments unless you toggle a compartment (close then re-open it).

MagicDraw/Cameo: The display option 'Show Value Type Units' does not seem to work on the Slots of an InstanceSpecification in a BDD

MagicDraw/Cameo v19SP3: uses the Block compartment name 'signal receptions' instead of just 'receptions'. [CLAIMED FIXED in v2021x]

MagicDraw/Cameo 19SP3: Stakeholder: Has 'concern' NOT derived and /concernList derived; SysML-1.6 has /concern derived and concernList NOT derived.

MagicDraw/Cameo: The apparent grouping of member elements under an ElementGroup node in the model tree can cause complications for searching and for the Cameo Collaborator exports.

SysML-1.6: The constraint that ''An Action appearing in an “AllocateActivityPartition” shall be the /client (from) end of an “allocate” dependency.' is not compatible with all Activity Diagram swimlane configurations.

MagicDraw/Cameo 19SP3: The property path in callout does always correspond to the SysML spec examples.

MagicDraw/Cameo 19SP3: uses PascalCase instead of lowerCamelCase on some SysML compartment names

SysML-1.6: AbstractRequirement: direction of /tracedTo wrong in Attributes description

SysML-1.6: Refers to both 'composite requirements' and 'compound requirements' (clearly as identical concepts)

MagicDraw/Cameo 19SP3: Validation of required and provided Interfaces proxied between a ProxyPort and a part with a compatible contract fails

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

SysML-1.6: InterfaceBlock: OCL in constraint 2_no_part is missing FlowProperty check (for FlowProperty of a valid type other than ValueType).

MagicDraw UML/SysML/Cameo 19SP3: Sometimes on application of a named Association as the Type of a Connector that already has an InformationFlow (or ItemFlow) applied, the direction of the InformationFlow (or ItemFlow) indicator swaps.

In SysML the NOW DEPRECATED (since SysML-1.6) direct UML Port conjugation does not work consistently with SysML DirectedFeature and SysML FlowProperty on nested ports!

SysML-1.6: Needs a constraint on ~InterfaceBlock making the implied inversion of provided/required Interfaces explicit

SysML-1.6: reference to 'Figure 17-1' should be 'Figure 16-7'

SysML-1.6: Stereotype keyword consistency: «testCase» in Figure 16-6, «TestCase» in Figure 16-7

SysML-1.6: Typo: Constraint name: Copy::1_source_and_ta[r]get_are_requirements

SysML-1.6: double-callout into one Note from 2 part Property symbols in 'Figure 16.4: Requirement satisfaction in an internal block diagram' is not tool friendly

SysML-1.6: in 'Figure 16-3: Links between requirements and design' on block BrakeSystem the part 'r:BrakeLine' should probably be 'r:RearBrake'

SysML-1.6: 'Figure 16-2: Requirements Derivation' indeed shows DeriveReqt but spec text refers to it only as 'an example of a compound requirement'

SysML-1.6: text on Requirement 'Test and procedure conditions' is mangled in 'Figure 16-2: Requirements Derivation' (was OK in SysML-1.5) [and also on Figure 16-6]

SysML-1.6: Consistency: either show the [metaclass] on all Stereotype symbols in profile diagrams or on none

SysML-1.6: The spec 'Figure 15-8: Example of Structural Allocation' has an IBD for Block1, which only makes sense if 'Abstract Reference' and 'Concrete Example' are meant to be part Properties (not Blocks)

SysML-1.6: In 'Figure 15-7: Example of flow allocation from ObjectNode to FlowProperty' there are allocations from an Actions (usage level) to Blocks (definition level)

SysML-1.6: In 'Figure 15-7: Example of flow allocation from ObjectNode to FlowProperty' it does not make sense naming the BDD 'Block0' if that Block is not shown in the diagram

SysML-1.6: The 'Figure 15-7: Example of flow allocation from ObjectNode to FlowProperty' does not show the allocatedFrom for 'action2' on Block7

SysML-1.6: The 'Figure 15-7: Example of flow allocation from ObjectNode to FlowProperty' does not allocate to any FlowProperty

MagicDraw/Cameo does not seem to offer the display option Apply SysML Callout Style on CentralBufferNode

SysML-1.6: Figure 15-5 does not show 'flow allocation of ObjectFlow .. alternatively to an ItemFlow', Figure 15-6 does.

SysML-1.6: text concerning Figure 15-4 says 'allocation of Actions to Parts are depicted in Figure 15-4' then has an allocation from a part to Activity6.

SysML-1.6: text concerning Figure 15-4 'The allocation to Activity6'; the allocation is FROM Activity6.

MagicDraw/Cameo: DOES NOT support the Namespace compartment on Block

MagicDraw/Cameo 19SP3: can't assign Statemachine submachine as principal of AdjunctProperty via validation warning dialog (confirmed bug). WORKAROUND: Set principal using the specification dialog.

SysML-1.6 Typo: There is no "hybridSUV" Lifeline in Figure D.9 - there is 'vehicleInContext:HybridSUV'

SysML-1.6: An additional ControlFlow is required into the DecisionNode of 'Figure 11-12: Continuous system example 3' and the existing ObjectFlow with Brake Pressure must become a decisionInputFlow

SysML-1.6: Edge for [else] in 'Figure 11-11: Continuous system example 2' should be an ObjectFlow not a ControlFlow

MagicDraw/Cameo 19SP3: Can't seem to show {control} notation on control Pin

MagicDraw/Cameo: Has ControlValue not ControlValueKind (due to known SysML spec issue)

SysML-1.6: Multiple references to ControlValue should be ControlValueKind (known issue)

Claim: The ControlValue input to Monitor Traction without a Pin is invalid in 'Figure 11-10: Continuous system example 1' and multiple issues with ControlOperator

MagicDraw/Cameo: Uses the lowerCase keyword «valueType», the SysML spec has «ValueType» in some sample figures

MagicDraw/SysML 19SP3: does not support ObjectNode notation shown in SysML-1.6 in Figure 11-6 and Figure 11-7 because does not support ObjectNode notation properly

SysML-1.6: Reference to 'in the decomposition from Figure 9-17' should be '...Figure 9-16'

SysML-1.6: Reference to 'House 2' for Figure 9-11 is inconsistent. Should probably just be 'House'.

SysML-1.6: reference to 'association between Spigot and Faucet Inlet in Figure 9-11' should say 'Figure 9-8'

Webel vs SysML-1.6: There is no «port» stereotype keyword for Port or Property in UML-2.5.1 or SysML-1.6, it is introduced as a custom (user-defined) stereotype keyword here only to mimic the spec Figure 9-8.

SysML-1.6: does not leverage redefinition of 'sp:Surface' on 'Figure 9-7: Usage example of proxy and full ports' (earlier versions of the spec did). And does not show direction of flows.

SysML-1.6: 'Figure 9-6: Usage example of ports with provided and required features' does not expose any directed features. It would be more instructive if the ports on the diagram used the capability to show the underlying directed features of the blocks

SysML-1.6: Missing correct diagram for 'Figure 9-5: Item Flow Stereotype'

MagicDraw/Cameo 19SP3: enumeration 'FeatureDirection' should be 'FeatureDirectionKind' (reflects known error in older SysML specification versions)

MagicDraw/Cameo: the keyword for PropertySpecificType is «PropertySpecificType» not «pst»

SysML-1.6: Figure 8-17: Multiplicity of rollBarBR should be [0] not [*] in 'Vehicle Model 2'

SysML-1.6: Figure 8-17: EndPathMultiplicity is applied to 'rollBarBR' instead of 'lugBoltBR' of 'Vehicle Model 2'

SysML-1.6: Figure 8-17: Multiplicity of 'lugBoltBR' of 'Vehicle Model 1' should be [6] not [6..8]

SysML-1.6: Figure 8-17: Multiplicity of 'rollBarBR' in 'Vehicle Model 1' should be [1] not [*] and it has no redefined type for the 'light roll bar'

SysML-1.6: Figure 8-17: Multiplicity of 'cylinderBR' in 'Vehicle Model 1' should be [4] not [*]

SysML-1.6: Use of ValueTypes named like units in Figure 8-12 and Figure 8-14 is inconsistent w.r.t. some other specification diagrams and examples (but not necessarily wrong)

SysML-1.6: Typo: Figure 8-12 'diamter' should be 'diameter'

SysML-1.6: Typo in figure name 'Figure 4-2: SysML Extension of UMLFigure'

SysML-1.6 Typo 'Acitivies' in Figure 4-3: SysML Package Structure

SysML-1.6: Spec Figure D.41 refers to 'em:ElectricalMotor' inconsistent w.r.t. 'emg:ElectricalMotorGenerator' in D.18 and allocation tables.

SysML-1.6: Spec Figure D.41 refers to 't:Transmission' not 'trsm:Transmission', inconsistent w.r.t. D.18 and allocation tables (with impact on some connector names).

Some Connectors 'b-l' and 'i-l' shown in Figure D.17 are missing in spec Figure D.41, and some 'c-p' and 'bk-p' are named inconsistently w.r.t 'p-c' and 'p-bk' in D.17

SysML-1.6: Spec Figure D.41 refers to 'i:Interior' not 'i:InteriorSubsystem', inconsistent w.r.t. Figure D.16.

SysML-1.6: The allocation from ObjectNode 'driveCurrent' in Figure D.38 to itemFlow 'i1' on the Connector in Figure D.39 does not appear in the allocation table Figure D.40; Instead there is an allocation from an ObjectFlow 'o6' to the Connector 'epc-emg'

MagicDraw/Cameo: 19SP3: Callout of allocatedFrom on Connector vs ObjectFlow shows «decisionInputFlow» not «objectFlow» keyword

MagicDraw/Cameo 19SP3: Can't callout from ItemFlow on Connector, the Note handle pulls from the Connector not the ItemFlow

MagicDraw/Cameo: HOWTO redisplay the name and type of a SysML ItemFlow on a Connector if it vanishes (such as when the Connector is redrawn)

MagicDraw/Cameo 19SP3: If Continuous or Discrete are applied to the underlying Parameter of an InputPin or an OutputPin the keywords «continuous» or «discrete» can't be displayed

In the Webel trail versions of the SysML-1.6 spec sample Figure D.38, the alignment of ObjectNode symbols over the ActivityParameterNode boundaries is completely contrived, please DO NOT mimic it; please use explicit Pins instead!

MagicDraw/Cameo 19SP3: Continuous and Discrete have metaclass [ActivityEdge, ObjectNode, Parameter] not just [ActivityEdge, Parameter] (via Rate), so may be applied directly to Pin and ActivityParameterNode

SysML-1.6: Each «continuous» Parameter (of each corresponding ActivityParameterNode) in Figure D.36 and Figure D.38 should be set to be streaming, because the Continuous Stereotype has a Generalization to Rate

SysML-1.6: The spec version of Figure D.37 does not show the breakdown from the top-level Accelerate activity

Webel recommends when using MagicDraw/Cameo: AVOID the "elided Pin" abstract ObjectNode notation on Activity Diagrams, use explicit Pins!

MagicDraw/Cameo: DO NOT use the ObjectNode menu item on Activity Diagrams ever!

[BUG: FIXED]: MagicDraw/Cameo SP193: Offers the display option to show the name and type label inside a Pin symbol, but it does not seem to work. [FIXED since 2022xRefresh2]

MagicDraw/Cameo: ERROR: Incorrectly uses 2 ObjectFlow edges and a CentralBufferNode for "elided Pin notation" instead of an abstract ObjectNode _symbol_ and 2 arrow _symbols_ (notations that are supposed to represent together 2 Pins and 1 ObjectFlow edge)

SysML-1.6: Figure D.32 does not have 'incline' value property connected

SysML-1.6: Figure D.32 aggregation kind on 'delta-t' is inconsistent w.r.t. Figure D.26

SysML-1.6: Figure D.31 has constraint parameter 'vc' on ':CapacityEquation', which is inconsistent w.r.t. parameters 'V1', 'V2', 'V3' and constraint {pcap=Sum(Vi)) shown in Figure D.26.

MagicDraw/Cameo 19SP3: Does not seem to directly support compartment for decomposition of Views as properties of Views (but one can create properties in an IBD and they will show in the 'attributes compartment')

SysML-1.6: The spec sample diagrams D.27 has Expose relationships to ValueType, they should be to value properties.

SysML-1.6: The View and Viewpoint spec sample diagrams D.27, D.28, D.29 and D.30 have multiple known issues; the trail versions here on this site are only placeholders until new spec versions are available once SysML-1.7 is released.

SysML-1.6: Figure D.25 has the type Fuel for both an in Port and an out Port on FuelTankAssembly (and it is not ideal to have same name as the Classifier that flows)

SysML-1.6: Need a Connector from fuel:Fuel to :FuelPump in 'Figure D.25 Detailed Internal Structure of Fuel Delivery Subsystem (Internal Block Diagram)'

SysML-1.6: Naming inconsistencies 'Figure D.24 is a parametric diagram showing how fuel flowrate is related to FuelDemand and FuelPressure value properties.'

SysML-1.6: Typo: 'Binding connectors, as defined in Clause 8 are used'

SysML-1.6: Figure D.24 does not explicitly show «equal» keyword or '=' on BindingConnectors [suggest this might be good to show this notation on at least one HSUV sample diagram]

SysML-1.6: Figure D.23 has FuelFlow redundantly stereotyped by the DEPRECATED «flowSpecification»

SysML-1.6: The provided features are in fact not indicated on the spec version of Figure D.20 (this was addressed by OMG JIRA SYSML17-224 'Features that are not denoted as a DirectedFeature are implicitly provided features'')

SysML-1.6: References to 'ecu:PowerControlUnit' should be 'pcu:PowerControlUnit'

SysML-1.6: Figure D.19: It's not clear why 'Port:~FuelTankFitting' (an ~InterfaceBlock conjugation port) does not match 'Port:ICEFuelFitting'

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.

SysML-1.6: Figure D.19 has an unnecessary Comment with the name of the 'ctrl' Port

SysML-1.6: Figure D.19 Internal Structure of the Power Subsystem (Internal Block Diagram): Connector 'acl-ecu' and 'bkp-ecu' should be 'acl-pcu' and 'bkp-pcu'

It's not clear that the «domain» block 'AutomotiveDomain' is the best choice of owner for BDD Figure D.16, the «system» block 'Hybrid SUV' might be better.

SysML-1.6: For the Connectors in Figure D.4 to be typed by the implied anonymous Associations need define them in Figure D.15 (or elsewhere) between 'HybridSUV' and: 'Driver', 'Maintainer', 'Passenger', 'Baggage', 'Environment'.

SysML-1.6: Figure D.3: Would 'HSUV Interfaces' be better higher up directly under 'HSUV Model' (instead of under 'HSUV Structure')?

ERROR: SysML-1.6: The name 'Operational Viewpoint' in Figure D.3 contradicts the name ''Functional Viewpoint' in Figure D.30 (suggest amend D.30 not D.3)

ERROR: SysML-1.6: Figure D.2: the original spec figure appears to show Real owned by the ModelLibrary 'Automotive Value Types' without an explicit element import.

ERROR: SysML-1.6: Figure D.3 Automotive Value Types model library does not belong under the HSUV Model, showing it on this diagram without showing the owner suggests it is. Compare with Figure D.2.

SysML-1.6: In Figure D.9 is a synchronous Message from Lifeline for :Driver for an Operation StartVehicle() intended? Does it make sense for the human Driver to have to wait for such a synchronous call?

MagicDraw/Cameo: There are lots of spelling mistakes in the ISO-80000 ModelLibrary

MD SysML and Cameo 19SP3 can't yet validate provided/required Feature subsets (such as Features of one Block against Features of multiple Ports)

SysML-1.6: Name 'knockSensor' should be 'isKnocking' for consistency with D.21

SysML-1.6: HSUV sample problem and spec sample diagrams naming issue, 'ecu:PowerControlUnit' should be 'pcu:PowerControlUnit'

ObjectNode::inState - The UML2.5.1 spec is not clear on whether composite state parents should also be listed in the states

To get synchronisation of multiple AcceptEventAction "loops" to work in Cameo Simulation Toolkit one sometimes needs an additional ForkNode

BUG: An unmarshalled AcceptEventAction fails in Cameo Simulation Toolkit 19SP3 as soon as use Generalization with a redefined property!

UML-2.5.1: Statement about 'Adding a value to an ordered StructuralFeature requires an insertion point' contradictory. First it says 'insertAt' is 'required', then it says it is not always 'required'. The 'insertAt' attribute is [0..1].

Cameo Simulation Toolkit 19SP3 DOES NOT support AcceptCallAction or ReplyAction (even though compliance with fUML-1.3/1.4 would require it to)

Subscribe to ISSUE