DO NOT use Connector names that are identical to the names of the Associations that type them!

Icon class
icon_class
far fa-sticky-note
icon_class_computed
far fa-sticky-note
Note kind
NAMING
POLICY
WARNING
Policy level
STRICT
UML keywords
Type
NamedElement::name
Association
Connector
Keywords
Webel Best Practice usually strongly discourages use of punctuation in element names, but in Connector names the hyphen '-' may be used.
Relates to
Related notes
[CONVENTION, NAMING, STYLE]{STRONG} Avoid punctuation in Property names (except when used to "quote text"). You can usually avoid underscores in Property names (even if they are used in the Type name) if you can "Trust the Type"!
[NAMING, POLICY, WARNING]{STRICT} DO NOT use Property names that are identical to the names of the Classifier (Class, DataType, Block, ValueType) that type them!
[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]
Related notes (backlinks)
Related snippets (extracts)
Visit also
Visit also (backlinks)