-
Key: SYSML17-384
-
Status: open
-
Source: Elparazim ( Edward Roberts)
-
Summary:
A BoundReferrence must be more general in multiplicity than the property it binds to... but there is nothing in the constraints that specify this... the lower and upper limit the number in that specific Type
Also, the best practice for BoundReference is to make its multiplicity * so there is not the double maintenance issue if any multiplicity changes along the path it is bound to... this should be specified
Also, specify that lower, upper of BoundReference restricts the multiplicity of the property it is bound to... and there should be example showing how the multiplicity of BoundReference can be different than the values of lower,upper and why
also, the statement "Properties to which BoundReference is applied shall be the role of a connector end of at least one binding connector, or generalized by such a property through redefinition" especially "or generalized by such a property through redefinition" is not clear as to what is being generalized
also, an example of when nonuniqueness would come into play would be good in the standard
-
Reported: SysML 1.6 — Sun, 25 Oct 2020 13:26 GMT
-
Updated: Tue, 27 Oct 2020 19:36 GMT