-
Key: SYSMLR-216
-
Status: closed
-
Source: Change Vision ( Michael Chonoles)
-
Summary:
In Table 8.1 2nd row, Block, the compartment header, "parts" is misplaced. It is above the compartment separator but belongs below it.
In the constraints compartment, there is an extraneous space after the { (left brace). The remainder of the diagram uses no space inside the braces.
In the operations compartment, operation2 has a parameter q1 of Type 1 (with an embedded space). It is also used with a space in op3. However, Type1 without a space is used in operation1. Generally, no space should appear in a type name. These problems with Type 1 also appear in row 4 showing an example of a valueType. Also in row 4 (showing the valuetype) prop6 and prop7 have extraneous spaces in their types.
Also, in Row 4 an extraneous space appears in the subsets clause of property2. It says {subsets property 0). It should say
{subsets property0}.
In both Row 2 and Row 4, operation2 has a return type of Types. Either this is some sort of category operation (which doesn't generally seem possible in UML) or one of the worst possible names for a Type
-
Reported: SysML 1.4 — Sat, 19 Dec 2015 19:34 GMT
-
Disposition: Resolved — SysML 1.5
-
Disposition Summary:
Proposal: Table 8.1 Block compartment header misplaced and other formatting problems and inconsistencies
Changed as proposed by the submitter and changed Block0 to ValueType0 in the redefinition clause for the ValueType since a ValueType can not inherit from a Block.
-
Updated: Thu, 6 Apr 2017 13:49 GMT
SYSMLR — Table 8.1 Block compartment header misplaced and other formatting problems and inconsistencies
- Key: SYSMLR-216
- OMG Task Force: SysML 1.5 RTF