ARCHIVAL (2022): This content is now considered historical only!

[HISTORICAL] SysML: Some users employed the ~ tilde prefix for a conjugated Port type long before it was introduced for ~InterfaceBlock and you MAY use it to name a regular Block that is not an ~InterfaceBlock

 ARCHIVAL (2022): This content is now considered historical only!
Icon class
icon_class
far fa-sticky-note
icon_class_computed
far fa-sticky-note
Note kind
ASSERTION
MODELLING
NAMING
TIP
Policy level
INFORMATIVE
Specification keywords
SysML-1.6
SysMLv1.x keywords
Block
~InterfaceBlock
InterfaceBlock
Keywords
Dr Darren says:
I was using the ~ tilde prefix to indicate a manually conjugated type in attempting modelling of physical systems with UML even before SysML existed.
Relates to
Related notes
[NAMING, POLICY]{STRICT} For SysML Blocks and InterfaceBlocks used to type Ports with contracts use the naming convention 'I_UpperCamelCase' [may be combined with acronymn conventions]
[TIP] If you are using Blocks (not InterfaceBlocks) to Type your Ports just use "manual" feature-by feature direction inversion to achieve type conjugation (and you can even use a ~ tilde prefix)
[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!
[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)
[NAMING, POLICY]{STRONG} Webel: For SysML Blocks and InterfaceBlocks used to type Ports with physical flows use 'F_UpperCamelCase' [may be combined with acronymn conventions]. The trailing part (after the underscore '_') may indicate the type that flows.
Related notes (backlinks)
Related snippets (extracts)
Visit also
Visit also (backlinks)