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.

Topics - Svend Erik Nygaard

Pages: [1] 2 3 4
How do I SQL-query items within a large hierarchy of nodes (or namespace)?
Of course, I can use joins (recursive in programming or through unions in a single SQL statement) - BUT that is not performance-friendly.
I thought (hoped) that EA would recursively mark all items down through the tree structure in a given namespace - but I haven't found any table column (neither in t_xref) for that.

I still hope that there is a perforamnce-friendly way search with SQL within a large hierarchy of nodes.

Any suggestions?

Now, in EA 15, it has become easier to link to attributes (as well as other element features).
However, we really need important support for these feature-level connectors in more ways, e.g.
  • Show relationships for a given attribute
  • Show traceability for a given attribute
  • Insert related elements for a given attribute
  • Show traceability for a given attribute
  • Option on diagrams to hide all feature-level connectors - without this option, diagrams are really easily becoming cluttered with a mess of connectors - and it is not realistic to manually hide these  --  (possible criteria nuance: one or both ends at feature-level)

I have often considered creating triggers on Sparx' tables.
Has anyone tried that?
Is there any official policy on that?
(Of course, I may have to recreate them when upgrading EA versions, but that is alright)

Any good tips on how to make references between attributes (across) elements?

One option, of course, would be to create connectors between them ('link to feature') - but that will totally clutter our model - so that option is out (unless I have missed some way to filter them out from diagrams and miscellaneous windows (relationships, insert related …)

Another option would be to create shadow elements for all the attributes that I want to link to and then choose such an element in the type property for the referring attribute - but again clutter …  - so that one is out too.

A third option is DOA: Creating special reference tags that refer to attributes in stead of to classes - is not possible anyway.

The fourth option - which I'm considering - is creating an attribute tag, that holds ea_guid of the referred attribute -  but that will not be user-friendly in the EA gui, since it will only show a guid. I would probably create an accompanying tag that shows fx the name of the referred tag, and its parent element - and then keep that synchronized. I would also have to create a GUI to maintain such references.

hmmm - it would be great to hear tips from you on a better solution … ???

We have our own web components on top of a local EA repository, where we extract information via SQL. In fact we have a complete website with lots of views for different stakeholders.

Can we do this, if we move EA to sparx' EA cloud solution (with the EA cloud repository being actually in the cloud, not on our own network)?

Anyone having experience with this?

How do I open webpage in a browser from an EA JScript.
E.g. I want to add a script to an element's context menu that opens a webpage with specialized documentation views on that element.

General Board / No dockable window with table columns?
« on: December 11, 2018, 12:19:39 am »
I want to have a docked window with table columns - just like the docked window with class attributes, which synchronizes itself to selecting an attribute in a diagram or in the project browser.
Is that not possible? (EA 14, 1427)

Also: in a class on a diagram I can add an attribute with shift+cntrl+F9  - is there no similar function for table columns?

Just to make sure, that I haven't missed the feature:

Is it correct, that there is no method in the object model telling which elements (plural) have been selected in the search result?

This is great (and, of course, about time  :))
Did you notice - Now you can also have icons on your stereotypes (metatypes) that extends package.
Earlier such icons would only show up in the project browser for elements, not for packages.

I cannot find how to publish a package as a UML profile  in EA v. 14.1.1427
I have tried:
Select a UML profile package in project broser
Then I go to ribbon: Specialize / Publish
But only gives me an option of: Publish Diagram as UML Profile (not a package)
I tried it, of course – but it actually does only save the diagram as a profile

I also tried the command search and opened the Save UML Profile window – but same result

In EA 14.0.1423 it worked (although, as Geert Bellekens told me, I had to have a diagram open )

Has anyone of you succeeded in saving a package as UML profile in EA v. 14.1.1427?

General Board / How do I hide derived tagged values?
« on: September 19, 2018, 06:57:45 pm »
In the tagged values pane/window, the derived tagged values are shown below the other tagged values.
This causes confusion and irritates my users.
I haven't found a way to hide them from the pane/window.
Is it not possible to hide these derived tagged values from this pane/window?

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)

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"/>

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?

Pages: [1] 2 3 4