-
Key: SYSML2_-409
-
Status: open
-
Source: UNICOM Systems ( Mark Gregory)
-
Summary:
Each section describing a particular thing e.g. Usage needs a notation subsection which should show all new possible notation relevant to that section where not described elsewhere and how it ties in with abstract syntax in terms of which properties, item types and values are involved.
Graphical lines which connect items should be described in terms what attributes of what item should refer to which other items.
Such information should not be buried in a sea of descriptive text, it should be clear and concise.
An example: 7.10 deals with Items and only lists a couple of symbols and one compartment (displayable property) called 'items'.
There is no specification of what this compartment is presenting in terms of a) the property or properties to be checked or b) what is referenced.
Point a can sometimes be answered where they have property name = ... but not in this case.
Point b can sometimes be answered by following the chain of notation specifications because they sometimes have notationname : type of element = ... - this does point to Usage types.
I guessed that the nestedItem attribute should be the source of this information.The Graphical syntax section identifies another symbol, an item reference, which I guess is the presentation to be used when the Usage is a ReferenceUsage. I say guess because again there is no specification.
Trying to understand 18: Connections with respect to abstract syntax when each pictured symbol's abstract type is not named is very difficult.
-
Reported: SysML 2.0b2 — Fri, 15 Nov 2024 16:21 GMT
-
Updated: Tue, 10 Dec 2024 08:12 GMT
SYSML2_ — Notation should be more formally tied with Abstract Syntax
- Key: SYSML2_-409
- OMG Task Force: Systems Modeling Language (SysML) 2.0 FTF 2