Icon class icon_class far fa-sticky-note icon_class_computed far fa-sticky-note Note kind NAMING POLICY STYLE Policy level STRONG Keywords Webel Best Practice Webel Parsing Analysis SysML Systems Modeling Language Relates to Figure D.3 - Establishing Structure of the User Model using Packages and Views Related notes Related notes (backlinks) [ANTI-PATTERN, CAVEAT, MODELLING, NAMING, WARNING]{INFORMATIVE} SysML: Naming: You may include Block, ValueType, and Signal names in the names of Behaviors (such as Activities) as long as this does not undermine the principles of functional analysis and allocation. [ASSERTION]{SUGGESTED} Webel vs SysPhS-1.1: Annex A.5: Assume the conversion value property name 'SaturationVaporPressure::hPa2Pa' stands for 'hectopascal to pascal'. [ASSERTION]{SUGGESTED} Webel vs SysPhS-1.1: Annex A.5: Assume the conversion value property names 'WaterTank::litpSec2mLitpHr' and 'EvaporationCalculation2::litPSec2mLitPHour' stand for 'litres per second to millilitres per hour' [ISSUE]{SUGGESTED} SysPhS-1.1: Annex A.5: Humidifier: Naming not very consistent across parts, input/output Port name, value properties, or constraint parameters [DISPLAY, STYLE]{OPTION} In SysML diagrams, showing the context name and type in the diagram frame can lead to clutter and is not always clear to non-SysML stakeholders (although that is the style used in the specification samples) Related snippets (extracts) Visit also Visit also (backlinks) Flags Book traversal links for The Webel modelling style, naming conventions, and Best Practices for SysML are more consistent than most SysML specification diagrams. When following Webel courses please DO NOT use the spec sample diagrams as visual references! Previous Up Next
