Icon class icon_class far fa-sticky-note icon_class_computed far fa-sticky-note Note kind NAMING POLICY Policy level STRONG Specification keywords SysML-1.6 SysML-1.7 UML keywords Port SysMLv1.x keywords Block InterfaceBlock FullPort ProxyPort "standard" Port flow FlowProperty Keywords SysML Relates to WaterProcessingPlant - FlowProperty and ItemFlow example with Ports - type staging WaterProcessingPlant - FlowProperty and ItemFlow example with Ports (in BDD with structure) WaterProcessingPlant - FlowProperty and ItemFlow example with Ports (in IBD with verbose Port compartments) SimpleOpticalTelescope light flow model: staging BDD and context IBD KeplerianRefractor: simple image flow model: staging BDD Figure 2: Association block with internal structure and connector properties in SysML (and Figure 3) Overview of flowing quantities and Port types with flows SysMLv1: Cameo Simulation Toolkit: HOWTO: Send a Signal via a nested Port using InvocationOnNestedPortAction and 'onNestedPort' together with 'onPort' [with mini video] SysMLv1: Cameo Simulation Toolkit: HOW send to an intended recipient via a shared Port? ATTEMPT: Using multiple Connectors to every candidate recipient without a mediating hub [with mini video] SysMLv1: Cameo Simulation Toolkit: HOWTO send a Signal via a Port to an intended recipient via a mediating secure RoutingHub [with mini video] SysMLv1: Cameo Simulation Toolkit: HOWTO handle sending and receiving families of related Signal types with reuse of send/receive and processing logic [with mini video] SysMLv1: Cameo Simulation Toolkit: Cases for Transitions triggered by Signals sent direct to a remote target vs via Ports [with mini video] SysMLv1: Cameo Simulation Toolkit: HOWTO send a Signal via a nested Port using Action Language Helper (ALH) [with mini video] SysMLv1: Cameo Simulation Toolkit: HOWTO Handle a timeout for a Signal send/receive: Strategy: TimeEvent on Transition [with mini video] SysMLv1: Cameo Simulation Toolkit: HOWTO Handle a timeout for a Signal send/receive: Strategy: StructuredActivityNode with AcceptEventAction + TimeEvent [with mini video] Webel Radio Net: Conventions, terminology, acronyms Webel Radio Net: 'exchange' SysML Package Diagram with Signals (and Port types) Webel Radio Net: 'scheduling' SysML Package Diagram with scheduling message Signal families (and Port types) Webel Radio Net: 'radio' SysML Package Diagram with high level view of Port types for 'Radio' Signals Webel Radio Net: The RadioMessage Signals 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] [NAMING, POLICY]{STRONG} Use 'UpperCamelCase' (a.k.a. PascalCase) names for Classifiers such as UML Classes and SysML Blocks) to avoid confusion with 'lowerCase' Property names [see however special naming conventions for acronyms and SysML contract and flow Blocks] [NAMING, POLICY]{STRICT} When using acronyms in names of Classifiers either treat them as a word 'TlaLikeThis' or suffix with an underscore 'TLA_LikeThis', except at the end of the name 'LikeThisTLA' is admissable. Related notes (backlinks) [CONVENTION, MODELLING, NAMING] Block naming: If you find you've got similar blocks named 'Thing' and 'Thing2' then 'Thing' is probably better renamed 'Thing1' [ASSERTION, MODELLING, NAMING, TIP]{INFORMATIVE} [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 [CONVENTION, MODELLING, NAMING, TIP]{STRONG} Webel: If you must name your Ports or Pins, name them simply 'i', 'o', or 'io' (or 'oi') to indicate direction UNLESS you have to indicate a special role like 'iRole', 'oAuxiliary'. DO NOT use Port or Pin names like 'input', 'output', etc. [CONVENTION, NAMING]{STRICT} Webel: DO NOT name the Type (Block or InterfaceBlock) of a Port with a flow the same as the name of the 'Stuff' that flows through it; use the Webel 'F_Stuff' convention! [NAMING, POLICY]{STRICT} DO NOT use spaces in Property names or Class/Block names! If you want to communicate familiar names of elements within an organisation use a custom stereotype and tagged values (such as 'aka')! Related snippets (extracts) Visit also Visit also (backlinks) Flags Book traversal links for 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. Previous Up Next
