Webel: Mathematica: CONVENTION: The Stereotype keyword «functional» indicates a "pseudo functional" representation of functional in SysML. There are limits to representation of functional programming in SysML, but it can be informative and is worth doing.

Webel IT Australia promotes the amazing Mathematica tool and the powerful Wolfram Language and offers professional Mathematica services for computational computing and data analysis. Our Mathematica tips, issue tracking, and wishlist is offered here most constructively to help improve the tool and language and support the Mathematica user community.

DISCLAIMER: Wolfram Research does not officially endorse analysis by Webel IT Australia.

Icon class

icon_class

far fa-sticky-note

icon_class_computed

far fa-sticky-note

Note kind

Policy level

UML keywords

«keyword»

Activity

ValueSpecificationAction

InputPin

SysMLv1.x keywords

SysML Activity Diagram

Mathematica keywords

Symbol

function

Webel Mathematica keywords

«functional»

pseudo functional

Keywords

Click on the image to view it full size

In Webel SysML4Mathematica (v1) the custom Stereotype «functional» indicates a "pseudo functional" representation of functional in SysML. There are limits to representation of functional programming in SysML, but it can be informative and is worth doing.

Simply passing a function Symbol around as an argument is easy. The tricky part is representing specific invocations of functions, especially when the number of arguments accepted by various injected functions differs, and where the return "type" varies, as it often can with Wolfram Language. In some cases this can be handled using an OpaqueBehavior with more than one 'out' Parameter.

Visit also:

Webel: SysML4Mathematica: SysML Activities and SysML Activity Diagrams CAN represent some functional programming paradigms (sort of). You can type Parameters by encapsulations of functions and pass them to/from InputPins/OutputPins of Actions.

Webel: Programmers who can count higher than one (1) know that you don't have to choose exclusively between object-orientation (and classes) and functional programming. You can have your cake and eat it. It's not XOR!

Relates to

The sigsUp function with OptionsPattern modelled as a SysML Activity (and with "pseudo functional" representation)

The sigsUp/Down functions as a SysML BDD: With Options Block and pseudo functional indicators

Extract Options from an OptionsPattern[] in a SysML Activity (2) DETAILED

Related notes