MultiplicityElement::upperValue

A multiplicity on the composing end of a composite aggregation must not have an upper bound greater than 1. inv: isComposite and association <> null implies opposite.upperBound() <= 1

Source

Unified Modeling Language 2.5.1

Association and Property - some cases - with dot notation and ownership indicators

Gallery

Tutorial

TRAIL: Webel's ultimate guide to Systems Modeling Language (v1) with MagicDraw/Cameo

Section

01:02: UML 101 for model-based systems engineering with SysMLv1

Slide kind

UML Class Diagram

Association and Property - some cases

Gallery

Tutorial

TRAIL: Webel's ultimate guide to Systems Modeling Language (v1) with MagicDraw/Cameo

Section

01:02: UML 101 for model-based systems engineering with SysMLv1

Slide kind

UML Class Diagram

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.

Source

OMG Systems Modeling Language (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.

Source

OMG Systems Modeling Language (SysML) 1.7

The semantics are undefined for adding a value that violates the upper multiplicity of the StructuralFeature, and for adding a new value to a StructuralFeature with isReadonly=true after initialization of the object that would have the value.

Source

Unified Modeling Language 2.5.1

Subscribe to MultiplicityElement::upperValue

We are Australia's Systems Modeling Language (SysML^®) and Model-Based Systems Engineering (MBSE) specialists!

Catch our SysML/MBSE course Early Bird Deal 30% off all courses fully booked by 31st Mar 2025!

The home of the Webel Parsing Analysis recipe for Model-Based Systems Engineering with SysML^®

Visit our Client showcase