SysML defines defaults for multiplicities on the ends of specific types of associations.

Icon class
icon_class
fas fa-quote-left
icon_class_computed
fas fa-quote-left
Related content
Figure D.18 - Defining Structure of Power Subsystem (PowerSubsystem Breakdown)
Block, Generalization, Association: Home entertainment system
Association and Property - some cases
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.]
SysMLv1: Some invalid multiplicity examples with navigable and non-navigable Association ends. In Cameo Systems Modeler with validation.
Association and Property - some cases - with dot notation and ownership indicators
Source
OMG Systems Modeling Language (SysML) 1.7
Copyright information
About Object Management Group copyright in text extracts quoted from OMG specifications for educational purposes
Snippet kind
EXAMPLE
INFO
UML keywords
Association
AggregationKind
multiplicity
SysML keywords
HSUV sample problem
Full quote
SysML defines defaults for multiplicities on the ends of specific types of associations.
Next snippet
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.
These multiplicities may be assumed if not shown on a diagram. To avoid confusion, any multiplicity other than the default should always be shown on a diagram.
Related snippets
Related snippets (backlinks)
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)