Icon class icon_class far fa-sticky-note icon_class_computed far fa-sticky-note Note kind NAMING POLICY Policy level STRICT SysMLv1.x keywords ValueType QuantityKind Keywords Webel Best Practice Webel: SysMLv1.x: TIP: The name and documentation of a ValueType can indicate and specify more than just the unit and quantity kind. Example: A ClockFrequency may document how the frequency is measured. Example: WeightOnEarth. Relates to Figure 8-12 - Block diagram for the Wheel Package (WheelHubAssembly) Figure 8-14: Defining Value Types with units of measure from the International System of Units (SI) SysML ValueType and QUDV overview QuantityKind and ValueType example - length vs radius vs radius of tire QuantityKind and ValueType example - frequency vs clock frequency vs sound frequency Related notes [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] [CONVENTION, NAMING, POLICY]{STRONG} Webel: SysMLv1.x: AVOID (where possible) ValueType names that are the same as the name of units or unit symbols 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. [CONVENTION, MODELLING, NAMING] Block naming: If you find you've got similar blocks named 'Thing' and 'Thing2' then 'Thing' is probably better renamed 'Thing1' [CONVENTION, NAMING, POLICY]{STRONG} Webel: SysMLv1.x: AVOID (where possible) SysML Unit names that are the same as unit symbols. Unit names SHOULD start with a lower case Latin alpha letter. Custom Unit names should be a single lower case word or lowerCamelCase. [NAMING, TOOL] MagicDraw/Cameo: SysMLv1.x: ValueType naming: The ISO-80000 libraries use 'lower case' (sometimes with spaces for compound units and/or with [scaling] indicated in square brackets). [CONVENTION, NAMING, POLICY]{STRONG} Webel: SysMLv1.x: AVOID (where possible) ValueType names that are the same as the name of units or unit symbols [ISSUE] SysML-1.6: Use of ValueTypes named like units in Figure 8-12 and Figure 8-14 is inconsistent w.r.t. some other specification diagrams and examples (but not necessarily wrong) Related snippets (extracts) Visit also Visit also (backlinks) Flags Book traversal links for SysMLv1.x: ValueType naming: The Webel convention is 'UpperCamelCase' (a.k.a. PascalCase). Previous Up Next
