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
TIP In professional applications of the Webel Parsing Analysis recipe for SysML, a robust reusable profile for «part»/«assembly»/«leaf» components is used, along with stereotypes keywords like «assembles» for indicating physical composition hierarchies. AggregationKind Block, block property Webel Best Practice, WPA:«assembles», WPA:«part», WPA:«leaf», WPA:«assembly», composition hierarchy
In some slides some Comments in UML/SysML diagrams are verbosely marked with the stereotype keyword «webel» to distinguish them from «snippet» domain source document text extracts. Webel Parsing Analysis, WPA:«snippet», WPA:«webel»
DISPLAY, STYLE In SysML diagrams, showing the context name and type in the diagram frame can lead to clutter and is not always clear to non-SysML stakeholders (although that is the style used in the specification samples) SysML, Systems Modeling Language, Webel Best Practice
COMPLICATION In SysML more than one NamedElement can help Satisfy a single Requirement (which presents challenges for verifying satisfaction of Requirements). This is a conceptual challenge for requirements engineering in general, not just SysML! SysML-1.6 NamedElement Satisfy, Satisfy::getSatisfies(in ref), AbstractRequirement::/satisfiedBy, AbstractRequirement, Requirement requirements engineering, test engineering
ISSUE, WARNING 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 Port::isConjugated, Port
TIP In SysML, unless you MUST use a DataType or PrimitiveType from an existing ModelLibrary or Profile, you SHOULD probably be using a ValueType, Enumeration ValueType, or SysML PrimitiveValueType instead so that it integrates with the value system of SysML. DataType, PrimitiveType ValueType, PrimitiveValueType Webel Best Practice
ASSERTION, GOTCHA, WARNING In the course PDF for 'CED Engineering: Air Conditioning Psychrometrics (A.Bhatia)' the term "enthalpy (h)" usually refers to the mass-specific enthalpy per dry air (in CoolProp notation 'Hda') enthalpy, specific enthalpy, Psychrometrics, CoolProp
POLICY In the Webel Parsing Analysis recipe you are not obliged to map every single part of a Snippet's text extract to a UML or SysML model, just traceably elicit model elements of immediate or anticipated interest to your task or goal. Webel Parsing Analysis
ASSERTION, TIP In the Webel recipe for SysML, DO use a "standard" Port until you have a truly compelling reason to commit to a FullPort or ProxyPort Port FullPort, ProxyPort, "standard" Port Cameo Systems Modeler, MagicDraw SysML, MD SysML
PATTERN In the Webel recipe for UML/SysML, the pattern of progressive redefinition of end Properties of Associations between progressively more specialised pairs of Blocks at the same level of abstraction is informally called a "redefinition ladder" Generalization, Association, Property::redefinedProperty, Association::memberEnd Block, block property Webel Best Practice
NAMING, PATTERN, TIP In the Webel terminology for a basic control loop there is an 'aim' value (controlled via an actuator) and a 'got' value (a value read from a sensor). The 'got' value is NOT necessarily exactly the same as the actual physical value. SysML-1.6, SysML-1.7, SysMLv2, SysPhS-1.1, UML-2.5.1 got value, aim value, control loop, Webel Best Practice
ISSUE, STYLE 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! SysML-1.6 elided Pin notation, ObjectNode HSUV sample problem, AllocateActivityPartition MagicDraw SysML, Cameo Systems Modeler
TIP In UML and SysML a '/' forward slash prefix before a Property name indicates that it is derived from other elements in the model. SysML-1.6, UML-2.5.1 Property::isDerivedUnion, Property::isDerived
In UML/SysMLv1.x Lifelines do not have specific information about the times or time ordering of events (such as Message arrival/sending) of other Lifelines Lifeline, Sequence Diagram, Interaction, interaction diagram, Message SysML Sequence Diagram UML, Unified Modeling Language, SysML, Systems Modeling Language, SysMLv1.x
ASSERTION In Webel Parsing Analysis elicited model elements MUST eventually be moved out of the 'source' (or '0-source') Package/Model zone and under a main project Package/Model area. (Use the owner display option to check.) Webel Parsing Analysis, WPA:«pa», WPA:TargetModelZone, WPA:SourceInputZone
TIP In Webel Parsing Analysis every Package, Model, or Diagram used to perform Parsing Analysis MUST have the stereotype keyword «pa» applied, and MUST live under a top-level Model or Package 'source' separate from the rest of the project model. Webel Parsing Analysis, WPA:«pa»
OPTION In Webel Parsing Analysis if you want to track elicited model elements that have not been explicitly mentioned in source text you can introduce Element-level custom tracking Stereotypes with the keywords «pa:implied» or «pa:assumed». Stereotype, custom Stereotype, «keyword», user defined Stereotype parsing analysis, Webel Parsing Analysis, WPA:«pa:implied», WPA:«pa:assumed»
TIP In Webel Parsing Analysis tutorials, Wikipedia pages are often used as a placeholder sources to represent authoritative domain source documents from which text extract "snippets" are sourced, and from which SysML model elements are traceably elicited. Webel Parsing Analysis, Wikipedia
CAVEAT, COMPLICATION, GOTCHA, ISSUE, MODELLING, NAMING, TOOL 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! Activity, ActivityParameterNode, Activity Diagram, Pin, Parameter, CallBehaviorAction, CallOperationAction SysML Activity Diagram Unified Modeling Language, UML, SysML, Systems Modeling Language, SysMLv1.x, MagicDraw UML, MagicDraw SysML, Cameo Systems Modeler, MagicDraw:validation
ISSUE, MODELLING, TOOL ISSUE: Cameo Simulation Toolkit: v2024x: Does not show argument Pins corresponding to inherited attributes of Signal on SendSignalAction or un-marshalling AcceptEventAction. No known UML2.5.1 or fUML-1.4 constraint; no obvious tool display option. fUML-1.3, fUML-1.4, SysML-1.6, SysML-1.7, UML-2.5.1 InputPin, Signal, SendSignalAction, AcceptEventAction, AcceptEventAction::isUnmarshall SysML, Systems Modeling Language, SysMLv1, MBSE, Model-Based Systems Engineering, Cameo Systems Modeler, MagicDraw SysML, CATIA Magic, Magic Model Analyst [Cameo Simulation Toolkit], UML, fUML
ISSUE, TOOL ISSUE: MagicDraw/Cameo: v2022x Golden, v2022xRefresh1: Comment can't connect anchor to another Comment as annotatedElement SysML-1.6, SysML-1.7, UML-2.5.1 Comment, Comment::annotatedElement Systems Modeling Language, SysML, MagicDraw, CATIA Magic:v2022xGolden, MagicDraw SysML, MagicDraw UML, Cameo Systems Modeler, CATIA Magic:v2022xRefresh1
ASSERTION, WARNING It is NOT true in SysML1.6+ that you "should" always use a SysML FullPort or a SysML ProxyPort instead of a "standard" Port, and it's not even always a good idea (and the spec states this very clearly in multiple places)! Port FullPort, ProxyPort, "standard" Port
ISSUE 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.
TOOL LINKS: Wolfram Workbench for Mathematica (or just use the far superior IntelliJ IDEA Plugin) Wolfram, Wolfram Workbench, Wolfram Language, Mathematica, coding, code formatting, documentation
TIP List of some formal systems engineering methodologies, standards, and guides [EXTERNAL LINKS] Model-Based Systems Engineering, systems engineering, Unified Architecture Framework, UAF, DoDAF, MODAF, NATO Architecture Framework, NAF, The Open Group Architecture Framework, TOGAF, INCOSE, INCOSE Systems Engineering Handbook, SeBOK, NASA
CAPABILITY, GOTCHA, LIMITATION, TIP, TOOL Mac: Compressor: HOWTO render H.264 and H.265 at higher than 50Mbps Mac:Compressor, Mac, video, H.264 H.265, HEVC, bps, bitrate, Final Cut Pro, FCP, 4K
GOTCHA, MODELLING, TIP, WARNING MagicDraw SysML/Cameo 19SP3: GOTCHA: If you drag a Behavior from the model browser onto the 'entry', 'doActivity', or 'exit' field in a specification dialog of a State it WILL BECOME OWNED by the State (which "steals ownership")! SysML-1.6, SysML-1.7, SysPhS-1.1, UML-2.5.1 State, State::entry, State::doActivity, State::exit, Behavior Modelica, MD SysML, MagicDraw SysML, Cameo Systems Modeler, drag-n-drop
ISSUE, TOOL 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 InformationFlow, InformationFlow::conveyed, Connector ItemFlow MagicDraw SysML, Cameo Systems Modeler
MODELLING, STYLE, TIP, TOOL MagicDraw SysML/Cameo has a nice feature 'Tools > Delegate Port(s)' accessible from the context menu for splitting Connectors that cross block boundaries into multiple Connectors with "exporting" Ports. SysML, Systems Modeling Language, Cameo Systems Modeler, MagicDraw SysML, MD SysML
CAVEAT, ISSUE, TOOL MagicDraw SysML/Cameo: 19SP3: Does not seem to support export to Modelica from a Package [use a SysML Block as root instead] SysML-1.6, SysML-1.7, SysPhS-1.1 Package Block MagicDraw SysML, MD SysML, Cameo Systems Modeler, Modelica, SysPhS, Modelica::model
ISSUE, TOOL MagicDraw SysML/Cameo: 19SP3: Export to Modelica from SysPhS sample for HumidifierSystem does not execute in Wolfram SystemModeler Simulation Centre SysML-1.6, SysML-1.7, SysPhS-1.1 Wolfram SystemModeler, MagicDraw SysML, MD SysML, Cameo Systems Modeler, Modelica, SysPhS
ISSUE, TOOL MagicDraw SysML/Cameo: 19SP3: Export to Modelica from TestBed (for SignalProcessor) sample does not validate in Wolfram SystemModeler SysML-1.6, SysML-1.7, SysPhS-1.1 Wolfram SystemModeler, MagicDraw SysML, MD SysML, Cameo Systems Modeler, Modelica, SysPhS
TIP MagicDraw SysML/Cameo: For export of more complex physical interaction and flow cases to Modelica or Simulink/Simscape/Stateflow load the SysPhS ModelLibrary using SysPhSLibrary.mdzip as a shared project. SysML-1.6, SysPhS-1.1 SysPhS, Modelica, Stateflow, Simulink, Simscape, MD SysML, SysML, Systems Modeling Language, Cameo Systems Modeler, simulation, execution, MagicDraw SysML
COMPLICATION, FEATURE, MODELLING, TIP, TOOL, WARNING MagicDraw SysML/Cameo: GOTCHA: A Constraint created and applied to a ConstraintBlock via the sidebar menu is NOT owned by the ConstraintBlock! SysML-1.6, SysML-1.7 Constraint ConstraintBlock MagicDraw SysML, Cameo Systems Modeler, Systems Modeling Language, MD SysML, SysML
COMPLICATION, TIP, WARNING MagicDraw SysML/Cameo: GOTCHA: Export to Modelica only includes owned Constraints (not just applied Constraints) under the 'equation' export SysML-1.6, SysML-1.7, SysPhS-1.1 Modelica, Modelica::equation, SysPhS, MagicDraw SysML, MD SysML, Cameo Systems Modeler, SysML, Systems Modeling Language
FEATURE, GOTCHA, MODELLING, TIP, TOOL MagicDraw SysML/Cameo: If you have a SINGLE Allocate from an Activity to a Block it will set that Block to be the Behavior::/context for that Activity. SysML-1.6, SysML-1.7 Behavior::/context, Behavior, Activity Allocate, Block functional allocation, SysML, Systems Modeling Language, systems engineering, MagicDraw SysML, Cameo Systems Modeler
TIP, TOOL MagicDraw SysML/Cameo: SysPhS: Export to Modelica: It does not seem to matter whether you give the language of Constraints as 'Modelica' or 'sysphs' (although SysPhS specifies a restricted SysPhS expression grammar) SysML-1.6, SysML-1.7, SysPhS-1.1 MD SysML, MagicDraw SysML, Systems Modeling Language, SysML, SysPhS, Modelica
CAPABILITY, TIP, TOOL MagicDraw SysML/Cameo: You can customise the generic query table diagram kind to check that the context Blocks of your Parametric Diagrams only contain BindingConnectors (not Connectors) SysML-1.6, SysML-1.7 Connector BindingConnector, constraint parameter MagicDraw SysML, Cameo Systems Modeler, SysML, Systems Modeling Language
TIP MagicDraw SysML/Cameo: You do not always need to load the entire SysPhS ModelLibrary for simpler black box exports to Modelica or Simulink/Simscape/Stateflow (sometimes the sysphs_profile within the MD Customization for SysML is enough) SysML-1.6, SysPhS-1.1 Profile SysPhS, Modelica, Stateflow, Simulink, Simscape, MD SysML, SysML, Systems Modeling Language, Cameo Systems Modeler, simulation, execution, MagicDraw SysML
COMPLICATION, DISPLAY, FEATURE, GOTCHA, ISSUE, MODELLING, WARNING, WORKAROUND MagicDraw SysML: [v2022xGolden,v2022xRefresh1]: ISSUE: Automatic assignment of the Type of the 'result' of a ReadStructuralFeatureAction not working with drag & drop. CallBehaviorAction, OutputPin, Pin, ReadStructuralFeatureAction, Action MagicDraw SysML, Systems Modeling Language, CATIA Magic:v2022xGolden, CATIA Magic:v2022xRefresh1
ISSUE, TOOL 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. InformationFlow, InformationFlow::conveyed, Connector Association, ItemFlow MagicDraw SysML, Cameo Systems Modeler, MD SysML
TIP MagicDraw, Cameo Systems Modeler, and Cameo Simulation Toolkit use the name 'English' for a "default" vendor-specific action scripting language MagicDraw SysML, MagicDraw UML, Magic Model Analyst [Cameo Simulation Toolkit], Cameo Systems Modeler
TOOL, WARNING MagicDraw/Cameo 19SP3 still supports the DEPRECATED UML Port conjugation (but it is recommended here that you DO NOT use it, even though there might be future migration for such directly conjugated Ports). Port, Port::isConjugated InterfaceBlock, ~InterfaceBlock, conjugation MagicDraw SysML, Cameo Systems Modeler
COMPLICATION, DISPLAY, FEATURE, ISSUE, MODELLING, STYLE, TOOL, WARNING, WORKAROUND 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] SysML-1.6, SysML-1.7, UML-2.5.1 Activity, Pin, Activity Diagram, ObjectFlow SysML Activity Diagram MagicDraw, UML, MagicDraw UML, Unified Modeling Language, Systems Modeling Language, SysML, MD SysML, Cameo Systems Modeler, CATIA Magic, Mathematica, Webel:MathematicaSysML, CATIA Magic:v2022xGolden
ISSUE 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. AdjunctProperty, AdjunctProperty::principal MagicDraw SysML, Cameo Systems Modeler
ISSUE, TOOL MagicDraw/Cameo 19SP3: Can't callout from ItemFlow on Connector, the Note handle pulls from the Connector not the ItemFlow Connector, callout, Note, handle ItemFlow MagicDraw SysML, Cameo Systems Modeler
ISSUE MagicDraw/Cameo 19SP3: Can't seem to show {control} notation on control Pin Pin::isControl, ObjectNode::isControlType, control Pin MagicDraw SysML, Cameo Systems Modeler, MagicDraw UML
ISSUE 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 ActivityEdge, Parameter, CallBehaviorAction, CallOperationAction, InputPin, OutputPin, Pin Continuous, «continuous», Rate, «rate» MagicDraw SysML, Cameo Systems Modeler
CAVEAT, ISSUE, TIP, TOOL 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') Property View MagicDraw SysML, Cameo Systems Modeler
ISSUE, TOOL 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. Feature, BehavioralFeature, Reception, Operation, StructuralFeature, Property provided Feature, required Feature, DirectedFeature MagicDraw SysML, Cameo Systems Modeler
ISSUE, TOOL 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. provided Feature, required Feature, DirectedFeature MagicDraw SysML, Cameo Systems Modeler
MagicDraw/Cameo 19SP3: Does not yet support AddFlowPropertyValueOnNestedPortAction AddStructuralFeatureValueAction AddFlowPropertyValueOnNestedPortAction Cameo Systems Modeler, MagicDraw SysML
ISSUE, TOOL MagicDraw/Cameo 19SP3: enumeration 'FeatureDirection' should be 'FeatureDirectionKind' (reflects known error in older SysML specification versions) FlowDirectionKind Cameo Systems Modeler, MagicDraw SysML
DISPLAY, FEATURE, TIP, TOOL MagicDraw/Cameo 19SP3: if Continuous or Discrete are applied to the Parameter of an ActivityParameterNode the keywords «continuous» or «discrete» can be optionally displayed on the ActivityParameterNode symbol ActivityParameterNode, Parameter Continuous, «continuous», Rate, «rate», Discrete, «discrete» MagicDraw SysML, Cameo Systems Modeler
CAVEAT, DISPLAY, ISSUE, TOOL 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 Parameter, Pin, InputPin, OutputPin Continuous, «continuous», Rate, «rate», Discrete, «discrete» MagicDraw SysML, Cameo Systems Modeler
ISSUE MagicDraw/Cameo 19SP3: Stakeholder: Has 'concern' NOT derived and /concernList derived; SysML-1.6 has /concern derived and concernList NOT derived. SysML-1.6 Stakeholder::/concern, Stakeholder::concernList MagicDraw SysML, Cameo Systems Modeler
ISSUE, TOOL MagicDraw/Cameo 19SP3: The property path in callout does always correspond to the SysML spec examples. callout pathname dot notation MagicDraw SysML, Cameo Systems Modeler
ISSUE MagicDraw/Cameo 19SP3: uses PascalCase instead of lowerCamelCase on some SysML compartment names MagicDraw SysML, Cameo Systems Modeler
ISSUE, TOOL MagicDraw/Cameo 19SP3: Validation of required and provided Interfaces proxied between a ProxyPort and a part with a compatible contract fails SysML-1.6 required Interface, provided Interface, InterfaceRealization, Usage, part ProxyPort, part property contract, Cameo Systems Modeler, MagicDraw SysML
CAPABILITY, FEATURE, TOOL MagicDraw/Cameo can parse the 'text' field of some mathematical Requirements and populate the constraint (and also then the constraint parameters) of a ConstraintBlock that refines a Requirement (your mileage varies). Constraint Requirement, ConstraintBlock, constraint parameter, Refine mathematics, equation
CAVEAT, TOOL MagicDraw/Cameo can't show tagged values in {braces} below owner name on instance symbols InstanceSpecification, tagged value, Stereotype MagicDraw SysML, MagicDraw UML, Cameo Systems Modeler
FEATURE, TIP, TOOL MagicDraw/Cameo derived relationships and metachain navigation are very powerful and worth exploring metachain navigation, derived relationships, MagicDraw UML, MagicDraw SysML, Cameo Systems Modeler
TIP, TOOL MagicDraw/Cameo does not explictly support tracking of satisfaction and verification of composite/compound requirements, but the "implied relations" facility can help. Satisfy, Verify, AbstractRequirement::/satisfiedBy, AbstractRequirement::/verifiedBy MagicDraw implied relationships, MagicDraw SysML, Cameo Systems Modeler
CAVEAT, ISSUE, STYLE MagicDraw/Cameo does not seem to offer the display option Apply SysML Callout Style on CentralBufferNode callout, CentralBufferNode SysML callout style MagicDraw SysML, Cameo Systems Modeler
CAPABILITY, FEATURE, TOOL Magicdraw/Cameo has a powerful "implied relation" facility for use in query tables, dependency matrices, and as element properties Relationship, DirectedRelationship dependency matrix, MagicDraw implied relationships, MagicDraw SysML, Cameo Systems Modeler, MagicDraw UML
DISPLAY, FEATURE, TOOL MagicDraw/Cameo has many tool-specific Stereotype icons, most of which can be hidden in most diagrams using Stereotype and icon display options. icon, Stereotype:icon Cameo Systems Modeler, MagicDraw SysML
CAPABILITY, FEATURE, TOOL Magicdraw/Cameo has powerful query view tables, maps, and dependency matrix diagrams! Cameo Systems Modeler, MagicDraw SysML, MagicDraw UML, table, query table, table query, report table, report generation, report
CAPABILITY, FEATURE, TOOL Magicdraw/Cameo has powerful relationship Dependency Matrix diagrams, and in many cases one can assign or remove relationships directly in the cells of the matrix just by clicking! relationship matrix, matrix, query matrix, Cameo Systems Modeler, MagicDraw SysML, MagicDraw UML
CAPABILITY, FEATURE, TOOL Magicdraw/Cameo has powerful relationship maps! Cameo Systems Modeler, MagicDraw SysML, MagicDraw UML, relationship map, derived relationships, metachain navigation
CAVEAT, FEATURE, TOOL, VARIATION MagicDraw/Cameo query tables use a single row (with a group of elements) to represent multiple targets/hits from a relationship, rather than one row per hit. MagicDraw UML, MagicDraw SysML, Cameo Systems Modeler
ASSERTION, TIP MagicDraw/Cameo support for the SysML Parametric Diagram and ConstraintBlocks for equations and mathematics is excellent, and it integrates with powerful maths engines such as Mathematica. It CAN be used on industrial strength real-world projects. Constraint ConstraintBlock, constraint parameter, SysML Parametric Diagram mathematics, equation, Mathematica, Cameo Systems Modeler, MagicDraw SysML
CAPABILITY, FEATURE, TOOL MagicDraw/Cameo supports embedding images in diagrams Magic Model Analyst [Cameo Simulation Toolkit], MagicDraw SysML, MagicDraw UML
CAVEAT, DISPLAY, STYLE, WARNING MagicDraw/Cameo tool support for Association composition "trees" is not good, and they end up being fiddly to maintain (and they can also cause issues for InformationFlows). Avoid them! Association, InformationFlow Webel Best Practice, MagicDraw UML, MagicDraw SysML, Cameo Systems Modeler
ISSUE, TOOL, WARNING 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. SysML-1.6, SysML-1.7, SysPhS-1.1 Modelica, Cameo Systems Modeler, MD SysML, MagicDraw SysML, Systems Modeling Language, SysML
GOTCHA, ISSUE, TOOL, WARNING 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) SysML-1.6, SysML-1.7, SysPhS-1.1 Block, «system», ~InterfaceBlock, InterfaceBlock, FlowProperty, FlowProperty::direction Modelica, Cameo Systems Modeler, MD SysML, MagicDraw SysML, Systems Modeling Language, SysML
ISSUE, TOOL 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). DEPRECATED:FlowPort SysPhS, Systems Modeling Language, Cameo Systems Modeler, SysML, MD SysML
GOTCHA, ISSUE, TOOL, WARNING MagicDraw/Cameo v19SP3+SysPhS-1.1: Does not cleanly export INLINE Modelica 'if/then/else' statements (a.k.a. "switching" form) SysML-1.6, SysML-1.7, SysPhS-1.1 Constraint MagicDraw SysML, Cameo Systems Modeler, MD SysML, SysPhS, Modelica
GOTCHA, ISSUE, TOOL, WARNING MagicDraw/Cameo v19SP3+SysPhS-1.1: Does not cleanly export Modelica 'when/then' statements SysML-1.6, SysPhS-1.1 Constraint MagicDraw SysML, Cameo Systems Modeler, MD SysML, SysPhS, Modelica
ISSUE, TOOL, WARNING MagicDraw/Cameo v19SP3+SysPhS-1.1: On export to Modelica sometimes repeats parts of an equation into an extending model. SysML-1.6, SysPhS-1.1 Constraint, Generalization ConstraintBlock, Block MagicDraw SysML, Cameo Systems Modeler, MD SysML, SysPhS, Modelica
DISPLAY, ISSUE, TOOL, WARNING MagicDraw/Cameo v19SP3: Does not support display of context-specific values on a FlowProperty symbol within a Port in an IBD SysML-1.6, SysML-1.7 context-specific values, initialValues compartment, initial values SysML, MD SysML, Systems Modeling Language, Cameo Systems Modeler, MagicDraw SysML
GOTCHA, ISSUE, TOOL, WARNING 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. SysML-1.6, SysPhS-1.1 Generalization ValueType, Unit, Real MagicDraw SysML, Cameo Systems Modeler, MD SysML, SysPhS, Modelica
DISPLAY, ISSUE, TOOL, WARNING 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. OpaqueExpression, Slot value property, ValueType, ValueType::unit, Unit, context-specific values, initial values, initialValues compartment MagicDraw SysML, Cameo Systems Modeler, SysML, Systems Modeling Language
CAVEAT, DISPLAY, NAMING, TOOL MagicDraw/Cameo v19SP3: The SysML 'properties' compartment of a ValueType is called 'attributes' like in UML2.5.1 for DataTypes [CLAIMED FIXED in v2021x] compartment, attributes compartment ValueType, properties compartment MagicDraw SysML, Cameo Systems Modeler
MODELLING, TIP, TOOL MagicDraw/Cameo v19SP3: UML/SysML: HOWTO Set an OpaqueExpression on a Slot that seems to be stuck on a numerical value. SysML-1.6, SysML-1.7, UML-2.5.1 Real, Slot, OpaqueExpression Real MagicDraw UML, MagicDraw SysML, Cameo Systems Modeler, Systems Modeling Language, SysML, SysMLv1.x, SysPhS, Modelica
ISSUE, NAMING, TOOL MagicDraw/Cameo v19SP3: uses the Block compartment name 'signal receptions' instead of just 'receptions'. [CLAIMED FIXED in v2021x] SysML-1.6, SysML-1.7, UML-2.5.1 receptions compartment, Signal, Reception Cameo Systems Modeler, MagicDraw UML, MagicDraw SysML
DISPLAY, ISSUE, TOOL, WARNING 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. SysML-1.6, SysML-1.7, SysPhS-1.1 Port FlowProperty, "standard" Port, value property SysML, MD SysML, Systems Modeling Language, Cameo Systems Modeler, MagicDraw SysML, SysPhS, Modelica
GOTCHA, ISSUE, TOOL, WARNING 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] SysML-1.6, SysML-1.7, SysPhS-1.1 Slot, OpaqueExpression context-specific values, initial values SysML, MD SysML, Systems Modeling Language, Cameo Systems Modeler, MagicDraw SysML, SysPhS, Modelica
GOTCHA, ISSUE, TOOL, WARNING MagicDraw/Cameo vs SysML&SysPhS: GOTCHA: Will NOT export a non-normative System «system» block to Modelica, it only recognises a plain Block «block»! SysML-1.6, SysML-1.7, SysPhS-1.1 Block, «system» Modelica, Cameo Systems Modeler, MD SysML, MagicDraw SysML, Systems Modeling Language, SysML
TIP MagicDraw/Cameo/CATIA Magic: Getting your software tools ready for the Webel IT training courses in SysML/MBSE CATIA Magic, MagicDraw SysML, MD SysML, Cameo Systems Modeler, training, Magic Model Analyst, Magic Model Analyst [Cameo Simulation Toolkit], SysML, Systems Modeling Language, MBSE, Model-Based Systems Engineering
GOTCHA, TIP, WARNING MagicDraw/Cameo/CATIA Magic: How to (try to) edit and fix a corrupt MDZIP project file SysML-1.6, SysML-1.7 CATIA Magic, MagicDraw, Cameo Systems Modeler
ISSUE, LIMITATION, TOOL 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 Property, Property::defaultValue Unified Modeling Language, UML, SysML, Systems Modeling Language, MagicDraw, MD SysML, Cameo Systems Modeler
ISSUE, TOOL MagicDraw/Cameo: 19SP3: Callout of allocatedFrom on Connector vs ObjectFlow shows «decisionInputFlow» not «objectFlow» keyword Connector, callout, ObjectFlow, DecisionNode::decisionInputFlow Allocate, allocation, «allocate» MagicDraw SysML, Cameo Systems Modeler
GOTCHA, ISSUE, TIP, TOOL MagicDraw/Cameo: 2022xGolden: TIP/GOTCHA: Mac: HOWTO Load the available plugins in the Resource/Plugin Manager SysML-1.6, SysML-1.7, UML-2.5.1 MagicDraw UML, MagicDraw SysML, CATIA Magic, CATIA Magic:v2022xGolden
CAPABILITY, DISPLAY, FEATURE, TIP MagicDraw/Cameo: A Requirement may appear on many kinds of such as a Block Definition Diagram or Package Diagram, not just a Requirement Diagram Requirement, AbstractRequirement, SysML Requirements Diagram, SysML Block Definition Diagram, SysML Package Diagram Cameo Systems Modeler, MagicDraw SysML
TIP, TOOL MagicDraw/Cameo: A structured ValueType can have value properties (each typed by a ValueType), but they list in an 'attributes' compartment (not a 'values' compartment) SysML-1.6 ValueType, Block, value property, structured ValueType MagicDraw SysML, Cameo Systems Modeler
DISPLAY, ISSUE, TOOL 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). Class, Property, compartment, attributes compartment Block, :values compartment, :parts compartment, :references compartment, parts compartment, values compartment, references compartment, IBD :features compartments inheritance, MagicDraw SysML, MagicDraw UML, Cameo Systems Modeler
CAVEAT, TOOL, WORKAROUND MagicDraw/Cameo: By default assumes custom units are both Unit and DerivedUnit and that quantity kinds are both QuantityKind and DerivedQuantityKind. Just remove the "Derived" variants if they don't apply and add the "Simple" variants. Unit, DerivedUnit, DerivedQuantityKind, QuantityKind, SimpleUnit, SimpleQuantityKind MagicDraw SysML, Cameo Systems Modeler
NAMING, TOOL MagicDraw/Cameo: By implementation the name of some Stereotype attributes and operations is UpperCase instead of lowerCase like in the UML and SysML specs attribute, Stereotype, Property, Operation MagicDraw SysML, MagicDraw UML, Cameo Systems Modeler
DISPLAY, MODELLING, OPTION, TIP, TOOL MagicDraw/Cameo: Display option: You can choose whether to show Domain Specific Language (DSL) stereotypes: 'None', 'All', 'Only Last' SysML-1.6, SysML-1.7, UML-2.5.1 Stereotype, custom Stereotype, user defined Stereotype, MD:Customization, MD:Customization::isHideMetatype Unified Modeling Language, SysML, Systems Modeling Language, MagicDraw UML, MagicDraw SysML, Cameo Systems Modeler
DISPLAY, MODELLING, TIP, TOOL MagicDraw/Cameo: Display options: On an 'entry', 'doActivity', or 'exit' Behavior of a State you may choose to display the specification code of an OpaqueBehavior or just its name. SysML-1.6, SysML-1.7, SysPhS-1.1, UML-2.5.1 State, State::entry, State::doActivity, State::exit, Behavior, OpaqueBehavior MagicDraw SysML, MagicDraw UML, Cameo Systems Modeler, MD SysML