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 - Geert Bellekens

Pages: 1 ... 5 6 [7] 8 9 ... 576
General Board / Re: SAVE-Project Button or Menu-Entry
« on: November 13, 2018, 11:38:25 pm »
The project has been saved immediately.

The only things that are not saved immediately are diagram layout changes.
There is a save all option when rightclicking on a diagram tab, but again, that only saves the diagram layout changes.


Automation Interface, Add-Ins and Tools / Re: ApplyUserLockRecursive
« on: November 13, 2018, 11:36:06 pm »
Can't you simply call ApplyUserLock on each element and do that recursively?

Or are notes etc not present in the .Elements collections?


General Board / Re: Check that instance diagrams match class diagrams?
« on: November 13, 2018, 06:00:26 pm »
Yes, that seems to be how EA works.

AFAIK there is nothing build-in to validate this type of thing.
You could of course write your own validation using scripting, an SQL Query, ...

If you want to get it added tot he main product you'll have to send in a feature request, but I doubt it will get a very high priority.
Object diagrams is not really used that much.


General Board / Re: Attribute descrption in v14
« on: November 13, 2018, 03:25:38 pm »
And if you want the old attributes dialog back you can set the option (from 14.1)

Start | Visual Style | Prefer Property Dialogs


General Board / Re: Display Notes in a tooltip
« on: November 13, 2018, 05:43:43 am »
I'm not sure, you can edit the the css files used for the html export, but I don't know if you can add something like a tooltip in those files.


Hi zaxxon,

To extend your stereotype with another more specific stereotype you should use a Generalization and not an Extend relation.
In v14 this should be enough.
In earlier versions you also needed to extend the metaclass from your sub-stereotype as well.

I have found however that I needed to do that in v14 as well, despite the claims from Sparx.


You have to look into the correct t_xref records.

They are related to your Action based on the t_xref.Client = t_object.ea_guid

In your case there will be two t_xref records. One that indicates the type of Action, and the other that specifies the GUID of the trigger element.

So based upon that trigger element you will again need to query t_xref. One record specifies the kind of trigger (Time) and the other specifies the specification (0.5s)
On my test model they look like this:

Code: [Select]
XrefID Name Type Visibility Namespace Requirement Constraint Behavior Partition Description Client Supplier Link
{6FD0BC82-87EA-43dd-83B1-02EF301AB86B} MOFProps element property Public NULL NULL NULL event 0 RefGUID={89807AC7-D452-48eb-85EC-844975D3497B};RefName=0.5s; {F0E65A7D-D49C-47e1-B198-50B0F2D6C091} <none> NULL
{829EF67E-BDB8-444b-95C4-581AD0CEA054} CustomProperties element property Public NULL NULL NULL NULL 0 @PROP=@NAME=kind@ENDNAME;@TYPE=TriggerKind@ENDTYPE;@VALU=Time@ENDVALU;@PRMT=@ENDPRMT;@ENDPROP; {F0E65A7D-D49C-47e1-B198-50B0F2D6C091} <none> NULL

I'm not sure how much of this info can be read using the API objects purely.



You are probably the only (active) user here that uses AUTOSAR

So unless you show us a part of the model and the code I don't think we will be able to help.
If we can see what you mean by "trigger" we could maybe point you in the right direction.

You could also try to contact LieberLieber directly. They will probably be glad to help, and since thy wrote the AUTOSAR add-in they will definitely understand what you are talking about.


Archimate 3 MDG seems to be broken in build 1427.

In my opinion, it's the ArchiMate 3 specification that's broken. It's self-contradictory and ambiguous.

EA has implemented the relationships as defined the the metamodel described by the specification. We are aware that it's different than the appendix, which attempts to provide an interpreted view of that metamodel.


I'm not saying you are wrong, I'm not a fan of the Archimate specification either, but in this particular case that can't be an excuse.
Figure 77 of the ArchiMate metamodel clearly shows the relation between device and system software.


I would be inclined to indeed believe this to be invalid, or at least not logical, but to be sure you should validate it against it's XSD or even check the additional documentation that defines the rules for the xs:annotation tag. There might be a rule that cannot be enforced using an XSD.
I would expect there to be only one documentation tag for each language (and I guess that is what Sparx expects as well).


I think the ValueOf can only be used for tagged values.
I'm not sure what "Dept.EA::Hyperlink1" refers to, but if it is a tagged value I guess it should work.

In case that doesn't work you can always resort to using an SQL fragment.
I often use that for this type of information.

Third alternative is to use a linked document to store that information.
We often include linked documents into our document generation for those parts that change only now and then, such as introduction, version history etc..
This is of course only an option if you don't need that info in a structured way.


General Board / Re: Unapply profile in XMI export
« on: November 10, 2018, 02:52:31 am »
I don't think there's a feature to do that.
You might want to play with the different options in the xmi export, or else write an xslt and apply that after exporting xmi.


General Board / Re: Multi-language model
« on: November 09, 2018, 11:34:46 pm »
We (in Belgium) have this issue also quite regularly, and a real solution would be welcome.

Currently we most often use a kind of hybrid model.
- Names are always in English (if that is not acceptable we sometimes use a tagged value for the name in the other languages)
- Descriptions can be in different languages.

We use a kind of xml tags to separate the different languages.

<en> This is the English description </en>
<nl> Dit is de Nederlandse beschrijving </nl>
<fr> Et ceci est la description Française </fr>

For document generation we parse the notes and extract the required language(s) for the document.

For one client I made an add-in to edit the notes in a user friendly way.
It is still a workaround, but it gets the job done.


Suggestions and Requests / Re: Copy and Link
« on: November 09, 2018, 10:51:08 pm »
Some of my clients use the schema composer + my addin EA Message Composer to create fully traced subset models.

See for more info


Bugs and Issues / problems importing Foreign Keys from ODBC
« on: November 09, 2018, 10:02:07 pm »
I'm using EA v14.1.1427 and SQL Server 2016.

After renaming a foreign key things go wrong when trying to import the changes into EA

Steps to reproduce:
- Import a simple test database with two tables and a foreign key between them
- Change the name of the foreign key in the database
- Show differences in the database builder
- Set Import All
- Import from ODBC

Notice that the fK relation has lost it's properties and it now a simple association with stereotype «FK» with no name or assigned columns.

- Import DB Schema from ODBC again with the option to synchronize everything.
- This brings back the foreign key (with the new name) but still leaves the broken FK association in the model.

The result of this all then looks like this:

Reported to Sparx


Pages: 1 ... 5 6 [7] 8 9 ... 576