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 ... 7 8 [9] 10 11 ... 546
For .NET projects you should be referencing Interop.EA.dll, not EA.tlb.

Wasn't that exactly what I posted? ???


I read it like:

This requires an additional argument to the addsubshape method

And indeed we see


That must be it no?



Here are a few example shapescripts that use layouttype=border:
I guess you should be able to deduct the proper syntax this way as well.


Thanks, that clarifies this issue

I'll report back to my client who wants this feature to tell them its just not possible.


If it's defined in a profile on the stereotype of this element, but the element doesn't have said tagged value then you need to update the stereotype.
You can do that manually by right clicking on the stereotype on a toolbox, or do it in a script.

If it's not supposed to be on the stereotype of that element then you can't "force" it to be there.


Someone has been messing with the required MDG technology settings it seems.

Check Configure|Model|Options|MDG Technologies and uncheck everything in the "Required" column.


You have to mark it as formatted text.
Use t_object.Note-Formatted in the query and {Note.Formatted} in the template.



General Board / Re: Importing glossary terms
« on: May 10, 2018, 02:42:26 am »
You can use my Excel Importer to import glossary tools.


General Board / Re: SQL query: how to use "like" in "where" clause?
« on: May 04, 2018, 08:45:29 pm »
In EA you can use #WC# which will be translated to the correct wildcard by EA (* for .eap(x) files, and % for anything else)


General Board / Re: Rule model toolbox
« on: May 04, 2018, 04:49:29 pm »
I think you need to upgrade to the Unified edition.



General Board / Re: MDG Profile derived from sysml in V14
« on: May 04, 2018, 04:03:24 pm »
Wow thats interesting,  I can see SysML 1.1 , 1.2, 1.3 and 1.5, just noticed 1.4 is missing, looks like we've to change to refer to either 1.3 or 1.5.

One of the Sparxians commented about this a while ago.
IIRC there were so little differences between 1.4 and 1.5 that they simply renamed it instead of having them as separate versions.
So version 1.4 is now version 1.5.

I'm not sure how or if you need to you upgrade from 1.4 to 1.5


The resulting tagged value will indeed contain the GUID of the package as value.

You can use Repository.GetpackageByGUID() to get the package object


Yes, a known issue.

There is actually a difference between the SQL server database format and the .eap database format.

I once reported it as a bug, but I got the "it's a feature, not a bug" response  :-\


To Geert's points, if I understand them correctly, they rely on multiple instances of the Repository.  I guess one of my (implicit assumptions) was that there was ONLY one repository.

As part of our possible future solution description, we have a "Transition diagram", where we place the model items (vertices and arcs) in the current state. We then add the future items and connect the current and future things with a "Transitions to" relationship.  With EA recent ability to allow relationships between relationships and relationships and items, we can specify what the transition will be to the requisite level of detail.  It's a really easy way to see if we've "considered everything".

Consequently, we need to maintain all versions in the one repository to allow us to map between them.


Using different repositories is more of a workaround then an actual requirement.
Having one repository where we could maintain all versions would be ideal.
But in that case the tool would have to support that in a transparant way.

For example, if I want to query all use cases I only want to see those of the branch I'm working on, not the ones from other branches (unless specifically instructed)
Or if I want to set the type of an attribute, I only want to be able to select classes from the same branch
Or... etc..

Seems like you should be able to set the context you are working in (MIGHT-BE alternative X) and the tool should then support this in such a way that you only work with elements that are in that branch.
I can imagine that would be a serious challenge to implement that properly in a single repository.


Using version control we can achieve some of these requirements already.
- Investigate a previous (AS-WAS) state (create a branch based on a certain date and restore that to (a copy of) the model)
- Create different alternative MIGHT-BE scenarios (again using different version control branches in different models)

The major difficulty is Merging

A very common scenario would be to have

- An AS-IS (and maybe partly TO-BE) model that is actively maintained. Let's call this the main trunk.
- Multiple branches for possible alternative MIGHT-BE models

Things that are currently very hard (practically impossible) to do:
- Update a MIGHT-BE branch to contain the latest changes in the main trunk (in order to not get too much behind in the branch)
- When a MIGHT-BE scenario has been chosen, merge it back into the main trunk. (or do the update above and call promote this branch to be the main trunk)

I think the LemonTree tool from LieberLieber addresses this problem (and that of three way merges), but I'm not sure if the overhead that comes with a tool like that is acceptable is most scenario's.
I can't imagine people wanting to spend days looking at thousands of differences having to decide to go left (trunk) or right (branch).

If this problem is to be solved there should be a very intelligent merge engine that somehow manages to keep the overhead (and thus the need for human decisions) to a minimum.

I'm not even sure if this is doable, even in theory.


General Board / Re: Excel Import
« on: May 03, 2018, 04:20:17 pm »
You can also generate a document using the document generation templates.

Or you can use a proper database to store your model and have your team members use EA to consult the model.
There is even a free Lite edition that gives read-only access to a model.


Pages: 1 ... 7 8 [9] 10 11 ... 546