SysML 2.0b3 FTF Avatar
  1. OMG Issue

SYSML2_ — Short Usage Name is not Specified (e.g. Perform action and Perform)

  • Key: SYSML2_-446
  • Status: open  
  • Source: Dassault Systemes ( Mr. Tomas Juknevicius)
  • Summary:

    In the graphical BNF the short usage name notations are not specified as well duplicated usage keywords are possible. For these usages, the issues occurs:

    • perform action -> perform;
      • the usage with 'perform' keyword is displayed in Table 9. Parts.
    • exhibit state -> exhibit;
      • exhibit-state-name-compartment = '«exhibit-state»' state-name-compartment - as well based on the specification the keywords could be «exhibit-state» «state», as the state-name-compartment is used.
    • assert constraint -> constraint
      • assert-constraint-name-compartment = '«assert constraint»' constraint-name-compartment - as well based on the specification the keywords could be «assert constraint» «constraint», as the constraint-name-compartment is used.
      • the same issue could be for require constraint and assume constraint but they are not specified as a node shape in the 8.2.3.19 Constraints Graphical Notation section.
    • satisfy requirement -> satisfy
      • the usage with satisfy keyword is displayed in Table 19. Requirements
      • satisfy-requirement-name-compartment = '«satisfy requirement»' requirement-name-compartment - as well based on the specification the keywords could be «satisfy requirement» «requirement», as the requirement-name-compartment is used.
    • the same issue could be for frame concern but it is not specified as a node shape in the 8.2.3.20 Requirements Graphical Notation section.
    • include use case -> include
      • include-use-case-name-compartment = '«include use case»' requirement-name-compartment - as well based on the specification the keywords could be «include use case» «requirement», as the requirement-name-compartment is used.
  • Reported: SysML 2.0b2 — Wed, 18 Dec 2024 09:30 GMT
  • Updated: Sat, 11 Jan 2025 19:47 GMT