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] 2 3 ... 536
Uml Process / Re: validation of OCL constraints
« on: April 23, 2018, 02:33:21 pm »
Please don't post questions twice.


Bugs and Issues / Re: Time-aware MDG Technology models
« on: April 20, 2018, 06:53:14 pm »
OTOH, if you want to reuse a toolbox page between toolbox profiles you've got to export from the diagram. Unless they've done something with that in recent versions?


I don't do that anyway, so that is not really an issue for me.
I guess I would even prefer to duplicate the toolbox page over using diagrams.


Bugs and Issues / Re: Time-aware MDG Technology models
« on: April 20, 2018, 05:05:03 pm »
I use the generate from project browser as well, first and foremost because I don't want to depend on what is visible on a diagram for my exports.
I don't consider diagrams to be a "real" part of the model and don't like to depend on them for this type of stuff.


Bugs and Issues / Re: V14RC: [Alt+Z] functionality Gone!
« on: April 20, 2018, 02:18:35 pm »
And I'm on Windows 10 and indeed the ribbon reacts by opening up the SpecialiZe tab when I try it.



I had a look at the time aware modelling feature and decided that it is not useful for me or my clients.
It really quickly becomes a mix of elements from different versions, all linked to each other.
Definitely not how I would design a feature like that.


General Board / Re: Prevent display of the window by fly on boudary
« on: April 19, 2018, 09:10:06 pm »
  how to prevent the display of the window on boundary by fly whic is particularly annoying, please ?
I'm sorry, I really don't understand what you are talking about.


Good to know.

One of my customers that is using document generation pretty seriously is planning to upgrade to v14 somewhere this year.
Will need to test all my templates to make sure nothing breaks.


Bugs and Issues / Re: V14RC: [Alt+Z] functionality Gone!
« on: April 19, 2018, 06:00:30 pm »

I use that all the time as well.



As an alternative, you could compare the xml files "functionally".

I had this same requirement to compare XSD files in a "functional" way -> ignoring order of elements (where not important), whitespace, order of attributes, etc...
(we are migrating a Magicdraw model + XSD generation to EA + XSD generation and we need to know if the XSD's (about 500 of them) are functionally still 100% the same while allowing non important differences)
What I end up doing was building my own comparer based on a code sample I found on a Microsoft website.

I uploaded it to github. I think you only need to change the (hardcoded) .xsd extension to .xml to make it compare xml file.


Where would that oder be important? I guess in the toolbox? If so (IIRC) EA does not offer an ordering from the MDG export (since IIRC I tried that once and could not figure it out).


In the toolbox you define the order yourself. (attribute order)
I don't see where the order in the MDG file would be relevant either.

But maybe it uses the project browser order when generating the profile xml file from a package?


To be clear,

You have

- A regular UML profile with "real" stereotypes
- Multiple toolbox definitions that use some of these stereotypes.

That is perfectly fine and won't be a problem. You can even use standard UML elements or stereotypes from other MDG's in your toolbox.


You will somehow have to navigate to the actual activity to see the description.

The EA Navigator could help with that.



Can you also explain how/why this is a problem for you?



It's not because you put components on a diagram (even a composite structure diagram) that they have some kind of relation to the owner element of the diagram.

The first thing I would think is that your components are actually owned by the owner object (they reside under the object in the project browser). In that case there is already a relation (ownership) between the objects, but unfortunately that relations is not easily detected and does not follow the same rules as other types of relationships.

If you wanted to you could, with the help of a little script, automatically add a relation between the owned elements and the owner, but you would have to run that script on a regular basis in order to keep the links in synch with the reality.


Pages: [1] 2 3 ... 536