Icon class icon_class far fa-sticky-note icon_class_computed far fa-sticky-note Note kind CONVENTION NAMING Policy level STRICT UML keywords Port SysMLv1.x keywords FlowProperty InterfaceBlock ~InterfaceBlock Block Keywords Webel Best Practice Relates to Figure D.25 - Detailed Internal Structure of Fuel Delivery Subsystem (Internal Block Diagram) SimpleOpticalTelescope light flow model: staging BDD and context IBD KeplerianRefractor: simple image flow model: staging BDD Related notes [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) [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. Related snippets (extracts) Visit also Visit also (backlinks) Flags Book traversal links for 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! Previous Up Next
