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 - Svend Erik Nygaard

Pages: [1] 2 3 ... 8
Suggestions and Requests / name's direction on dgm-link vs on connector
« on: August 21, 2018, 09:44:19 pm »
First: This is not about the connector's direction, but about the connector name's direction.

I have noticed, that the name's direction is stored on the diagram link - not on the connector.

This causes the following mal-function in EA:
1) the same connector can have different name directions on different diagrams - very unfortunate
2) when creating the same connector on (another) diagram, the name direction is not transferred (this is more an inconveniency than a malfunction - but it also makes modeling more error-prone, because of point 1 above)

I think the UML spec does noes not address this issue very clearly or explicitly - but I think the name direction should be on the connector itself.

This malfunction will probably make us use the connector's direction for the reading direction instead of the name direction.
Yes, I know, unlike the name direction, the connector direction has a semantic on it (navigability) - but since we don't use our model for forward engineering / code implementation, we may make that decision - unless there are plans to change the above described behavior.

Are there any such plans to change this behavior of the name direction in EA?

How do I administer enabling/disabling (and setting active) MDG Technologies for all users?
EA comes with a large bundle of MDG Technologies. I want to centrally disable a lot of these and set one of them as the active one. (preferably not for a specific model but for all clients)

That was a great shot, Geert - right in the bull's-eye  :)

One of the MDGs coming with EA14 must have a "impl" stereotype.

Of course that leaves me with a consideration of making my automation routines more robust (more precise)

I do not see anywhere in the t_connector table that tells me the 'absolute'/complete name of the stereotype - I'll look into that after the weekend (maybe in t_xref). It would be nice, had it been stored in two separate columns with the stereotype column holding only the short incomplete name - and then let it be purely e rendering choice.  Now I have two different values in the same column (respectively for rows before and after EA14)

Tanks very much for your help again

In my MDG, I have a stereotype “impl” extending “Realization”.
Before EA14, it behaved just like all other stereotypes, setting a connector’s stereotype property to “impl”.
But after upgrading to EA14, it sets a connector’s stereotype to “CPH_MetaModel::impl” – which causes a multitude of problems in our automation routines.
It seems, all other stereotypes in my MDG do NOT have this problem.
Have any of you experienced the same issue?

Below, I have included the MDG XML for the impl plus a couple of other connector steretypes. As mentioned only the impl causes problems.

<Stereotype name="impl" metatype="impl" notes="" cx="0" cy="0" bgcolor="-1" fontcolor="-1" bordercolor="-1" borderwidth="-1" hideicon="0">
      <Apply type="Realisation">
         <Property name="direction" value="Source -&gt; Destination"/>
      <Tag name="Master" type="boolean" description="" unit="" values="true,false" default=""/>

<Stereotype name="at" metatype="at" notes="" cx="0" cy="0" bgcolor="-1" fontcolor="-1" bordercolor="-1" borderwidth="-1" hideicon="0">
      <Apply type="Dependency">
         <Property name="direction" value="Source -&gt; Destination"/>

<Stereotype name="reflect" metatype="reflect" notes="" cx="0" cy="0" bgcolor="-1" fontcolor="-1" bordercolor="-1" borderwidth="-1" hideicon="0">
      <Apply type="Generalization">
         <Property name="direction" value="Source -&gt; Destination"/>
         <Property name="isSubstitutable" value=""/>
         <Property name="_lineStyle" value="direct"/>

Thanks, for quick answer, Geert.

After upgrading to EA 14 (1422), I cannot save package as uml profile
In EA 13.5 this menu item was in the package's context menu. Now in EA 14 it is under the ribbon Specialize/publish - but here the menu item "Save package as uml profile" is gray out.
(of course, I have selected a uml profile package when trying)
What am I doing wrong?

Why is it so important that you have a stereotype on your diagrams?

  • Searching
  • Reporting
  • Applying logic/rules/quality checks
  • ...

I'm sorry I don't understand what you mean with "elements created from the MDG's diagram type"

Yeah, that was a bit of fast typing, sorry.

I mean:

I create a customized diagram type "CityMap" in my MDG.
Then, when the user creates a new CityMap diagram, I want EA to set the diagram's stereotype to "CityMap"
Is there any way, I can specify in my MDG, that the diagram should automatically be given the stereotype "CityMap" - for instance, can I, in my MDG, specify a default value for the Stereotype property?

IIRC we found we had to place them in the General stereotypes list with a base class of Diagram to get them to show up.

But that will not associate the MDG's diagram type with the general stereotype - correct?

Is there any way to add a stereotype (possibly as a default value) from within the MDG, to elements created from the MDG's diagram type?

I created a custom diagram type in an MDG.

When I use the MDG, I can select my custom diagram type when I create a new diagram
  • The new diagram does not get a customized type - it is still just "Component"
  • The new diagram does not get a customized stereotype - it is still blank in the stereoype
  • If I try to change the stereotype in the properties field, my new stereotype does not show up
  • The new diagram does not get a customized stereotype (in diagram peoperties window) - it is still blank in the stereoype
If I go to Design/Diagram/Manage/Change type... - then I can actually choose my new diagram type, but I still don't see any change in the diagram's type og stereotype.
The diagram pane's title bar does show the new customized stereotype though (<Steretype> diagram: <name>
EA also presents the associated toolboxes correctly
Does EA not set diagram type and stereotype in the usual fields (Diagram_Type and Stereotype) for a customized diagram?
I can see that it does include the name of my customized stereotype (CityMap) in the field StyleEx:

You can also implement an attribute modified time as a tagged value. It won't be foolproof, but it is doable.

Thanks, I also thought about adding an extra column with timestamp default='NOW' to the table(s) in the db schema.

But maybe the tag-solution would be better. Do you know of anyway to setup a default (='now') for a tag - or would I have to use an addin to set it to default (apart from a db-trigger)?

The only thing you can do is to turn on auditing.

Can I find it in som audit table(s) in the DB (and where :) )?

Automation Interface, Add-Ins and Tools / t_attribute - no ModifiedDate
« on: August 11, 2017, 05:01:05 pm »
The t_attribute table has no ModifiedDate.

Is there no way to see when an attribute was last updated?

I tried to see if I could find something in the audit log - but I only found the t_snapshot table and did not find any thing helping me there - and even if the audit log could help me, that would only work when the audit log is active.

I also checked to see if the object to which the attribute belongs gets its ModifiedDate updated when the attribute changes, but this seems not to be the case

I am (was) sure that there it's possible to export/import Perspective Sets, Workspaces, etc - but I cannot find how to do it. I don't see them in the Export Eeference Data. And I don't see any export/import function in the Perspectives Window either.
How do I export/import Perspective Sets, Workspaces, ...?
I have them on my old workstation (windows 7 + EA 12) - and distributed them to users in an MDG file.
Now I have moved to a new workstation (windows 10 and EA 13) - and need the perspectives, workspaces, ... to include in my MDG.

Is it not possible to set a tag up as a combo box, where the type is an enumeration, but where the user will also be able to enter a free-text value?
(My context is a UML profile in an MDG)

Pages: [1] 2 3 ... 8