SysMLv1.7: A port MAY be typed by a ValueType (and validates in Cameo Systems Modeler) but this is NOT recommended best practice. Prefer a Block or InterfaceBlock with a directed FlowProperty typed by a ValueType.

Icon class
icon_class
far fa-sticky-note
icon_class_computed
far fa-sticky-note
Note kind
ASSERTION
WARNING
Policy level
INFORMATIVE
Specification keywords
SysML-1.7
UML keywords
Port
SysMLv1.x keywords
flow port
FlowProperty
FlowProperty::direction
ValueType
Block
InterfaceBlock
Keywords
Click on the image to view it full size

In SysMLv1.7, a port MAY be typed by a ValueType. There is no constraint that prevents it, and it validates in Magic Cyber-Systems Engineer® (Cameo Systems Modeler®).

But using a ValueType as the type of a port is NOT recommended best practice

Prefer a Block or InterfaceBlock with a directed FlowProperty typed by a ValueType.

Use of a ValueType to type a port is related to the DEPRECATED concept of an atomic flow port (as opposed to a nonatomic flow port typed by the DEPRECATED FlowSpecification). See annex C.3.2.2 FlowPort of the SysMLv1.7 specification.

Relates to
Related notes
[DEPRECATION] Although the older SysML FlowPort is strictly deprecated, the term "ports with flows" is often used for a Port typed by a block with a FlowProperty. The expression "flow port" is best avoided to prevent confusion.
[DEPRECATION, TOOL, WARNING]{STRONG} SysML: MagicDraw/Cameo: DO NOT use the FlowPort or FlowSpecification menu items or smart manipulator items they are completely OBSOLETE (they create fully DEPRECATED SysML model element types)! Use FlowProperty on Block features instead.
[GOTCHA, TIP]{INFORMATIVE} SysMLv1: A 'part property' in SysMLv1 does not formally include 'port' (which is considered a special kind of property), even though the Port metaclass in UML2 extends Property and a 'port' may have 'composite' aggregation and be typed by a Block.
Related notes (backlinks)
Related snippets (extracts)
Visit also
OMG Systems Modeling Language (SysML) 1.7
Visit also (backlinks)