-
Key: SYSML16-1
-
Legacy Issue Number: 10047
-
Status: closed
-
Source: Change Vision ( Michael Chonoles)
-
Summary:
The current document eliminates Protocol State Machines on the grounds of simplification. See Section 13
However, this leaves a hole in the capabilities of SysML. Currently, SysML supports UML interfaces (provided and required), which can’t have state machines to define them.
It is an important part of designing systems interfaces (SE terminology) to define the details of the (UML/SysML) Interfaces. These details include the allowed ordering of messages. As we are not allowed to use behavior state machines and the standard solution, that of, protocol state machines are not included, we can’t properly do interface engineering within SysML
If some other solution/work-around is proposed (which I don’t recommend) the explanation of how to accomplish this should be in the spec.
-
Reported: SysML 1.4 — Mon, 31 Jul 2006 04:00 GMT
-
Disposition: Deferred — SysML 1.6
-
Disposition Summary:
Defer
Postponed to the next RTF
-
Updated: Mon, 1 Apr 2019 18:17 GMT