UML2/SysML1.x: If AggregationKind 'shared' has meaning to you (and if you use it consistently without contradicting the use of 'composite' aggregation elsewhere in your model) by all means use it. Damn the purists! But it's going to die in SysMLv2 anyway.

Icon class
icon_class
far fa-sticky-note
icon_class_computed
far fa-sticky-note
Note kind
TIP
Policy level
OPTION
UML keywords
AggregationKind::composite
AggregationKind::shared
AggregationKind
SysMLv1.x keywords
part property
reference property
Keywords
Relates to
Female 0.1" pin header strips - redefinition "ladder" view
Related notes
Related notes (backlinks)
Related snippets (extracts)
  [SysML-1.6] SysML also supports properties with shared aggregation, as shown by a white diamond symbol on an association.
  [SysML-1.6] Like UML, SysML defines no specific semantics or constraints for properties with shared aggregation, but particular models or tools may interpret them in specific ways.
  [SysML-1.7] A part or shared association has a default multiplicity of [0..1] on the black or white diamond end. A unidirectional association has a default multiplicity of 1 on its target end.
Visit also
Visit also (backlinks)