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 ... 5 6 [7] 8 9 ... 62

in Visual Studio Project Properties, Debug for the DEBUG configuration activate
- Enable 'native code debugging'.

The forum also contains a thread about this.

Kind regards,


General Board / Re: Showing constraints
« on: July 11, 2017, 02:18:57 pm »

you can:
- Attach a note to the class (Link from Class to Note)
- Right Click on the Link from Class to Note, Select 'Link this to an Element Feature', Select and choose
-- Constraint for the Class Constraint
-- Attribute for the Class Attribute

As far as I know, you can't visualize the Attribute Constraint on the Diagram.

Kind regards,


General Board / Re: Structured Node - Activity
« on: July 03, 2017, 12:20:26 am »

When you drag a 'Structured Activity' from the Toolbox to the canvas, you can either create a Simple Composite or from a selection of  'Structured'. See also the online help (F1 in the diagram).

Just give it a try, and you quickly understand it. Drag a 'Structured Activity' from the Toolbox to an Activity Diagram and observe Diagram and Project Browser. With ALT+G you can navigate from Diagram Element to specification in Browser.

'Simple Composite':
It's an Activity which is refined by an Activity Diagram. A useful construct, often called Composite. You will learn to appriciate it. It hides complexity and with a double click you jump into the refinement.

Personally, I never use them. If I have e.g. a loop I usually model it as a 'Composite Activity'/'Simple Composite'. The name is then something like 'Loop over all..'. The refinement diagram (composite) contains what inside the loop happens. If you use such a construction you get easy to understand Activity diagrams. If you try to model loops with Case and Merge you soon get a messy diagram. It takes long to understand the sense behind it.
Another possibility is to use <<Stereotypes>> like <<loop>>.

Kind regards,


General Board / Re: Autonumbering on stereotype level
« on: June 30, 2017, 04:03:58 pm »

I'm working on integrating Auto Counter on Stereotype level in Open Source hoTools. Soon, I'll release it

If you are interested or have ideas, read the WiKi and contact me. The basic ideas are:
- Auto numbering on Stereotype level (Type, Stereotype)
- For Name and Alias
- Configure by format string like 'My0.00.0.0_Best'  (0=placeholder for numerical value)
- Support Diagram with Drag and Drop, the usual way
- New Auto Numbering for the whole model and choosen Type/Stereotype
- Configurable in Settings.json


Kind regards,


Thanks Uffe,

it works the way you described it. I only tried Tagged Value and that doesn't work.

Best regards,



you may use Dynamic Documents to see the Tagged value of the selected Diagram Element in the Document Window. You can define what you want to see of a selected element. There is also a Webinar available.

I know, it's not exactly what you wants and I'm not sure if it works for Tagged Values of type Memo.

Kind regards,


General Board / Re: Autonumbering on stereotype level
« on: June 26, 2017, 06:37:36 pm »

in principle it's simple: Just override the EA Broadcast Event  'EA_OnPostNewElement'.

The drawback is:
EA currently has a bug that it doesn't support the Broadcast Event 'EA_OnPostNewElement' with the Specification Manager.

The other thing is that there are a lot of Use Case. Just for example:
- Make the created number unique for stereotype in the whole model
- Unique in package or package branch
- Handle initial applying the numbers to existing Elements (e.g. use creation date to give a reasonable sequence).

I have implemented a basic approach in the open source 'hoTools'. It's not released yet but you can explore or contribute to code and ideas.

You can configure with JSON:
- Stereotype
- Start value
- Format to build like 'myRequirement_0.00.00_fun'
- ..

Currently, I'm thinking about applying the rules to existing Elements (based on e.g. creation date).

If you like to contribute or have ideas just contact me.

Best regards,




The SPARX answer:
This is a known issue which is yet to be resolved.


Thanks for the answer.

I'll file a bug report.

Best regards,



I try to auto name newly created  Requirements with the EA Broadcast Event 'EA_OnPostNewElement'. It mostly works as expected.

When I add requirements, e.g. Functional Requirments, with the Specification Manager EA don't send the Broadcast Event 'EA_OnPostNewElement'.

Any idea?

Thanks for your help!


General Board / Re: Autonumbering on stereotype level
« on: June 23, 2017, 07:58:15 am »
Hi mrblack12,

here are a lot of people who want their special solution - for a thank you - maybe.

Here are also a lot of engaged persons who invest their leisure time to answer questions, share their knowledge, develop scripts and presents useful Add-Ins. For nothing!

I think you are working for a company which will profit. If your company is really interested in a solution, get some money and make a little open source project.

In this Forum you'll find people to realize your dreams. Be aware: A general solution beyond "FR-" is some work and not just 10 lines of code.

Please appreciate the great help you get here for nothing. Personally, I don't like remarks like 'The only reply I got..'.


Automation Interface, Add-Ins and Tools / Re: Publishing Add Ins
« on: June 21, 2017, 11:03:13 pm »

a good source is Geerts tutorial on the EA community:

Kind regards,


Uml Process / Re: How to use IBD and properties
« on: June 21, 2017, 10:22:17 pm »
Hi Mark,

I have just redone it. It works. I have done it this way:
0. Create Block Definition Diagram with:
1. Create Block 3
2. Create Block 1 + Block 2 as composite part of Block 3
3. Make Association between Block 1 and Block2
3. Name the Association 'MyAssociation'

4. Create Internal Block Diagram from Block 3
5. Drag Block 1 as Property into Diagram (new)
6. Drag Block 2 as Property into Diagram  (new)
7. Make Connector between Properties of Block1 and Block2
8. Right Click on Connector,  Advanced, Set Connector Type
    You can select an Association from BDD or 'none' for the connector in IBD

You may use multiple Associations and connectors. The usefulness is in your responsibility.

Kind regards,


Hi TheMintRubber,

I checked your Code. It works as expected if I add the below code.

Code: [Select]
public class EAAppInstance
public EA.App EaApp { get; }
public int ProcessId { get; }
public EAAppInstance(EA.App eaApp, int processId)
EaApp = eaApp;
ProcessId = processId;


I think the effect is similar to the EA DLL 'SparxSystems.Repository.dll'. This SPARX DLL get's the repository from the passed EA process id and was first released with EA 13. I think this DLL also works for older EA releases, but I'm not sure about.

Thanks a lot for sharing your code. It also gives me an inside how such things work.

Kind regards,



I doubt that EA is a good solution to simulate a business decision.

In my experiences, EA is top in understanding and discussing complex coherences. With this profound knowledge you gain from modeling and discussion, you can develop a simulation. Often it's a good idea to simply use Excel.

Maybe I have missed the point.

To get a quick understanding what you can achieve with EA you may have a look on the SPARX Webinars or whitepapers.

Kind regards,


Pages: 1 ... 5 6 [7] 8 9 ... 62