SysML also supports properties with shared aggregation, as shown by a white diamond symbol on an association.

Icon class
icon_class
fas fa-quote-left
icon_class_computed
fas fa-quote-left
Related content
Figure D.16 - Defining Structure of the Hybrid SUV System (Hybrid SUV Breakdown)
Figure D.18 - Defining Structure of Power Subsystem (PowerSubsystem Breakdown)
SysML "shared" Property example: two Triangles share one LineSegment edge.
SysML "shared" Property challenge as objects: two Triangles share one LineSegment edge.
The first known practical telescopes were refracting telescopes
Focus BDD for block RefractingTelescope
Cameo Simulation Toolkit: GOTCHA: In the Variable pane reference properties are hidden by default (show them using the Options pulldown menu)
Female 0.1" pin header strips - redefinition "ladder" view
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.
SysMLv1: A part Property or reference Property is not necessarily a 'memberEnd' or 'ownedEnd' of an Association ('association' or 'owningAssociation'). But an Association always as at least 2 'memberEnd' Properties. [With some MagicDraw/Cameo tool tips.]
SysML: Syntax ain't Semantics: FUN CHALLENGE: SysMLv1 block property aggregation: 'The tornado chaser plane "has" a chaser car "with" a chaser team.'
SysMLv1: TIP: You can strengthen the ill-defined semantics of Property 'aggregation' (an AggregationKind) by applying custom Stereotypes to a Property, documented with its intended use. Not perfect, but better than not. EXAMPLE: «assembled»
Source
OMG Systems Modeling Language (SysML) 1.6
Copyright information
About Object Management Group copyright in text extracts quoted from OMG specifications for educational purposes
Snippet kind
INFO
UML keywords
AggregationKind::shared
AggregationKind
Association
Property
Full quote
SysML also supports properties with shared aggregation, as shown by a white diamond symbol on an association.
Next snippet
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.
Related snippets
Related snippets (backlinks)
A property typed by a Block that does not have composite aggregation is classified as a reference property.
The supported variety of notations for associations and association annotations has been reduced to simplify the burden of teaching, learning, and interpreting SysML diagrams for the systems engineering user.
Notational and metamodel support for n-ary associations and qualified associations has been excluded from SysML.
The use of navigation arrowheads on an association has been simplified by excluding the case of arrowheads on both ends, and requiring that such an association always be shown without arrowheads on either end.
An “X” on a single end of an association to indicate that an end is not navigable has similarly been dropped, as has the use of a small filled dot at the end of an association to indicate that the end is owned by the associated classifier.
Visit also
Visit also (backlinks)