Systems-Modeling / SysML-v2-Pilot-Implementation

Proof-of-concept pilot implementation of the SysML v2 textual notation and visualization
GNU Lesser General Public License v3.0
114 stars 23 forks source link

ST6RI-705 Resolutions from SysML v2 FTF Ballot #3 #505

Closed seidewitz closed 8 months ago

seidewitz commented 8 months ago

This PR implements the following issues from SysML v2 FTF Ballot #3:

SYSML2-84 Connection declaration does not allow a feature value

The resolution of this issue allows connection usages to have feature values. Previously the second line of the following did not parse:

abstract connectionc1; abstract connectionc2 = c1; // Error: No viable alternative at input '='

Now this will parse. Indeed, a feature value may be included in any connection declaration that uses the explicit connection notation. For example,

connectionc3 = c1connecta to b;

A similar update has been made for interface usage declarations. (Not that message and flow connection usage declarations already allowed feature values.)

SYSML2-155 Limitation on specifying view rendering

The resolution to this issue extends the notation for a view rendering usage to allow the rendering to be defined locally within the containing view, rather than just allowing rendering by reference. The new notation is exactly consistent with almost all the other current textual notations that also allow a special syntax for reference usage (e.g., exhibit state usages, perform action usages, assumed and required constraints of a requirement definition or usage, etc.).

render renderingname : Def [m] ... ;

The previous notation renderr; then effectively becomes a shorthand for render rendering referencesr;.