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 - Viking

Pages: 1 ... 4 5 [6] 7 8 ... 16
I'm not sure about most of the questions, I guess you'll have to find out using trial and error.
I can give you an easy tip on the question which Metaclass to extend.
If you remove the stereotype of an element then only the Metclass remains. That is the metaclass to extend.
Geert, many thanks.

Do you know, why EA creates the meta class, I create in a diagram by using Toolbox > Profile > Metaclass, also in the Project Browser? I expect just a link resp. a reference to the original one, which should be part of the system (so somewhere in the system resp. another folder, which is not accessible by the user). It seems to me that I get a copy.

General Board / Re: UML Types for Standard BPMN 2.0 stereotypes
« on: March 15, 2017, 03:51:09 am »
1.) You will need to extend your own event-sterotype (MyStartEvent) from <<metaclass>> Event (the standard UML::Event).
2.) Your extended stereotype will need to generalize the BPMN2.0::StartEvent sterotype.

Hope this thread is still read by the participants.

My question is, if I generalize my own MyStartEvent stereotype from BPMN2.0::StartEvent sterotype, why do I need to extend my own event-sterotype (MyStartEvent) from <<metaclass>> Event ? Don't I inherit the extension from the generalized StartEvent ?

Why take a proven, existing language, if you can invent a new one? Or even another one for transformations?

This is a very good question. I don't know if we will find out the reason one day.

Hi together,

We created a MDG. A part of it is the new stereotype "Process Step" with an own shape script. Dependent on the diagram type it is used, the Shape Script shows a BPMN Activity or ArchiMate BusinessProcess. We have learned that we have to use Generalization and / or Extension. But we think we did not understand the concept behind it. The MDG does not work as expected.

Our questions are:
(1) Can a new stereotype (here "Process Step") use Extension to a (or several) meta class(es) and Generalization to a (or several) sterotype(s) in parallel?
(2) To which Stereotypes should we point Generalization of "Process Step" (currently we are using Archimate2::ArchiMate_ApplicationComponent and BPMN2.0::Pool)?
(3) Is multiple Generalization possible (in our exampe above "Process Step" points to 2 sterotypes (see (2))?
(4) To which MetaClass should we point the Extension of "Process Step" (we tried "Class")? Or do we only need Generalization because the sterotypes we used for Generalization (see (2)) should have been extended a MetaClass already).

Many thanks in advance, V.

Shapescript is dumb as bread. IF only accepts one HasProperty method as argument. No string comparison. No arithmetics. q.
Really? I thought that the existing scripting languages were not good enough and it was necessary to invent a new one. Is that a misinformation?

Hi together,

is there a way to use an If-Or-Statement within a shape script?

"if-else" is not an option, because then I would have to copy the script within the brackets (e.g. if (a=1) {do XY} else if (a=2) {do XY}). I need something like "if (a=1) else if (a=2) {do XY}".

Setting a variable inside the shape script could help me, but I think that this is not possible (e.g. if (a=1) {var1=1}; if (a=2) {var1=1};  if (var1=1) {do XY}).

Any suggestions? Many thanks in advance V.

Thank you, Uffe.

I did not want to use the concept for software development. I just thought there where an analogy in software development to better understand the concept.

Hi together,

We created an own profile with MDG. Unfortunately I do not understand the concept behind "Extension" resp. "extends". What does "extends" mean in conjunction with metaclasses (resp. a stereotype extends Metaclass) resp. what effects would "extends" have on software, for example? I only know and understand "extends" in conjunction with UseCases.

Many thanks in advance, V.

Suggestions and Requests / Re: ToolBox - reuse of other stereotypes
« on: March 06, 2017, 11:21:56 pm »
Solved. We had to use inheritance of stereotypes.

We solved the issue. The our stereotype has to inherit from the Pool stereotype.

Automation Interface, Add-Ins and Tools / Re: Base Class
« on: March 02, 2017, 02:59:53 am »
‘base_’ extendedMetaclassName

The name of the Property typed by the extension Stereotype (the ExtensionEnd) is:

‘extension_’ stereotypeName

Constraints are frequently added to Stereotypes. The above Properties may be used for expressing OCL navigations. For example, the following OCL expression states that a Home Interface shall not have attributes:


I am as confused as before :-)

Automation Interface, Add-Ins and Tools / Re: Base Class
« on: March 02, 2017, 02:52:53 am »
If you explain what you mean by UML types.

Project > Settings > UML Types.

Here I implement stereotypes and shape scripts.

Automation Interface, Add-Ins and Tools / Base Class
« on: March 01, 2017, 10:46:26 pm »

Could somebody explain to me the concept behind Base Classes in UML types, please?

Many thanks in advance, V.

1. Does your element have all of the tags and properties that the shape script is looking for? Are their values what the shape script is expecting?

We tried this with the original Shape Script of the Pool, provided by EA. We did not change anything. We also set all tagged values the shape script uses.

We did the same with other scripts and they work as expected.

That's why we think there are some inherited variables, global variables or baviour of EA, used for some shape scripts in the background. See also,37866.msg236243.html#msg236243.


We built up an own Toolbox. For the Toolbox we reused the ShapeScript of BPMN Pool in our own stereotype.

The problem is, nothing gets displayed when we drag the element into a diagram?

The reason could be that the shape script of BPMN Pool uses "drawnativeshape()". Probably it inherits this method.

We use <all> as Base Class. Should we change this? We already tried all Base Classes but nothing happens. Or do we have to use further tagged values, inherited from the super class(es)? We currently use the tagged values displayed by the Property Dialog of the standard BPMN Pool. Which ones do we have to use and with which default values?

Many thanks in advance, Viking.

Pages: 1 ... 4 5 [6] 7 8 ... 16