Webel's "super-relational" Note pages!

A Note is a short categorised statement, claim, policy, tip, or issue tracker Throughout this site, content is often related to supporting Notes, and each Note page links back to the content pages that reference it! The Note and Snippet concepts are very closely related and they support each other.
Look for "super-relational" Note page links at the bottom of most content pages!
Note kind Note Spec tag UML keywords SysML keywords Keywords
ISSUE SysML-1.6: Multiple references to ControlValue should be ControlValueKind (known issue) SysML-1.6 ControlValueKind
ISSUE SysML-1.6: Missing correct diagram for 'Figure 9-5: Item Flow Stereotype' SysML-1.6 ItemFlow
ISSUE SysML-1.6: InterfaceBlock: OCL in constraint 2_no_part is missing FlowProperty check (for FlowProperty of a valid type other than ValueType). SysML-1.6 InterfaceBlock, SysML-1.6, FlowProperty
ISSUE 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? SysML-1.6 Message, MessageSort, MessageSort::synchCall HSUV sample problem
ISSUE 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 SysML specification figure, part property, Block
ISSUE 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 SysML specification figure, Block, SysML Block Definition Diagram, allocation, behavior allocation
ISSUE 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 SysML specification figure, Block, SysML Block Definition Diagram
ISSUE SysML-1.6: HSUV sample problem and spec sample diagrams naming issue, 'ecu:PowerControlUnit' should be 'pcu:PowerControlUnit' SysML-1.6 SysML specification figure, HSUV sample problem, SysML-1.6
ISSUE 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 Association, Connector, Type HSUV sample problem
ISSUE, QUESTION SysML-1.6: Figure D.3: Would 'HSUV Interfaces' be better higher up directly under 'HSUV Model' (instead of under 'HSUV Structure')? SysML-1.6 Package, Element::owner, containment HSUV sample problem, SysML Package Diagram
ISSUE SysML-1.6: Figure D.32 does not have 'incline' value property connected SysML-1.6 SysML specification figure, BindingConnector, value property
ISSUE SysML-1.6: Figure D.32 aggregation kind on 'delta-t' is inconsistent w.r.t. Figure D.26 SysML-1.6 AggregationKind SysML specification figure
ISSUE 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. SysML-1.6 constraint parameter, ConstraintBlock, «constraint»
ISSUE 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 Port HSUV sample problem, FlowProperty
ISSUE 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 BindingConnector, «equals»
DEPRECATION, ISSUE SysML-1.6: Figure D.23 has FuelFlow redundantly stereotyped by the DEPRECATED «flowSpecification» SysML-1.6 DEPRECATED:FlowSpecification
ISSUE SysML-1.6: Figure D.19: It's not clear why 'Port:~FuelTankFitting' (an ~InterfaceBlock conjugation port) does not match 'Port:ICEFuelFitting' SysML-1.6 Port HSUV sample problem, ~InterfaceBlock, conjugation
ISSUE 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' SysML-1.6 Connector HSUV sample problem, SysML Internal Block Diagram
ISSUE SysML-1.6: Figure D.19 has an unnecessary Comment with the name of the 'ctrl' Port SysML-1.6 HSUV sample problem
ISSUE 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' SysML-1.6 BoundReference, HSUV sample problem Systems Modeling Language, SysML
ISSUE SysML-1.6: Figure 8-17: Multiplicity of rollBarBR should be [0] not [*] in 'Vehicle Model 2' SysML-1.6 multiplicity, Property::redefinedProperty SysML specification figure, Block, BoundReference
ISSUE 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 multiplicity, Property::redefinedProperty SysML specification figure, Block, BoundReference
ISSUE SysML-1.6: Figure 8-17: Multiplicity of 'lugBoltBR' of 'Vehicle Model 1' should be [6] not [6..8] SysML-1.6 multiplicity, Property::redefinedProperty SysML specification figure, Block, BoundReference
ISSUE SysML-1.6: Figure 8-17: Multiplicity of 'cylinderBR' in 'Vehicle Model 1' should be [4] not [*] SysML-1.6 multiplicity, Property::redefinedProperty SysML specification figure, Block, BoundReference
ISSUE SysML-1.6: Figure 8-17: EndPathMultiplicity is applied to 'rollBarBR' instead of 'lugBoltBR' of 'Vehicle Model 2' SysML-1.6 multiplicity, Property::redefinedProperty SysML specification figure, Block, BoundReference, EndPathMultiplicity
ISSUE SysML-1.6: Figure 15-5 does not show 'flow allocation of ObjectFlow .. alternatively to an ItemFlow', Figure 15-6 does. SysML-1.6 ObjectFlow SysML specification figure, ItemFlow
ISSUE SysML-1.6: Edge for [else] in 'Figure 11-11: Continuous system example 2' should be an ObjectFlow not a ControlFlow SysML-1.6
ISSUE 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 Parameter::isStreaming, Parameter Continuous, «continuous», Rate, «rate»
DISPLAY, ISSUE, STYLE 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 callout SysML specification figure
ISSUE 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 Property::redefinedProperty SysML specification figure, FlowProperty
DISPLAY, ISSUE, STYLE SysML-1.6: Consistency: either show the [metaclass] on all Stereotype symbols in profile diagrams or on none SysML-1.6 Stereotype, metaclass
ISSUE 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 DecisionNode, DecisionNode::decisionInput, DecisionNode::decisionInputFlow
ISSUE SysML-1.6: AbstractRequirement: direction of /tracedTo wrong in Attributes description AbstractRequirement, AbstractRequirement::/tracedTo
ISSUE 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 DirectedFeature
ISSUE 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 SysML specification figure, AbstractRequirement::text, composite (compound) requirement
MODELLING, TIP SysML-1.6/1.7: You can introduce a custom (user-defined) stereotype keyword «item» to indicate Properties that are to be used as "packets" for ItemFlows on Connectors. (SysMLv2 will have a formal way of treating such items/packets.) Stereotype, «keyword», custom Stereotype, user defined Stereotype SysML, Systems Modeling Language, Webel Best Practice
ISSUE SysML-1.6 Typo: There is no "hybridSUV" Lifeline in Figure D.9 - there is 'vehicleInContext:HybridSUV' SysML-1.6
ISSUE SysML-1.6 Typo 'Acitivies' in Figure 4-3: SysML Package Structure SysML-1.6
ASSERTION, MODELLING, TIP SysML+SysPhS: Flows: If you intend to use a Classifier to type the itemProperty of an ItemFlow on a Connector for a physical interaction you MUST use a Block (not a ValueType or Signal) so your can extend ConservedQuantityKind. SysML-1.6, SysML-1.7, SysPhS-1.1 Signal, InformationFlow, InformationFlow::conveyed Block, ValueType, ItemFlow, ItemFlow::itemProperty Systems Modeling Language, SysML, flow, Webel Best Practice, physical interaction, SysPhS
COMPLICATION, GOTCHA, NAMING, WARNING SysML vs Modelica: GOTCHA: Terminology: A 'connector' in Modelica is equivalent to the Type of a Port in SysML. A Connector in SysML-1.x is equivalent to a 'connect(source,target)' in Modelica. SysML-1.6, SysML-1.7, SysPhS-1.1 Connector Block, InterfaceBlock SysPhS, Modelica, SysML, Systems Modeling Language, UML
TIP SysML v2 (unlike SysML v1.x) is not directly based on Unified Modeling Language (UML) SysMLv2 SysMLv2, SysML, Systems Modeling Language
ASSERTION SysML tools can ALSO be used for many graphical Model-Based Engineering tasks that benefit from Single Source Of Truth - and even without any formal System Engineering methodology (which is NOT to say that formal System Engineering is not also useful). SysML-1.6, SysML-1.7, SysMLv2 systems engineering, Model-Based Systems Engineering, SysML, Systems Modeling Language, SysMLv1.x, SysMLv1.7, SysMLv2, Single Source of Truth, model-based engineering
MODELLING, NAMING, TIP SysML Parametrics: You can use custom stereotypes keywords «i» and «o» to indicate value properties that are intended to be used as (i)nputs and (o)utputs when bound to constraint parameters for SysML Parametrics Property, Stereotype, custom Stereotype, «keyword» constraint parameter, ConstraintBlock, value property, MD:ConstraintParameter Webel Best Practice
MODELLING, NAMING, TIP SysML Parametrics: You can use custom stereotypes keywords «i» and «o» on constraint parameters to indicate their intended use (causality) as (i)nputs and (o)utputs on ConstraintBlocks Property, Stereotype, custom Stereotype, «keyword» constraint parameter, ConstraintBlock, SysML Parametric Diagram, BindingConnector, MD:ConstraintParameter, MD:ConstraintProperty Webel Best Practice, Systems Modeling Language
WARNING SysML does NOT distinguish between 'assembly' and 'delegation' Connector kinds (because of its more complex support for nested ports). These Connector type classifications are only relevant in UML. ConnectorKind::assembly, ConnectorKind::delegation nested Port, NestedConnectorEnd Unified Modeling Language, Systems Modeling Language, UML, SysML, MagicDraw SysML, MagicDraw UML, Cameo Systems Modeler
ASSERTION SysML directional FlowProperty contracts for ProxyPorts SHOULD be satisfiable Property-wise (including as subsets of Properties) not necessarily just at the level of entire Blocks! SysML-1.6 FlowProperty, FlowProperty::direction, FlowDirectionKind
DISPLAY, STYLE SysML directed features displayed on Port symbols are often far clearer than UML-style provided/required Interface "ball (lollipop) and socket" notation SysML-1.6 provided Interface, required Interface, ball-and-socket, InterfaceRealization, Usage directed Feature
ASSERTION, TIP SysML Blocks have lots of possible features and compartments, lots of capabilities, and are very powerful! But you don't have to use every aspect of a Block (or show every aspect in every diagram) at once on every project. Block Webel Best Practice
NAMING, TIP Suffix the "focus" BDD for a Block with .bdd so that it won't clash with a corresponding IBD on diagram export. Webel Best Practice
DISPLAY, STYLE, TIP, TOOL Style: use line width 2 or 3 on the border of the "focus" element in "focus" diagrams (such as the main Block or Class of a dedicated Block Definition Diagram or Class Diagram)
ISSUE 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 HSUV sample problem
POLICY Since SysML-1.6 use of direct UML conjugation of Ports is NOT supported; If you are using InterfaceBlocks use instead a conjugated ~InterfaceBlock type! SysML-1.6 Port ~InterfaceBlock, conjugation
DISPLAY, TIP, TOOL Showing lots of Expose relationships can be unwieldy! Consider instead just showing them in a compartment once they have been created (then remove the relationships visually from the diagram) Expose
MODELLING, TIP Sample problems and example diagrams in graphical language specifications are NOT necessarily indications of how one should model on a real-world project! They often just serve to demonstrate a particular aspect of the specified language. Alf-1.1, fUML-1.3, fUML-1.4, OCL-2.4, SysML-1.6, SysML-1.7, SysMLv2, SysPhS-1.1, UML-2.5.1 specification, UML, fUML, Unified Modeling Language, SysML, Systems Modeling Language, Alf, Object Constraint Language, OCL, SysPhS, graphical engineering, patch-based
ASSERTION, DISPLAY, TOOL Rule #1: A UML or SysML Element in a tool is NOT just an Element symbol in a diagram! A Note is not an Element (compare with a Comment). SysML-1.6, UML-2.5.1 Diagram, Element, symbol Webel Best Practice, MagicDraw SysML, Cameo Systems Modeler
TIP QUDV in SysML refers to: Quantity, Unit, Dimension, Value. It is strongly influenced by the International Vocabulary of Metrology (VIM). SysML-1.6 QuantityKind, ValueType::unit, Unit::quantityKind, ValueType, Unit scientific unit system, Systems Modeling Language, VIM3, SysML, ISO-80000
ASSERTION, GOTCHA, TIP Psychrometrics: The volumetric flow rate of a humid air mixture MAY change between a State1 and State2 (but the mass flow rate of dry air does not under steady state)! This is sometimes "glossed over" in some online calculators and less formal guides. Psychrometrics, humid air, air, water, water vapour, steam
ASSERTION, TIP Psychrometrics: Calculations of the mass flow rate of the dry air component (assumed constant under steady state) from the ENTRY volumetric flow rate of the humid air mixture MUST use the INITIAL state variables! Psychrometrics, humid air, air, water, water vapour, steam
DISPLAY, STYLE, WARNING Provided/required Interface "lollipop" and "socket" (a.k.a. ball-and-socket) notation can quickly lead to clutter in UML Composite Structure Diagrams and SysML Internal Block Diagrams. SysML provided/required DirectedFeature notation is cleaner. Port, lollipop, ball-and-socket DirectedFeature, FeatureDirectionKind::provided, FeatureDirectionKind::required, FeatureDirectionKind::providedrequired
MODELLING, STYLE, TIP Progressively "exporting" internal Ports of usages of Blocks to the boundary of their using Block may seem like a bit of extra work, but it means you can progressively develop with clean black box views without the Connectors crossing Block boundaries. Webel Best Practice, SysML, Systems Modeling Language, Cameo Systems Modeler, MagicDraw SysML, MD SysML
DISPLAY, TIP Prefer the Name Display Mode 'both' on CallBehaviorAction symbols (rather than 'Show Action Name', 'Show Behavior Name', or 'Show Both or Behavior Name') Action, Behavior, CallBehaviorAction Webel Best Practice, Cameo Systems Modeler, MagicDraw UML, MagicDraw SysML
Prefer owner path indicators over Package containment operators (which are fragile). Element::owner, owner path display
TIP Prefer not rename Properties when redefining unless indicating a clear change in role. Property::redefinedProperty, NamedElement::name Webel Best Practice
NAMING, POLICY Prefer anonymous Actions, or if they must be named, prefer code-like 'lowerCamelCase' or completely 'lower case' (if you do absolutely insist on having spaces in action names, but please no other punctuation). Action UML, SysML
NAMING, POLICY Prefer 'UpperCamelCase' (a.k.a. PascalCase) names for Behaviors such as Activities intended for use in CallBehaviorActions, or at least use a 'Capital first letter'; avoid 'all lower case' (as it leads to confusion with lower case Action names) Behavior, Activity, Classifier UML, SysML
TIP Place your SysML-1.6 ~InterfaceBlock conjugation under the 'original' InterfaceBlock (i.e. make the original the containment owner). ~InterfaceBlock, conjugation
TIP One of the most important reasons to use a Port to send a Signal is that only the connection context, not the sender, knows the ultimate recipient (at the end of a specific Connector). SysML-1.6, UML-2.5.1 Port, InvocationAction::onPort, SendSignalAction::target
CAVEAT One limit of the SysML-1.6 ElementGroup for use as a Snippet in the v1.x version of Webel Parsing Analysis for SysML is that an ElementGroup is not directly relatable. SysML-1.6 ElementGroup Webel Parsing Analysis
EXPLANATION, MODELLING, TIP On the Webel Best Practice modelling tips for SysML (and UML). If you want to model the Webel way, use them, if you don't, ignore them. They are ONLY offered as options and graphical modelling paradigms and idioms for you to consider. SysML-1.6, SysML-1.7, UML-2.5.1 Systems Modeling Language, SysML, MBSE, Model-Based Systems Engineering, Webel Best Practice
On OMG copyright in text extracts and figures reproduced for educational purposes copyright, Object Management Group, WPA:«snippet», quote, extract
ISSUE ObjectNode::inState - The UML2.5.1 spec is not clear on whether composite state parents should also be listed in the states ObjectNode::inState
TIP Not every task in Activity Diagrams is well-suited to graphical modelling; consider using Action Language Helper (ALH) or Action Language for Foundational UML (Alf) Alf-1.1 LoopNode, ConditionalNode, StructuredActivityNode Alf, Action Language Helper, Cameo Systems Modeler, Magic Model Analyst [Cameo Simulation Toolkit]
TIP Not every task in Activity Diagrams is well-suited to graphical modelling and LoopNode and ConditionalNode are notoriously fiddly to setup; consider using Action Language Helper (ALH) or Action Language for Foundational UML (Alf) LoopNode, ConditionalNode, StructuredActivityNode Alf, Action Language Helper, Cameo Systems Modeler, Magic Model Analyst [Cameo Simulation Toolkit]
ASSERTION Not even the most experienced requirements engineers can easily state requirements perfectly in consistent requirements-friendly language first shot; requirements and constraints are often buried in the natural text of domain source documents. Requirement requirements engineering, Webel Parsing Analysis, parsing analysis
TIP Nobody (informed) said that SysML (or even UML) modelling and MBSE is only about graphical modelling, notations, and diagrams! Information can be extracted in many different ways and presented in many different formats from the underlying model! SysML-1.6, SysML-1.7, SysMLv2, UML-2.5.1 Cameo Systems Modeler, MagicDraw SysML, MagicDraw UML, relationship map, derived relationships, metachain navigation, table, report, query, model query, table query, query table, report generation, report extraction, repository, model, Model-Based Systems Engineering, model-based development, model-driven development, matrix, dependency matrix, relationship matrix
CONVENTION, NAMING Naming: If SISO is 'Single Input Single Output' then 'Double Input Single Output (DISO)' is more consistent than 'Two Input Single Output (TISO)', otherwise you'd have to have a 'One Input Single Input (OISO)' for consistency. But who ever says OISO? SISO, DISO, signal processing
TIP Modelica: Units: Uses 'l' for litre, rather than 'L'. Modelica, Wolfram SystemModeler, units, unit conversion
CONVENTION, MODELLING, NAMING Modelica: Naming convention: Why does the OnePort family of electrical components have 2 Pins? Where is the "one port"? "standard" Port Modelica
TIP, WARNING Modelica: GOTCHA: Sometimes the name 'p' is used for any Pin (such as on Ground) and sometimes 'p' is used for a specifically PositivePin (as opposed to 'n' for NegativePin). Modelica
GOTCHA Modelica does not support comparison of Real values using == outside of functions (so not directly inside state machines) Modelica, Wolfram SystemModeler
ISSUE, TOOL MDSysML19SP3: Validation engine does not report value properties with AggregationKind other than composite SysML-1.6, SysML-1.7 AggregationKind, AggregationKind::composite, AggregationKind::none, AggregationKind::shared SysML-1.6, value property SysML, MagicDraw SysML, Cameo Systems Modeler
TIP, TOOL MDSysML/Cameo: Unless a custom ValueType is otherwise specified through specialisation it is behaves like a Real for the purposes of data entry for value properties typed by that ValueType ValueType, value property, Real Cameo Systems Modeler, MagicDraw SysML
TIP, WARNING MDSysML/Cameo: SysPhSLibrary: GOTCHA: You must set the additional 'k2' parameter for Modelica to be minus to achieve subtraction SysPhS-1.1 SysPhS, Modelica
ISSUE, TOOL MDSysML/Cameo: 19SP3: SysPhSLibrary: Has value properties with aggregation kind 'none' SysML-1.6, SysML-1.7 AggregationKind, AggregationKind::composite, AggregationKind::none, AggregationKind::shared SysML-1.6, value property SysML, MagicDraw SysML, Cameo Systems Modeler
ISSUE, TOOL, WARNING MDSysML/Cameo 19SP3: The SysPhS versions of Conductance, Frequency, siemens, and hertz, are not explicitly provided in the MagicDraw/Cameo model library ValueType, ValueType::unit, Unit SysPhS, MagicDraw SysML, Cameo Systems Modeler, current, resistance, voltage
ISSUE MDSysML/Cameo 19SP3: SysPhSLibrary vs SysPhS-1.1: SPELLING/TYPO: VariableDelay: parameter 'maxDelay' should be 'delayMax' SysPhS-1.1 SysPhS, MagicDraw SysML, Cameo Systems Modeler
ISSUE 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 Real Real, value property, ValueType SysPhS, MagicDraw SysML, Cameo Systems Modeler
ISSUE, TOOL MDSysML/Cameo 19SP3: SysPhSLibrary vs SysPhS-1.1: RealVectorSignalIn2Element extends RealVectorSignalElement not RealVectorSignalInElement, RealVectorSignalOut2Element extends RealVectorSignalElement not RealVectorSignalOutElement (and so on) SysPhS, SysML, MD SysML, Cameo Systems Modeler, MagicDraw SysML
ISSUE 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 SysPhS-1.1 Real Real, value property, ValueType SysPhS, MagicDraw SysML, Cameo Systems Modeler
ISSUE 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 SysPhS-1.1 Real Real, value property, ValueType SysPhS, MagicDraw SysML, Cameo Systems Modeler
ISSUE 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 SysPhS-1.1 Real Real, value property, ValueType SysPhS, MagicDraw SysML, Cameo Systems Modeler
ISSUE, TOOL MDSysML/Cameo 19SP3: SysPhSLibrary vs SysPhS-1.1: Does not represent the elements in 'Figure 32: Elements for signal flows of electrical quantities' SysPhS, MagicDraw SysML, Cameo Systems Modeler, current, resistance, voltage
ISSUE, TOOL MDSysML/Cameo 19SP3: SysPhSLibrary vs SysPhS-1.1: Continuous.Integrator is missing the 'init' PhSConstant (maps to y_start in Modelica) SysPhS, Cameo Systems Modeler, MagicDraw SysML, MD SysML
DISPLAY, FEATURE, ISSUE, MODELLING, TOOL, WARNING MDSysML/Cameo 19SP3: Showing stereotype keywords on FlowProperty rows is UNSUPPORTED FlowProperty MagicDraw SysML, MD SysML, SysML, Systems Modeling Language, Cameo Systems Modeler
ISSUE 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 SysPhS, MagicDraw SysML, Cameo Systems Modeler
COMPLICATION, TOOL, WARNING MDSysML/Cameo 19SP3 SysPhSLibrary vs SysPhS-1.1: SimulinkBlock and ModelicaBlock specialise ExternalModel not Block
CAVEAT, ISSUE MD SysML and Cameo 19SP3 can't yet validate provided/required Feature subsets (such as Features of one Block against Features of multiple Ports) Port provided Feature, required Feature Cameo Systems Modeler, MagicDraw SysML, MD SysML, validation
ISSUE, TOOL Mathematica: Wolfram Workbench: Sometimes the Outline view gets completely out of sync with the .m or .wl Package code Mathematica, Wolfram Workbench, Wolfram Language, Wolfram, Eclipse IDE
ISSUE, TOOL, WORKAROUND 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. Mathematica, Wolfram Workbench, Wolfram Language, Wolfram, Eclipse IDE
FEATURE, ISSUE, LIMITATION, WISHLIST 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.) Webel:WISHLIST, Mathematica, Wolfram Workbench, Wolfram