Eclipse Community Forums: Papyrus » SysML V1.6 Call Bahior Action Name and Fork

Home » Modeling » Papyrus » SysML V1.6 Call Bahior Action Name and Fork (Activity Diagram does not behave as I would expect it)

SysML V1.6 Call Bahior Action Name and Fork [message #1862741]

Tue, 26 December 2023 02:29

Eclipse User

Hi,
when I add a Call Behavior Action to an activity diagram and assign it to a already existing Actvity (e.g. Activity1) , I would expect 2 things:

The name of the assigend Activity is shown in Call Behavior Action name sperated by a colon (xyz : Activity1) ánd a fork is dislpayed.

Neither one nor the other is the case.
I could not find any setting where I could "switch on" this behavior.

Can anybody please give short hint if my expections are wrong or where I could configure something.

Thanks

Marcus

Re: SysML V1.6 Call Bahior Action Name and Fork [message #1862835 is a reply to message #1862741]

Sun, 31 December 2023 08:50

Eclipse User

Hi Marcus,
seems to be OK to me. I recorded a screen cast.

Behavior is as defined by the SysML 1.6 specification (https://www.omg.org/spec/SysML/1.6), which in this case refers to the UML 2.5 specification (https://www.omg.org/spec/UML/2.5.1).
/Carsten

Attachment: drop existing activity.mp4
(Size: 1.51MB, Downloaded 79 times)

[Updated on: Sun, 31 December 2023 09:37] by Moderator

Re: SysML V1.6 Call Bahior Action Name and Fork [message #1862888 is a reply to message #1862835]

Thu, 04 January 2024 07:56

Eclipse User

Hi Marcus,

The goal of drop action is only to create a new CallBehaviorAction configured with the activity as behavior feature. I don't understand why you are expected a Fork node ?

Best regards,
Pauline

Previous Topic:	SysML - multiline constraint
Next Topic:	No architecture contexts

Goto Forum:

-=] Back to Top [=-

Current Time: Sun Jul 13 16:09:25 EDT 2025

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter