Messages

1

Suggestions and Requests / Python as scripting / parametric simulation lang

« on: May 29, 2010, 01:52:10 am »

I'd like to request the integration of Python into at least the SysML parametric simulation.  I've been able to port most of my MATLAB code to Python and found that its easier to code in and runs faster.   Plus its open source and thus free.

It would be a really nice addition to EA as several other vendors in different areas have moved to python as their underling script engine

Thanks!  

2

Automation Interface, Add-Ins and Tools / Re: sysML Binding Connector

« 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.

3

Automation Interface, Add-Ins and Tools / Re: sysML Binding Connector

« 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,

4

Automation Interface, Add-Ins and Tools / sysML Binding Connector

« 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,

5

Automation Interface, Add-Ins and Tools / Re: sysML parameters

« on: July 19, 2007, 06:37:25 am »

 Working through tech support I was able to get some answers to these questions:

1.) & 2. ) this is a bug to be fixed: fault report
number 07071082.

3.) My assumption as to the problem in saving sysML profiles was incorrect.  Only diagrams under <<profile>> packages can be saved as UML 2.0.  I had to first create a Profile package from the UML Profile toolBox and populate it with my stereotypes. Although the save UML Profile dialog now allows selection of UML 2.0 I'm still having a problem here because none of my stereotypes show up in the order stereotypes list and thus are not saved.

PARAMETERS:  sysML ConstraintBlock parameters must be created as embedded elements - InternalPropery

To have them display per  the OMG sysML tutorial have them unchecked (not visible ) in the ConstraintBlock's embedded elements dialog and turn feature visibility - Show element type (port and Part Only) on.

6

Automation Interface, Add-Ins and Tools / sysML parameters

« on: July 09, 2007, 05:43:19 am »

I'm new to EA and sysML but a couple of things don't seem right to me.

1.) I create a constrainBlock and add constraints (engineering formulas) and ports.   I then drag and drop the constraintBlock to create a constraintProperty and I choose the "include Embedded" option.  The new constraintPorperty has the embedded ports, but not the constraints I defined in the constraintBlock.  Shouldn't the constraints be carried over when I create a constraintBlock?

2.) Once I manually add constraints to a constraintProperty I can not get them to display (feature visibility has show constraints checked).

3.) I wanted to build a library of reusable constraintBlocks that I can use across multiple projects.  However, I can not save constraintBlock profiles as UML 2.x (since sysML is a super set) and thus I can not create an MDG technology containing my desired reusable Blocks.  This is a big drawback since I will have to re-enter the same constraints over and over again.  Is there another way to reuse my constraintBlocks?

Thanks,