Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Messages - Ted Speers

Pages: 1 [2]
General Board / Re: Support for nested ports ... SysML1.3
« on: May 28, 2014, 11:03:01 pm »
Ok, so I am still demonstrating general ignorance on how the tool works.  This time, I tried to create a port with a flow direction indicated.
1. create a block
2. add a flow property to block [newchildelement->flowproperty]
3. set the flowproperty to out
4. added another block
5. added a port to the block
6. selected the port and [advanced->set property type]
7. selected the block created in step 1.
8. nothing happens

General Board / Re: Support for nested ports ... SysML1.3
« on: May 27, 2014, 03:34:12 pm »

very clear explanation ... this is not easy to grasp (for me at least)

General Board / Re: Support for nested ports ... SysML1.3
« on: May 27, 2014, 02:09:55 pm »
thanks ... unfortunately this is completely non-intuitive to me ... i was able to get a port nested into another following your instructions this way:
1. add a class to diagram
2. add a port (3) to the class - set the type of the port to the class it is attached to
3. expose inherited/owned elements and select the port i added (1) ... the port is now nested to itself ... i want a different port nested to port 1\

i've tried many permutations and get no where ... lacking basic understanding of what is going on obviously

General Board / Support for nested ports ... SysML1.3
« on: May 27, 2014, 12:08:30 am »
is there anyway to create nested ports (a SysML1.3 construct).  if not, what is the expectation that a particular modelling feature is supported or not by EA

General Board / EADDS !BAD
« on: May 13, 2014, 10:22:28 am »
I repeatedly get a pop-up titled EADDS with the content ! BAD.

It takes repeated dismissing to go away but comes back pretty much any time I try and do anything.  It has to do with my install of 1106.  I never experienced this before.

General Board / SysML Flexibility including multiplicity
« on: November 26, 2013, 02:32:21 am »
I am trying to understand mutliplicity (among other things)

Things I would like to do include:
Declare cardinality of block (say 0..*) (either on the block itself or on the composing connector) and then in the IBD add three individual instances of the resultant part and connect them up differently ... eg part[0] to part 'a' and part [1] to part 'b'.  Instead, if I declare cardinality on the block, I get a part labled 'part[0..*] and no obvious way to single out part[1] from part[2].  I can't put two instances of a part in a diagram as I was expecting.

Include a part in the ibd that inherits from one of the composing parts ... say part a, b and c are specializations of d.  I want to say e is composed of 3 d's and then in the ibd, use 1 each of a, b and c.

Among the many things I don't understand (I've been at EA for 30 days, SysML for a weekend):

I can't tell when some things are information and others have a real impact on the model ... i can make the cardinality of a block 2 and then have a connector with multiplicity 3 attached to it ... seems illegal

If a declare a port has multplicity of [0..2], how do a connect port[0] to block 'a', port[1] to block 'b', etc?  Now say the block has a multiplity of [0..1] ... I want to connect block[1]port[0] to block 'a' and bloclk[0]port[0] to block 'b'.

Does the import connector do anything?  If I import pkg 'a' into pkg b' and 'a' contains 'c' ... how do i refer to b.c ... i would also expect to be able to display the imported contents inside the package

Automation Interface, Add-Ins and Tools / Multi-instantiation
« on: November 11, 2014, 02:08:00 am »
Any tools or tips on dealing with the 'multi-instantiation' problem.

The problem is outlined in this white paper and apparently handled by the tool from Esterel.  In their example, they have a car with 4 wheels, each with a tire.  There is no way to have different pressures on the tires, among other things.  

"Challenges with SysML
One main issue to deal with is the “multi-instantiation” of architecture components;"

Pages: 1 [2]