SYSPHS12 — Humidifier example: Direct Port conjugation not permitted since SysML-1.6, prefer ~InterfaceBlock type-based conjugation (example requires migration)

p.88 describes use of UML-style direct conjugation of Ports, along with a contrived additional ~ indicator alongside Port names in BDDs Figure 72 through Figure 78:

Figure 72 through Figure 78 show block definitions for component used in the internal block diagrams shown in Figure 65 through Figure 71, respectively (one each for the total humidifier system, humidified room, relative humidity, humidifier, vapor generation plant, heating, and environment components). All ports are typed by RealSignalInElement from the signal flow library (see Subclause 11.2.1). A tilde (~) next to a port name indicates that it receives signals (conjugated port type), otherwise the port sends signals (the tilde normally appears before the type name, after a colon, but port types are omitted from the figures for brevity, because they are all the same

Since SysML-1.6, direct UML-style conjugation of Ports is no longer permitted, the examples needs to be migrated to use ~InterfaceBlock type-based conjugation (the reported has already performed migration in a highly annotated project, but it includes significant - and more consistent - renaming throughout so might not be directly suitable as a replacement).

Even once a migration to use ~InterfaceBlock is performed, a question remains about the benefit of the contrived additional ~ tilde conjugation indicator near Port names in BDDs. If the Ports in the BDDs are simply listed in compartments, instead of being shown as Association end Properties, the conjugated ~Type can be shown. Note also that the additional ~ is not shown in the corresponding IBDs anyway.

Even though not yet directly supported in the tool, creation of a customised ~InterfaceBlock Stereotype in the MagicDraw/Cameo tools since v19SP3 is straightforward.