Webel: SysML4Mathematica: An Association used as the Type of an argument or return is represented by a Block '<||>'. A List used as as the Type of an argument or return is represented by a Block '{}'.

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
CONVENTION
MODELLING
NAMING
Policy level
STRICT
Specification keywords
SysML-1.6
SysML-1.7
UML-2.5.1
UML keywords
Activity
OpaqueBehavior
SysMLv1.x keywords
Block
ConstraintBlock
Keywords

Note that while a SysMLv1.x ValueType can be structured, it can only hold limited types of properties. A Mathematica Association '<||>' or List '{}' can hold any Mathematica expression, so the use of SysML Blocks to represent them is far more flexible.

The MagicDraw SysML Plugin and Magic Model Analyst® (Cameo Simulation Toolkit®) tools seem to cope well in most cases with the use of such punctuation characters in Block names, and the characters are easy to prompt on.

Reusable libraries of Activity, OpaqueBehavior, and SysML ConstraintBlock elements may be created to represent Mathematica operations on Associations and Lists, including Map operations, and functional programming (which Mathematica excels at).

Note that either the Association <||> Block or the List {} Block may be extended for dedicated cases, such as:

Webel: SysML4Mathematica: An '@' prefix in the name of a Block indicates a Mathematica data structure (such as an Association or List) that is not represented by an MTools class in the Mathematica code
Relates to
SysML4Mathematica: Example 11 [B]: Total (qDotTot), sensible (qDotSen), and latent cooling (qDotLat) required for cooling air: Using Webel MPsy objects and SysML Activity Diagrams
Related notes
[TIP]{INFORMATIVE} Mathematica: TIPS for living with the user-contributed MTools for Object-Orientation (until a vendor-supported OO solution is eventually provided)
[PATTERN, TIP, TOOL]{INFORMATIVE} Webel + Mathematica + MTools + SysML
[CONVENTION, MODELLING, NAMING]{RECOMMENDED} Webel: SysML4Mathematica: An '@' prefix in the name of a Block indicates a Mathematica data structure (such as an Association or List) that is not represented by an MTools class in the Mathematica code
[CONVENTION, MODELLING, NAMING]{RECOMMENDED} Webel: SysML4Mathematica: An '@' prefix in the name of a ConstraintBlock, Activity, or OpaqueBehavior indicates that it is not represented by a dedicated function in a Mathematica code library (typically for minor maths or logic)
[CONVENTION, LIMITATION, MODELLING, NAMING, TOOL]{RECOMMENDED} Webel: SysML4Mathematica: Convention: A '$E' in a function name indicates that all parameters (arguments and return) are Mathematica '_' expressions. However, when representing such functions as Activities they may end up getting strongly typed in tools!
[LIMITATION, MODELLING, WARNING]{STRONG} Webel: SysML4Mathematica: SysML Parametric Diagrams are not well suited to modelling calculations with Blocks for MTools classes, or for modelling complex logic flow of Mathematica functions. Prefer SysML Activity Diagrams for those modelling cases.
[CONVENTION, MODELLING, NAMING]{RECOMMENDED} Webel: SysML4Mathematica: When modelling the logic flow of Mathematica code with Activity diagrams it is not necessary to model every single Mathematica construct. Placeholder OpaqueBehaviors (used via CallBehaviorActions) and OpaqueActions may be used.
Related notes (backlinks)
Related snippets (extracts)
Visit also
Mathematica zone
Visit also (backlinks)