Webel: SysMLv1: TIP: Use semantically meaningful Association names and/or custom Stereotypes where applicable. They can also often be used as pseudo OWL/RDF semantic triples. But don't use Association names where an ItemFlow can capture an exchange item!

Icon class
icon_class
far fa-sticky-note
icon_class_computed
far fa-sticky-note
Note kind
MODELLING
TIP
Policy level
RECOMMENDED
Specification keywords
SysML-1.6
SysML-1.7
UML-2.5.1
UML keywords
Association
NamedElement::name
Stereotype
«keyword»
custom Stereotype
SysMLv1.x keywords
ItemFlow
Keywords

It is often useful to use semantically meaningful names on Associations.

In the case of uni-directional Associations, they can also be used to make a quick form of OWL/RDF-like pseudo semantic triple, as used often in the  Webel Parsing Analysis recipe for SysML.

But don't use Association names instead of ItemFlows with exchange items!

If you find yourself repeating a 'name' on more than one Association, it's usually a hint that you need a custom Stereotype and «keyword» to promote Single Source of Truth (SSOT) and Don't Repeat Yourself (DRY). It needn't be a fancy ontology, just collating such custom Stereotypes in a single Profile is often adequate.

Visit also: Webel: SysMLv1: TIP: Consider using high level "communication" Associations between Blocks in BDDs with ItemFlows and corresponding context IBDs WITHOUT any Ports, with Connectors typed by the Associations (as well, in parallel with your port-based IBDs).
Relates to
Related notes
[POLICY]{STRONG} About the Single Source of Truth (SSOT) and Don't Repeat Yourself (DRY) principles
[DISPLAY, REQUIREMENT]{STRICT} Webel Parsing Analysis: It SHOULD be possible to relate one Parsing Analysis Container to another and stereotype that relationship as an RDF/OWL-like semantic triple
[DISPLAY, MODELLING, NAMING, POLICY, TIP]{STRICT} Webel Parsing Analysis: Pseudo Semantic Triple: For «pa:triple» applied to a named one-to-one or one-to-many uni-directional Association, the non-navigable end Property is the subject, the name is the predicate, the navigable end Property is the object.
[DISPLAY, MODELLING, NAMING, POLICY, TIP]{STRICT} Webel Parsing Analysis: Pseudo Semantic Triple: For «pa:triple» applied to a named one-to-one or one-to-many uni-directional Association, the non-navigable end Property is the subject, the name is the predicate, the navigable end Property is the object.
[DISPLAY, MODELLING, NAMING, POLICY, TIP]{STRICT} Webel Parsing Analysis: Pseudo Semantic Triple: When «pa:triple» is applied to a named uni-directional Association the name and a consistent direction arrow should be displayed on the Association symbol in diagrams.
[MODELLING, POLICY]{STRICT} Webel Parsing Analysis: SysML: Pseudo Semantic Triple: A «pa:triple» may be applied to a Dependency between SysML Blocks and/or Actors or Properties typed by them.
[TIP]{SUGGESTED} Webel Parsing Analysis: You may create custom stereotypes applicable to a Dependency or a uni-directional Association to represent a «predicate» much like a semantic triple (subject-predicate-object) in OWL/RDF.
Related notes (backlinks)
Related snippets (extracts)
Visit also
The Webel Parsing Analysis recipe for SysML
Webel Parsing Analysis as a meta-process: Snippets before Requirements!
Web Ontology Language (OWL) zone
Visit also (backlinks)