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

Pages: [1] 2 3 ... 38
Yes Geert is correct there was a bug in Session.Input

His alternative method if input is great and one I have used myself.

I believe the bug has been fixed in the latest release of EA 14.1 Feb 6th 2019


Bugs and Issues / SysML Part Association
« on: February 12, 2019, 01:33:40 am »
Hi all

When creating Block Definition models, in SysML using EA version 13.5, and using a Part Association between Blocks, EA synchronised the source role name and source multiplicity between the Part Association and the correspond child Part Property. Which is as I expected.

However, when performing the same task in EA version 14.1 (including the latest build), all Part Properties and created as anonymous and no synchronisation between source role, source multiplicity and Part Property occurs. Frustrating and not what I expected.

Has anyone else experienced this?

I suspect its a bug, and if so will raise one through the usual channels.

Oddly, I have once or twice out of many attempts managed to get a synchronised source role name and Part Property name, but I cannot repeat this reliably, if at all.



Hi All

Many thanks for all the replies, the addition of the version number to replace the blank version number in the diagram and toolbox profiles solved the issue.

All the best


Hi All

Has anyone else experienced the following when generating an MDG in EA 14.1?

1) Create an MDG consisting of the usual profile, custom diagram(s) and toolbox(es)
2) Use the SPECIALIZE Publish -> Publish Diagram as UML Profile for the custom diagram(s), and toolbox(es) to create the XML files
3) Use the SPECIALIZE Publish -> Publish Package as UML Profile for the profile to create the XML files
4) Generate the MDG and select to include Profile, Diagrams, Toolboxes (etc) in the MTS

Only the Package Profile XML shows up the profile selections for profiles / diagrams / toolboxes! That is the XML files generated for the diagram(s) and toolbox(es) are not listed within the MDG Builder dialogs.

If I revert to EA 13.5 and re-generate all the XML files, the MDG builds fine in EA 14.1

Any thoughts?


Many thanks KP

Much appreciated


Automation Interface, Add-Ins and Tools / Metadata Stereotyped Relationship
« on: November 07, 2018, 03:10:19 am »
Hi All

I am developing  fairly complex MDG in EA 14.1 and am attempting to use the "new" quicklinker Stereotyped Relationship between two stereotyped elements defined in my profile.

It works, sort of.

When I create a diagram using my MDG, and use the Quicklink, I see the relationship defined in the Stereotyped relationship, BUT I also see the following




Information Flow




How can these be removed? Presumably somewhere within the MDG, these "extras" are not shown in ArchiMate 3.0 for example.

I don't really won't to revert to the legacy spreadsheet method!

Any help much appreciated


Follow up to last post

Setting the SOURCE role has no affect on the Part Property, but setting the TARGET role (and multiplicity) DOES affect the name. Maybe this is the "proper" way to use roles.


Yes I got caught out by that!

I suppose the only way is to turn off the diagram frame in EA 14, then open in EA 13?

On a different note, have you noticed in EA 14, that a part association will create the Part Property correctly, but the role name on the part associations does not affect the name of the Part Property which remains anonymous.


I too would like tagged values directly on a diagram.

In the meantime, there is a rather ugly workaround.

  • Drag a diagram as a Diagram Frame onto another diagram
  • Move this Diagram Frame to the same package as the Diagram
  • Make the diagram a child element of the Diagram Frame
Diagram Frames can have Tagged Values just like another elements, and of course you can use relationships to / from (for example realisation of Requirements)

Just a thought



Are we talking about defining the icon in an MDG or have you discovered some cool api function that will assign the icon dynamically within a script / extension?


General Board / Re: how to split a sequence diagram
« on: October 06, 2018, 12:55:49 am »
I split the interaction into several manageable interaction (sequence) diagrams.

Then to refer to one my "lower level" diagrams.

Drag the diagram to be referred to onto the "higher level" diagram and select "Interaction Occurrence"
This creates a rather ugly floating box linked to the "lower level" diagram
Right click this Interaction Occurrence" and select "Advanced > Show as Timeline" from the menu
You now have a lifeline with the heading ref the "lower level" diagram name, which you can send and receive messages to / from (as per usual lifeline). Double-clicking this drills down the levels.

You can refer to the same "lower level" diagram more than once on the "higher level" diagram if required


General Board / Re: Disable the abilty to Manage Add-Ins
« on: September 18, 2018, 09:03:04 pm »
You are correct Geert

Basically, the client has diabled audit due to performance issues, so the Add-in "mimics" the audit by monitoring for events "behind the scenes" and writes info to its own log files.

Since this addin must run for all users, any user should not be able to disable it, thereby by-passing the add-ins audit factility.

It is possible to restrict privilige to manage audit, so I was looking for a similar function.

One possiblity is to remove the Manage Add-ins from the Ribbon, but this would mean a change to each EA client.

Will send a feature request to add such a privilege.


General Board / Disable the abilty to Manage Add-Ins
« on: September 18, 2018, 08:06:24 pm »
I have received a request from a client to restrict who can disable / enable Add-ins / Extensions.

Having checked the List of Available Permissions, there does not appear to be any such permission, and a test of:
  • creating a new user with no permissions at all
  • logging in as that user
  • selected to Manage Add-ins, was able to enable / disable any listed Add-in

As workflow scripts only apply to selected element properties, that route won't work either.

Is there a way to prevent users from Managing Add-Ins?


General Board / Re: use case non human actor
« on: August 28, 2018, 06:48:39 pm »
For non-human actors in UML Use Case diagrams I use Rectangle Notation available via the context menu Advanced option for an Actor


There is an ERD MDG in EA which can be a bit confusing since this is not the "Crows Feet" notation closely related to UML class diagrams

Rather this is Chen ERD, whereby Entities Attributes and even Relationships are represented by elements. In Chen ERD you can model attributes as candidate keys, multi-valued attributes and structural attributes. Attributes are related to an Entity via a connector.

Relationships, represented as a diamond are used together with connectors to relate Entities in binary or n-ary relationships. You even define so called "weak entities" where a candidate key can not be identified.

As elements are used for Entities, Attributes and Relationships it is very easy via the relationship matrix to maintain traceability to requirements and other model elements.

EA has MDA from Chen ERD to Physical Model and vice versa

So what's the downside, well with all these elements a conceptual data model modelled in Chen ERD does take a vast amount of space, but I suppose this model could be spread over a number of "views"

Chen ERD does not appear to be well known, or indeed used very much.

This link will provide more details

Ignore the fact that this link is for a drawing tool, but it does provide a good overview of Chen ERD


Pages: [1] 2 3 ... 38