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 - marke

Pages: 1 [2] 3
General Board / Linked documents in merge import
« on: March 23, 2017, 07:14:53 pm »

I'm using xmi export/import to work remotely. When I import with merge back to the master I am finding that changes inside element linked documents are not being brought in. Is that a known limitation or is it possible I am doing something wrong?

Thank you , Mark

Suggestions and Requests / Re: EA 11 wishlist
« on: May 16, 2013, 06:59:36 pm »
How about enabling some kind of user voting on suggestions?

There is another tool I use whose vendor does this - see

as an example. Voters have 10 votes which they can apply 1-3 of on any suggestion. This forces people to prioritize what is important to them (rather than everyone voting for everything). You can move your votes and you get them back when a suggestion is implemented. It must give the vendor a very good indication of what should be in future releases.

Can this forum support something like that? Otherwise the example above uses uservoice (I guess there are others).


I guess the standard answer is to use DOORS MDG (which I have) or RaQuest. However, both of these tools seem to constrain you to creating the basic requirement model element types and not the SysML types, i.e. Extended, Functional etc.

What I would really like to see is the ability to control the SysML requirement id within EA on a per package basis, e.g. if I have package of System Reqts then these get numbered SRD001, SRD002 etc and then another package of Software Requirements these get numbered SRS001, SRS002 etc. Needless to say I would like to have EA enforce that the ids are both unique and static. The numbering sequence could just be based on order of creation (as DOORS does). Given the choice I would rather not have the requirements in another tool (DOORS or RaQuest) as well as EA.


Suggestions and Requests / SysML 1.3
« on: January 31, 2012, 02:12:49 am »
Is there a plan to support SysML 1.3?

Thank you,


General Board / Parameterized classes (templates)
« on: December 06, 2013, 07:44:13 pm »
Does anyone know how to hide the dashed outline box, containing the parameters, on a diagram? Or if it is possible to do so?

Thank you, Mark

General Board / Re: Activity element return field
« on: September 27, 2013, 11:08:26 pm »
Thankyou Geert.

So EA should add an activity parameter, of directionkind return, to the activity. It doesn't seem to do so.


General Board / Activity element return field
« on: September 26, 2013, 11:41:41 pm »
I'm using activities to describe the behaviour of some operations.

I notice in the Activity properties Behaviour there is a field to specify the Activity return type. The return type then appears as the type of the Activity.

I then open the diagram for a structured activity. I Show Diagram Frame which will include any activity parameters that are specified but there is nothing diagramatic to represent the return value. I guess I was expecting something like an activity parameter box. My activities are algorithmic and I can't see what I should connect a return value to.

I've done some searching in the SysML and UML specs and some textbooks and can find nothing about Activity return types/values. Is the Activity return some non-standard, EA addition? Should I stick with an Activity Parameter for the return?

Thanks, Mark

General Board / Re: Relationship between functions and Matrix
« on: July 17, 2013, 09:05:29 pm »
I've submitted a feature request (to Sparx, not God).

General Board / Re: Relationship between functions and Matrix
« on: July 17, 2013, 05:25:32 pm »
The Help makes it clear that the Link to Element Feature is a visual aid only and the actual links are between the Elements, not the Features.

Is there any good reason why the traceability could not be implemented by Sparx at the Feature level?

General Board / Re: SysML connector types
« on: May 07, 2013, 08:47:02 pm »
Hi q,

I'm not talking about the type of connector (e.g. abstraction, aggregations etc) but the type associated with the connector. For example, the type of the connector between a router and a PC might be an Ethernet Cable.

See page 24 in The connector between the PlugIF and the SocketIF has been typed by an association block.


General Board / Re: SysML connector types
« on: May 07, 2013, 08:07:55 pm »
Hi Gary,

SysML 1.3: Table 8.2 & section Also Fig 7.47 (p164) in "A Practical Guide to SysML (2nd Ed) by Friedenthal et al".

I was expecting that when I bring up a connector's properties (in this instance in an ibd) that there would be somewhere to specify the type (as you can in a port's properties).


General Board / SysML connector types
« on: May 01, 2013, 01:48:54 am »
The OMG standard shows that connectors between ports or parts on an ibd can be typed. EA doesn't seem to allow typing of connectors. Am I missing a trick or is this an omission?

Thank you, Mark

General Board / Re: SysML 1.3 Nested Ports
« on: April 23, 2013, 08:34:36 pm »
Just found the answer to my own question on the owning port size:

right-click on port, Advanced/Port Size Customizable.


General Board / Re: SysML 1.3 Nested Ports
« on: April 23, 2013, 08:28:13 pm »
Coincidently, I just created what looks like a nested port.

I did so in the project browser: added New Element full port to a block; then selected the port and again added New Element full port to that port. Then select instance of block in ibd and added "Structural Elements ..." to show the owning port. Then repeated add Structural Elements on owning port to add nested ports.

The question I was about to ask is: is there a limitation on how much you can stretch the owning port on the diagram? I have been able to stretch it enough to hold a few nested ports but seem to have hit a limit.

I'd add an image but I'm guessing the forum doesn't let you do that.


General Board / Re: RTF Property type
« on: October 28, 2011, 08:04:27 pm »
I've got the same problem in 9.1.910 and it applies in the html output too. The port documentation make no mention of the element type. This is a fundamental omission if you are trying to document interfaces.

Pages: 1 [2] 3