Avoid mixing flow properties on the Type of a Port with directed features (operations and values); One distinguishes between "ports with flows" and "contract ports".

Icon class
icon_class
far fa-sticky-note
icon_class_computed
far fa-sticky-note
Note kind
POLICY
Policy level
STRONG
SysMLv1.x keywords
FlowProperty
DirectedFeature
InterfaceBlock
~InterfaceBlock
Keywords
Relates to
Some valid FullPorts from the outside
Conjugation in SysML-1.7 is Type-based: InterfaceBlock, ~InterfaceBlock, and DirectedFeature
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.
[ASSERTION] SysML: Typing a Port by an InterfaceBlock or ~InterfaceBlock does NOT imply that the Port is a ProxyPort (but ProxyPort must be typed by an InterfaceBlock or ~InterfaceBlock)
Related notes (backlinks)
Related snippets (extracts)
  [SysML-1.6] [SysML1.6: PREFER SysML1.7] A DirectedFeature indicates whether the feature is supported by the owning block (provided), or is to be supported by other blocks for the owning block to use (required), or both ...
  [SysML-1.6] A FlowProperty signifies a single flow element to/from a block. A flow property has the same notation as a Property only with a direction prefix (in | out | inout). Flow properties are listed in a compartment labeled flow properties.
  [SysML-1.6] The ~InterfaceBlock stereotype (shall be pronounced: "conjugated interface block") is a specialization of InterfaceBlock that has the same features as its original InterfaceBlock except that its DirectedFeatures and FlowProperties are reversed (conjugated
Visit also
Visit also (backlinks)