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
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, 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
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
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
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, 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
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
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
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
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
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)
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
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
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 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
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
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
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
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
TIP SysML v2 (unlike SysML v1.x) is not directly based on Unified Modeling Language (UML) SysMLv2 SysMLv2, SysML, Systems Modeling Language
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
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
ISSUE SysML-1.6 Typo 'Acitivies' in Figure 4-3: SysML Package Structure SysML-1.6
ISSUE SysML-1.6 Typo: There is no "hybridSUV" Lifeline in Figure D.9 - there is 'vehicleInContext:HybridSUV' SysML-1.6
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: '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
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: AbstractRequirement: direction of /tracedTo wrong in Attributes description AbstractRequirement, AbstractRequirement::/tracedTo
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
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: 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: 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: 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»
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: 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: 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 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: 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 '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 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: 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 D.19 has an unnecessary Comment with the name of the 'ctrl' Port SysML-1.6 HSUV sample problem
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: 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
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.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»
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.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.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.32 does not have 'incline' value property connected SysML-1.6 SysML specification figure, BindingConnector, value property
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: 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 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: 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: 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 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 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: 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: Missing correct diagram for 'Figure 9-5: Item Flow Stereotype' SysML-1.6 ItemFlow
ISSUE SysML-1.6: Multiple references to ControlValue should be ControlValueKind (known issue) SysML-1.6 ControlValueKind
ISSUE SysML-1.6: Name 'knockSensor' should be 'isKnocking' for consistency with D.21 SysML-1.6 HSUV sample problem
ISSUE, NAMING 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 HSUV sample problem
ISSUE 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
ASSERTION, ISSUE SysML-1.6: Needs a constraint on ~InterfaceBlock making the implied inversion of provided/required Interfaces explicit SysML-1.6 Interface, InterfaceRealization, Usage InterfaceBlock, ~InterfaceBlock, ~InterfaceBlock::original
ISSUE 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-1.6 FlowProperty
ISSUE SysML-1.6: reference to 'association between Spigot and Faucet Inlet in Figure 9-11' should say 'Figure 9-8' SysML-1.6 SysML specification figure
ISSUE SysML-1.6: reference to 'Figure 17-1' should be 'Figure 16-7' SysML-1.6 SysML specification figure
ISSUE SysML-1.6: Reference to 'House 2' for Figure 9-11 is inconsistent. Should probably just be 'House'. SysML-1.6 SysML specification figure
ISSUE SysML-1.6: Reference to 'in the decomposition from Figure 9-17' should be '...Figure 9-16' SysML-1.6 SysML specification figure
ISSUE SysML-1.6: References to 'ecu:PowerControlUnit' should be 'pcu:PowerControlUnit' SysML-1.6 HSUV sample problem, SysML specification figure
ISSUE SysML-1.6: Refers to both 'composite requirements' and 'compound requirements' (clearly as identical concepts) SysML-1.6 composite (compound) requirement, Requirement
ISSUE 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 HSUV sample problem
ISSUE SysML-1.6: Spec Figure D.41 refers to 'i:Interior' not 'i:InteriorSubsystem', inconsistent w.r.t. Figure D.16. SysML-1.6 HSUV sample problem
ISSUE 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). SysML-1.6 HSUV sample problem
ISSUE, NAMING SysML-1.6: Stereotype keyword consistency: «testCase» in Figure 16-6, «TestCase» in Figure 16-7 SysML-1.6 «keyword», Stereotype TestCase
ISSUE SysML-1.6: text concerning Figure 15-4 'The allocation to Activity6'; the allocation is FROM Activity6. SysML-1.6
ISSUE 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
ISSUE 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 SysML specification figure, AbstractRequirement::text
ISSUE SysML-1.6: The 'Figure 15-7: Example of flow allocation from ObjectNode to FlowProperty' does not allocate to any FlowProperty SysML-1.6 FlowProperty, Allocate, SysML specification figure
ISSUE 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 Allocate, SysML specification figure
ISSUE 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' SysML-1.6 ObjectNode, ObjectFlow, Connector HSUV sample problem, ItemFlow, Allocate, allocation, «allocate»
ISSUE 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. SysML-1.6 Dependency::client, Dependency::supplier AllocateActivityPartition
ISSUE 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
ISSUE 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) SysML-1.6 Interface, InterfaceRealization, Usage, BehavioredClassifier::interfaceRealization
ISSUE 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 specification figure, Block, part property
CAVEAT, ISSUE SysML-1.6: The spec sample diagrams D.27 has Expose relationships to ValueType, they should be to value properties. SysML-1.6 HSUV sample problem, View, Viewpoint
ISSUE SysML-1.6: The spec version of Figure D.37 does not show the breakdown from the top-level Accelerate activity SysML-1.6 Activity
CAVEAT, ISSUE 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 HSUV sample problem, View, Viewpoint
ISSUE SysML-1.6: Typo in figure name 'Figure 4-2: SysML Extension of UMLFigure' SysML-1.6 SysML specification figure
ISSUE SysML-1.6: Typo: 'Binding connectors, as defined in Clause 8 are used' SysML-1.6
ISSUE SysML-1.6: Typo: Constraint name: Copy::1_source_and_ta[r]get_are_requirements SysML-1.6 Copy
ISSUE SysML-1.6: Typo: Figure 8-12 'diamter' should be 'diameter' SysML-1.6
ISSUE 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 ValueType
ASSERTION, COMPLICATION, ISSUE 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' SysML-1.6, SysML-1.7 AggregationKind, AggregationKind::composite FlowProperty, ValueType, value property, Block SysML, Systems Modeling Language
MODELLING, TIP SysML/MBSE: Many videos, tutorial slides, and guides to MBSE with SysML present particular modelling recipes as though they are THE way to do something in SysML, not just ONE way of doing it in SysML. They are not necessarily enforced by the SysML spec. SysML-1.6, SysML-1.7 Systems Modeling Language, SysML, MD SysML, Model-Based Systems Engineering, scenario
TIP SysML/SysPhS + Modelica: The variable 'time' is known to Modelica and need not be explicitly declared as a constraint parameter for a Constraint on a SysML ConstraintBlock SysPhS-1.1 Constraint SysPhS, SysML, Systems Modeling Language, Modelica
CONVENTION, MODELLING, NAMING SysML/SysPhS-1.1: Anonymous Property or Action names may not be an option if: You are exporting to Modelica or Simulink; You absolutely need names for generated query reports (such as generated Interface Control Documents). NamedElement::name, NamedElement, Property, Action, Port "standard" Port, block property, part property, reference property SysML, SysPhS, Systems Modeling Language, Modelica, Simulink, Simscape, Stateflow, Webel Best Practice
MODELLING, TIP, TOOL SysML/UML: MagicDraw/Cameo: Activity Diagrams: All Pins of CallBehaviorActions and CallOperationActions MUST be displayed (synchronised). All ActivityParameterNodes MUST be shown on the frame of an Activity Diagram. 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
COMPLICATION, CONVENTION, GOTCHA, LIMITATION, NAMING, TOOL SysML/UML: MagicDraw/Cameo: GOTCHA: Connecting a typed OutputPin to an untyped (UNSPECIFIED) InputPin with an ObjectFlow changes the type of the InputPin SysML-1.6, SysML-1.7, UML-2.5.1 Activity, CallBehaviorAction, Action, Parameter, Activity Diagram, ObjectFlow, Pin, InputPin, OutputPin SysML Activity Diagram, MD::UNSPECIFIED Systems Modeling Language, SysML, SysMLv1.x, Wolfram Language, MagicDraw SysML, Cameo Systems Modeler, CATIA Magic
MODELLING, NAMING, TIP, TOOL SysML/UML: MagicDraw/Cameo: The name of an ActivityParameterNode does not always stay in synch with its Parameter (and it is not always desirable that it does). 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