Operations and Signal Receptions!?

This video demonstrates the use of UML / SysML Operations and Signal Receptions using Cameo Systems Modeler (MagicDraw). Cameo Simulation Toolkit is used to demonstrate the behaviors in Sequence Diagrams and Activity Diagrams.
#SysML #UML #simulation #ModelBasedSystemsEngineering #MBSE #stc #digitalEngineering #CameoSystemsModeler #MagicDraw

[@idontknow1134]

Well done

[@muondude]

I really enjoy your videos and generally find them helpful. However, a suggestion: instead of jumping right into a model you already created could you should how you built the example? That would really add to the learning experience IMHO. Or can you post the examples that you show? TIA

[@ericbaker8807]

8:02 Has fUML been updated and implemented in 2024x version of Cameo? Or will it ever be? Signal Reception methods not being invokable seems like an oversight to me, no?

[@andrepenn2996]

Can you also clarify why have an input "target" on a call operation action? What is its purpose? Can you use the output of another action as an input to the "target" of the call operation action instead of readself and valueSpecification? Any comment as to why call operation action is not used often or when it is preferred over call behavior action? I didn't get a clear understanding of Friedenthal's text (page 234) when he referred to it as "When the action is executed, it sends a request to the target object, which handles the request.." In your example, is the "performBuiltInTest" the target? Or would you be able to do another video regarding call operation action with the "target" port in use? I apologize for the lengthy comment.

[@andrepenn2996]

Thank you. To clarify, from what I've observed, the method of an operation can be the same name as the operation or a different name. Is that correct?

[@andrepenn2996]

Unable to leave a comment on your "Target Pin" video. So I'll leave my comment here as it pertains to trying to understand the "target pin" discussion. By the way, NICE job on the videos. It is confusing that the target pin's direction is shown as an "input" on the send signal action. The thought is that the target "is a destination" hence the direction should be an output pin from the send signal action to the destination action. I know it may be the specification, but it is confusing. I naturally visualize or associate "target" as a "from-to" (source to destination). It seems reversed. Also, I recall the send signal action "sends" the signal and the accept event accepts the signal That signal is the token that flows. Not sure why the "target" pin is needed if both the send signal action and the accept signal action produce the token that is the name of the signal for both respectively. BIT Status Transmitted accepts that "BIT Status Transmitted" signal and produces that token. Don't understand why the "bitStatus" pin is needed. Will revisit the "Target Pin" video again.

[@billnewsr.9314]

Seems odd that you would name 2 functions with the ALMOST the SAME name. You should have used distinctly different names for clarity sake. Have been writing software for over 45 years now and at first I was very confused by your naming of the 2 functions. Hope this helps!

[@brianMoberley]

For sure! I agree. Definitely should have given them distinct names. Sorry for the confusion. I hope the rest was helpful.

[@billnewsr.9314]

@@brianMoberley very helpful for sure.