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 ... 44 45 [46] 47 48 ... 61
Bugs and Issues / Re: SysML 1.3 Aggregation
« on: May 27, 2013, 10:38:03 pm »

thanks for clarification. I wasn't correct. †In the following I try to explain it for EA.

according to SysML 1.3 page 65 a property may have the stereotypes:
  • <<DistributedProperty>>
  • <<ParticipantProperty>>
  • <<ConnectorProperty>>
  • <<>> No Stereotype it's simply a property

In my opinion the compartments 'parts' and 'references' express the usage of the property (page 54). In EA this is "isReference=true/false" of the property.

In EA:
  • If you use an Association or Reference Association 'isReference' of the Property is true. It's visualized in the reference compartment.
  • If you use a Composition or PartAssociation 'isReference' of the property is false. It's visualized in the properties compartment. In my opinion this isn't according to SysML 1.3

In my opinion there is no explicit Property of type part (it's in fact a compartment and the kind of usage).

I agree that the <<ParticipantProperty>> is part of an association class (thanks for your advice).

I hope that was it. Please check once more with your expertise.



Bugs and Issues / Re: SysML 1.3 Aggregation
« on: May 24, 2013, 11:47:14 pm »

in SysML 1.3 only properties with different stereotypes exist. The property <<ParticipantProperty>> is equal the former part. Parts don't exists in SysML 1.3.

Just drag the <<ParticipantProperty>> from toolbox to the internal block diagram.

If you have the wrong property type set or reset:
- <<ParticipantProperty>>
- isReference = true (advanced properties), if you have a reference
- isReference = false (advanced properties), if it's the original/defining part/property

The EA behavior of auto generating the correct <<stereotyp>>, isReferenced by drag&drop and composition isn't always what you would expect. But by simply correcting <<stereotype>>,IsReference you have a work araund.

Kind regards,


Bugs and Issues / Re: Warning: Underlying model data may have been m
« on: June 13, 2013, 05:47:15 pm »

I'll check it. It's the project of a collegue.

Kind regards,


Bugs and Issues / Re: Warning: Underlying model data may have been m
« on: June 13, 2013, 03:01:02 pm »

the warning regularly occurs (30 minutes to 1 hour). There was only one EA instance involved.

Kind regards,


Bugs and Issues / Warning: Underlying model data may have been modif
« on: June 12, 2013, 03:31:00 pm »

EA 9.35 with SQL Server and Controlled Packages (SVN).

I checked out a package and later I got the warning:
Warning: Underlying model data may have been modified by another user. Press OK to refresh.

After pressing OK the Controlled package is empty.

For me the message makes no sense because I checked out the package and no one else could have modified anything inside the package.

Thanks for your help!

Best regards,


Bugs and Issues / Re: Tree position
« on: June 11, 2013, 08:09:02 pm »

good ways to get familare with EA scripting/addins are:
  • Thomas Kilians Ebooks (Inside+Scripting)
  • The EA Examples in the Scripting View (Manage PagagesExample)
  • The EA Examples in the Scripting View (Manage Elements Example)

 † † (in group Local Scripts)

In essence you have to rercursively go through the collection Packages. TreePos is the position in the current collection of packages.

Best regards,


Bugs and Issues / Re: Adding a script to a constraint block
« on: May 04, 2013, 02:58:31 am »

the function is OS independent. I tried it with XP, Windows7 and 8.

If I remember something I'll inform you.

Best regards,


Bugs and Issues / Re: Adding a script to a constraint block
« on: May 04, 2013, 12:32:38 am »
Hello Martin,

I remember having the same problem.

You have to ensure:
- Installed the ultimate or system engineering version of EA
 †(I'm not sure about that and installing the trial version)
- In Settings, MDG Technologies check SysML 1.3

After that it worked. I made a little example for my own and successfully tested it. I admit: It takes me some time.

Always a good idea is to search in the forum for SysML, constraint block or so.

Best regards,


Bugs and Issues / Re: Locking Vertical or Horizontal Axes for Connec
« on: April 03, 2013, 02:22:39 am »

  • Tools, Options, Links
  • Click on 'Force perpendicular line'

Best regards,


Bugs and Issues / C-Code Generation, no typedef private enum, struct
« on: January 28, 2013, 09:33:08 pm »

EA generates the typedefs for enum, struct,.. in *.h File for public\protected classes.

EA don't generates typedefs for enum, struct,.. in *.c File for private classes.

If such an enum, struct is private I would expect EA to generate the associated stuff in the *.c file.

The Reverse Engineering function works as expected.
  • Typedefs from *.h are public.
  • Typedefs from *.c are private.

Thanks and kind regards,


Bugs and Issues / Re: C Gode Generation, handling private class elem
« on: January 11, 2013, 01:52:02 am »
Hi GŁnther,

I also stumbled about the problem and posted

I think about developing two scripts to handle the problem.

The ideas behind the two scripts are:

Two or so changes in the template to handle extern, default, or so.
  • Duplicate the attribute as private
  • Run the original EA script
  • Remove duplicate attribute

The idea behind it is:
The public attribute generates the *.h entry with EA standard
(extern, no default,..) generation.
The private attribute generates the *.c entry with EA standard generation.

  • Run the original EA script
  • Remove duplicate attributes

May be SPARX provide a solution.

I appreciate any suggestion.

Kind regards,


Bugs and Issues / Reverse Engineering C global variable
« on: January 10, 2013, 06:55:24 pm »

From C-Code:
Code: [Select]
*.h †File † † † † *.c File
extern int v; † †int v;
I would expect to get in EA a class with a public attribut v.
public int:v

What I get is:
public †int:v
private int:v

In fact I get two attributes with the same name, one public and one private.

Is there a way to avoid this problem?

Thanks and kind regards,


Bugs and Issues / Simulation Activity don't obey Token concept
« on: January 07, 2013, 11:19:55 pm »

an activity/action is started when all incoming control flows have a token.

If there is a decision, e.g. yes\no,  and both edges are going to an action\activity the action\activity  mustn't started.

The manual simulation don't wait for all incoming tokens to start an action\activity.

Kind regards,


Bugs and Issues / SysML required †& provided Features
« on: January 05, 2013, 12:24:33 am »

I miss something to define feature direction for properties and behavioral features (operation, reception, attributes,..): See SysML 1.3 (12-06-02):

Code: [Select]

Kind regards,


Bugs and Issues / SysML Item Flow with item property
« on: January 04, 2013, 11:23:46 pm »

if I read the SysML specification right than can an Item Flow be labeled with either an Classifier or an Item Property.

Classifier works fine (Advanced, Information Flow conveyed).

Is there a possibility to use an Item Property\Property instead of the classifier?

Kind regards,


Pages: 1 ... 44 45 [46] 47 48 ... 61