Legacy Issue Number: 18908
Source: Airbus Group ( Yves Bernard)
description of Signal flow property has the sentence: “ [ ] imply sending and/or receiving of a signal usage”. It seems that the word “usage” is not convenient here and is confusing. It should be removed.
Reported: SysML 1.3 — Thu, 12 Sep 2013 04:00 GMT
Disposition: Resolved — SysML 1.4
Subclause 126.96.36.199, Description subsection, third paragraph, relates flow properties
typed by signals to sending signals as follows:
Flow properties of type Signal imply sending and/or receiving of a signal
usage. [snip] An “out” FlowProperty of type Signal means that the owning
Block may send the signal via connectors and an “in” FlowProperty means
that the owning block is able to receive the Signal.
The text above does not require implementations to do anything special for flow
properties typed by signals beyond what is normally done for flow properties,
because it says “may”. Removing the text would not prevent implementations from
adding semantics as the text describes, because the specification would not disallow
it. However, the text implies alternative conforming implementations that should be
called out, but with more specific language referring to signal events. The revised text
should not require or prevent signals from being sent due to flow properties, because
this would invalid existing implementations unnecessarily.
Updated: Fri, 6 Mar 2015 20:58 GMT