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')!

Icon class
icon_class
far fa-sticky-note
icon_class_computed
far fa-sticky-note
Note kind
NAMING
POLICY
Policy level
STRICT
UML keywords
NamedElement::name
Property
Class
Connector
SysMLv1.x keywords
Block
Keywords
Of all the Webel best practice items, this is one of the most important! Put the UML/SysML-friendly naming convention first! Always!
It is tempting to think that using "human friendly" naming will help communication with your non-UML/SysML stakeholders. Don't do it, it will backfire. All it will achieve is a complete mess because it in fact means employing no convention at all.

Instead, use the strict Webel naming conventions, and use a custom stereotype with tagged values such as 'aka' to include information on one or more names by which an element is known within an organisation. This works like a charm.

A stricter code-like Block naming example using French-style "vin rouge" naming is shown here:

Webel Best Practice: Webel Parsing Analysis for SysML: Track and display alternative names, human friendly names, organisation-specific names, and identifiers using tagged values for a custom stereotype «pa:term» (adapt or extend as required).

Visit also:

Webel Best Practice: Webel: SysML: DO NOT sacrifice modelling naming conventions for the mere sake of carrying organisation-specific names! Instead use tagged values of custom stereotypes as metadata to carry alternative names in parallel with systematic model element names.
Webel: SysML: "Really long human friendly element names with spaces make my diagrams easier to read". Dr Darren says "No they don't! Prefer code-like naming (or anonymous for typed elements) wherever possible. Use custom tagged values for other names!"
Relates to
Figure D.19 - Internal Structure of the Power Subsystem (Internal Block Diagram)
Figure D.24 - Defining Fuel Flow Constraints (Parametric Diagram)
Figure D.24 - Defining Fuel Flow Constraints (Parametric Diagram) [ANNOTATED]
Figure D.26 - Defining Analyses for Hybrid SUV Engineering Development (Block Definition Diagram)
Figure D.32 - Establishing Mathematical Relationships for Fuel Economy Calculations (Parametric Diagram)
Figure D.32 - Establishing Mathematical Relationships for Fuel Economy Calculations (VARIATION: labels inside)
Figure D.34 - Defining Straight-Line Vehicle Dynamics Mathematical Constraints (Definition of Dynamics)
Figure 8-17: Vehicle specialization
Figure 15-8: Example of Structural Allocation
Block, Generalization, Association: Home entertainment system
More block Generalization examples: Home entertainment system
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} Prefer 'UpperCamelCase' (a.k.a. PascalCase) names for Behaviors such as Activities intended for use in CallBehaviorActions, or at least use a 'Capital first letter'; avoid 'all lower case' (as it leads to confusion with lower case Action names)
[NAMING, POLICY]{STRONG} Prefer anonymous Actions, or if they must be named, prefer code-like 'lowerCamelCase' or completely 'lower case' (if you do absolutely insist on having spaces in action names, but please no other punctuation).
[NAMING, POLICY]{STRICT} SysML: Naming: Always use either anonymous or first letter lower case for Property, ObjectNode and InstanceSpecification names; no exceptions (unless using names to "quote text")! Valid: 'lowerCamelCase' OR 'tla' vs TLA acronym OR 'uCC' vs UpperCamelCase
[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]{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.
[ASSERTION, MODELLING, NAMING, TIP]{STRICT} Webel: SysML: DO NOT sacrifice modelling naming conventions for the mere sake of carrying organisation-specific names! Instead use tagged values of custom stereotypes as metadata to carry alternative names in parallel with systematic model element names.
[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)
Related snippets (extracts)
Visit also
Visit also (backlinks)