Sparx Systems Forum

Enterprise Architect => Automation Interface, Add-Ins and Tools => Topic started by: K1955 on October 23, 2007, 01:45:09 pm

Title: sysML Binding Connector
Post by: K1955 on October 23, 2007, 01:45:09 pm
Per the released sysML v1.0 parametric diagrams should have only binding connectors, yet the MDG sysML add-Ins does not have this connector type.

Furthermore, the BlockProperty value Properties need to be bound to ConstraintProperties through the binding connector.  The sysML std provides for a nested notation reference the BlockProperty value Properties in a parameteric diagram.

Looking at the provided sysML example project I found that untyped blocks were used for the BlockProperty value Properties and UML connectors used for binding connectors.  As a result the BlockProperty value Properties are not really bound to the ConstraintProperty parameters.  I'd like to see that with-in sysML blockProperties the value properties are tied through binding connectors to the ConstraintProperties.

Is there someone looking to add the missing sysML constructs to the MDG sysML Add-In?  

Thanks,
Title: Re: sysML Binding Connector
Post by: «Midnight» on October 23, 2007, 02:01:55 pm
Quote
Per the released sysML v1.0 parametric diagrams...

Please cite your reference, so we can examine the same source.
Title: Re: sysML Binding Connector
Post by: K1955 on October 23, 2007, 02:13:07 pm
The ref is:
OMG Systems Modeling Language (OMG SysML™), V1.0
OMG Available Specification
OMG Document Number: formal/2007-09-01
Standard document URL: http://www.omg.org/spec/SysML/1.0/PDF

see page: 44:

8.3.2.1 Binding Connector
Description
A Binding Connector is a connector which specifies that the properties at both ends of the connector have equal values.
If the properties at the ends of a binding connector are typed by a DataType or ValueType, the connector specifies that the
instances of the properties must hold equal values, recursively through any nested properties within the connected
properties. If the properties at the ends of a binding connector are typed by a Block, the connector specifies that the
instances of the properties must refer to the same block instance.
Constraints
[1]The two ends of a binding connector must have either the same type or types that are compatible so that equality of their values can be defined.

and page 79:

10.3.2.2 ConstraintProperty
Description
A constraint property is a property of any block that is typed by a constraint block. It holds a localized usage of the
constraint block. Binding connectors may be used to bind the parameters of this constraint block to other properties of the
block that contains the usage.
Constraints
[1]A property to which the ConstraintProperty stereotype is applied must be owned by a SysML Block.
[2]The ConstraintProperty stereotype must be applied to any property of a SysML Block that is typed by a ConstraintBlock

Thanks,
Title: Re: sysML Binding Connector
Post by: «Midnight» on October 24, 2007, 03:31:01 am
Thanks,

Now the rest of us know what to look for.

Anyone seen any of these yet? Could it be some kind of tagged value - a la the approach taken with the BPMN add-in - or some other magic?
Title: Re: sysML Binding Connector
Post by: K1955 on October 24, 2007, 06:59:47 am
Actually I was expecting to see a Binding Connector tool under the sysML Parametric tool set in EA.

Another ref on page 80 states:

"A parametric diagram is similar to an internal block diagram with the exception
that the only connectors that may be shown are binding connectors connected to constraint parameters on at least one end."

The other end of a binding connector could be another constraint parameter or references to the properties of parts.  The std shows diagram 10.3 on pg 81 using nested property references to the properties of the parts.  These are in the form "ad.HSUV.VehicleDryWeight".

It appears to be missing in the EA sysML Add-In?

So far I have not found a way to implement this easily with the EA sysML Add-In.  Other sysML tools let you drag and drop part property references onto the Parametric diagram.   I was hoping EA had this capability as well?

Another, older reference is the INCOSE-2007-OMG-sysML Tutorial, pg 74 diagram "Cross Connecting Model Elements".  this diagram shows the required bindings between all of the sysML model elements.