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 - Helmut Ortmann

Pages: [1] 2 3 ... 60
Suggestions and Requests / Re: RAML
« on: February 20, 2018, 04:22:50 pm »

have a look at GitHub (

Best regards,


General Board / Re: Report Diagram/model changes when SQL schema updates
« on: February 15, 2018, 06:16:02 pm »

well, I don't know your Use Case of:
- updating your metamodel
- modelling the dependency between metamodel and UI

So I assume:
-  You update your metamodel at some time
-  You mark deleted and/or modified metamodel items somehow (name, tagged value,..)
-- Modified elements you may find via modified date.
-  You have modelled the dependencies between metamodel and your UI by means of dependency or so

With that you can write an SQL query:
- Find all metamodel items that are modified in your last metamodel update
- Find all UI Elements with a connector of type <<dependency>> to the found changed metamodel items
- Find all UI Elements with a connector of type <<dependency>>which are linked to deleted metamodel items

If you have modelled:
- Metamodel
- UI dependency to metamodel
- The change you have done to the metamodel (new, modified, delete)

finding the impact is an SQL and using EA <<ModelViews>>.

If your issue is finding changes to the changed metamodel (update, new, delete) you have to think about other solutions.

Best regards,


Uml Process / Re: Modeling complex component associations and interfaces
« on: February 12, 2018, 10:53:49 pm »
Hello Miktaylor,

I think what you call an association is a connector (connector between ports). An association is in UML/SysML a different concept.

In doing a functional view, I would avoid using Components. Components are more an implementation concept. Not a thing a Functional View should focus on. Personally, I would use a stereotype <<func>> or so to make it clear that's a pure Functional Class/Block or whatever.

To visualise and check the Port/Connectors you can use SQL ModelViews, and I also think Matrix Views.

In my opinion to combine small interfaces is a good idea.

In EA you can visualise those interfaces on Ports by either:
- Lolipop notation of Required/Provided Interfaces
- Visualize the port type, the interface (port:IMyAggregatedInterface)

The difference here in my opinion and usage are:
- The Lolipop notation emphasises more a software architecture.
- Port types stresses more the flow of information

To see such things in practice, or get some other ideas, a look into SysML may help. Personally, I like the SysML BDD (Block Definition Diagram) and the IBD (Internal Block Diagram). In UML Class Diagram and Composite Structure Diagram. From my first view, such concepts would fit into the world of IoT.

Best regards,


General Board / Re: Report Diagram/model changes when SQL schema updates
« on: February 12, 2018, 08:56:26 pm »

If I have understood you right, you want to model and visualize the relationship between a UI element and the database model modelled in EA.

In my opinion, the best way to visualise such relationships are:
- Matrix  (Relationship Matrix in EA with or without overlay, something like a CRUD Matrix)
- ModelViews (SQL results visualized as a table)

To edit or visualise particular parts you can use Diagrams which contains:
- Tables, Columns or so
- UI Elements or so
- Dependencies to connect UI Elements with Columns or so

With EA Matrixes you can also edit relationships between SQL schema and UI.

The relationships you can easily see in the diagram and you can highlight them with EA Filtering.

I would recommend a stereotyped dependency to model the relationships. To define such stereotypes, I would use a UML profile, distributed by an MDG.

Regarding Diagrams:
Diagrams are a view of something you like to show someone else. It's up to the modeller or to standards to define diagrams and their meaning.

Best regards,


General Board / Re: Auto-numbering based on stereotype
« on: January 30, 2018, 06:13:13 pm »

the open source hoTools supports auto numbering for arbitrary types and stereotypes. See:

Best regards,


General Board / Re: Requirements in EA or Doors?
« on: January 30, 2018, 06:09:01 pm »

I have almost the same experiences as qwerty.

Looking at the functional aspect, taking beside budget, image,...
- EA is excellent in integrating requirements with Model, Test,...
- DOORS and the other requirements specialists are great in doing requirements but often lacks behind in integration

Best regards,


General Board / Re: Synchronizing ports ibd <-> bdd
« on: January 26, 2018, 07:41:32 am »

Have you tried Custom Reference? Find, Custom Reference (Strg+J).

If I have understood you correctly, you have an algorithm to find the diagram for the part. If so you can use:
- Script / AddIn
- Search (SQL+Addin-Search)

Best regards,


General Board / Re: SCC interface to PTC of EA does not find Unique IDs
« on: January 15, 2018, 08:20:39 pm »

I've worked a lot with EA and PTC. In the end, it works, but sometimes it takes some time.

Have you set SCC in PTC on all PCs with admin rights?
- File, Integrations with Admin rights. A boot would not harm.

Best regards,


Hi Guillaume,

looks good! I tested the portable release with a test user who has no admin rights.

Making the registration via code has its charm. There is no fiddling with the right version or using Heat and copy and past.

Could you publish the code? Yes, it's not complicated but using code is easy and reliable.

I'm not sure which approach I use in future. Putting the dll registration in WIX or integrating your peace of code.

With the single Package Authoring approach, there is only one *.msi file and the user choose whether to install per-user or per-machine.

Thanks and best regards,



I've tried a bit to find an easy solution to install without local administration right. I use WIX 3.11.

The easiest one is quite simple. Microsoft installer handles all the stuff with the folders, putting the registry keys to the right location. The major things are:
- Add to <Package>
--  InstallScope='perUser'
--  InstallPrivileges='limited'
- Add SetProperty:
  <SetProperty Id="ProgramFilesFolder" Value="[LocalAppDataFolder]" Before="CostFinalize"><![CDATA[NOT Privileged]]></SetProperty>
- Don't use advanced WIX UI (User Interface)
- Register to EA: RegistryKey Root="HKCU" Key="Software\Sparx Systems\EAAddins\hoReverse">
- Register dll: <RegistryValue Root="HKCR" Key="CLSID\...
  (Standard for WIX tool Heat)

I think about making this easy approach to always install for a user to my standard method. Easy to develop and to use! You can see an example in hoTools, branch Development, AaddinSimpleNoAdminSetup.

It's possible to make an *.msi file with WIX for per user or per-machine install. It took me a while to figure it out and to get it running. During install you have to go to advanced (not click install) to make a proper per-user install without asking for admin. See the references.

It's complicated, and you have to install in Advanced Mode to get it properly working without asking for admin rights. The main things are:
- Register to EA: RegistryKey Root="HKMU" Key="Software\Sparx Systems\EAAddins\hoReverse">
- Register dll: <RegistryValue Root="HKCR" Key="CLSID\...
  (Standard for WIX tool Heat)
The Installer keeps care of the correct location in the registry (user/machine).

You can see it at GITHUB in my hoReverse, Branch Development.

I would also like to hear about your experiences.

- Install per user without admin rights is quite simple with WIX
- Install with GUI for per user and per machine may cause you long nights. But it works with one drawback I know about.

Best regards,


-  Basics: Single Package Authoring
-  Proper UAC Control (for per machine / per user) in WiX

Uml Process / Re: Action pins and instances of artifacts
« on: November 21, 2017, 07:22:31 pm »
Hi Uffe,

I don't know why UML or EA says that an instance of an artifact can't be part of an object flow.

If you model e.g processes or work flows it's important. The SPEM profile is an example.

Best regards,


General Board / Re: attribute range and unit; best practice?
« on: November 21, 2017, 05:43:49 pm »
Hi Paul,

I usually make a profile and define some types with tagged values. These tagged values I can easily visualize on the diagram but it's also possible to use them by Search, Script or Generator. It's easy to assign the type to an Attribute. Then the Attribute has e.g. Unit, range or whatever is important to you.

Usually I call them domain type like 'OutsideTemperature', 'Budget' or 'Money'. I define the tagged values and then I can ensure that every usage has to comply with this definition. Often I use prefixes to label my domain types as 'DomainTypes'.

Best regards,



if I haven't done something stupid it's enough to change WIX install:
- Add to <Package>
--  InstallScope='perUser'
--  InstallPrivileges='limited'
- Make sure install into accessible folder like '..user\appdata\local\apps\'

If you use WIX UI to decide whether to install per user or per machine it should work in the per-user case without admin rights.

WIX seems to handle registry keys on its own.

I tested it with a Windows10 standard user.

Kind regards,


Hi Guillaume,

regarding ICE57:

Maybe this helps:

Could you please publish your working WIX install files for non admin installation?

I think there is a lot of interests.

Thanks a lot,


Pages: [1] 2 3 ... 60