Learn about Webel's comprehensive SysMLv2 Workshop Seminar course!
Webel now has a SysMLv2 Online Self-Study course with self-test Quizzes!
Learn about the Webel Q&A     online self-testing system for SysML v2/v1

Activities as blocks can have associations between each other, including composition associations. Composition means that destroying an instance at the whole end destroys instances at the part end.

Icon class
icon_class
fas fa-quote-left
icon_class_computed
fas fa-quote-left
Related content
Figure D.37 - Decomposition of “Accelerate” Function (Activity and Object Flow Breakdown)
Figure 11-1: Block definition diagram with activities as blocks
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.]
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
Activity
Association
AggregationKind::composite
SysML keywords
Block
Full quote
Activities as blocks can have associations between each other, including composition associations. Composition means that destroying an instance at the whole end destroys instances at the part end.
Next snippet
When composition is used with activity blocks, the termination of execution of an activity on the whole end will terminate executions of activities on the part end of the links.
Related snippets
Related snippets (backlinks)
When composition is used with activity blocks, the termination of execution of an activity on the whole end will terminate executions of activities on the part end of the links.
Associations can be used between activities and classifiers (blocks or value types) that are the type of object nodes, variables, or parameters in the activity, as shown in Figure 11-5.
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)