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 - Ksenia Wahler

Pages: [1]
1
Uml Process / EA conformance with UML 2.1.2
« on: June 11, 2009, 02:05:42 am »
Hi there,

Does EA fully conform to the UML 2.1.2 metamodel?

In the metamodel, an InformationFlow has an association to a Connector labeled realizingConnector. When I create an InformationFlow in EA, I cannot find anywhere to set the realizingConnector. Am I missing something or does EA not support this?

Thanks,
Ksenia

2
Hi,

I would like to include a Relationship Matrix Profile into a Model Template. Is this at all possible?

I exported a UML model where I created Relationship Matrix Profiles to XMI and included the exported XML file as a Model Template in an MDG Technology. However, it seems that the Matrix Profiles are not exported using the XMI export (even when the EA roundtripping option is set).

Anybody has a solution to this?

Thanks,
Ksenia

3
No, the :: does not work, I tried that already.

4
I just discovered what part of the problem is. There are some stereotype references across different profiles in my MDG Technology, which causes problems. Does anybody know if it is at all possible to reference stereotypes across different profiles?

For example, I have something like this now inside my MDG Technology file:

...
<UMLProfiles>
<UMLProfile profiletype="uml2">
<Documentation id="AD939260-B" name="P1"/>
  <Content>
    <Stereotypes>
      <Stereotype name="ArchitectureMetaData" generalizes="MetaData"/>
      </Stereotypes>
  </Content>
</UMLProfile>

<UMLProfile profiletype="uml2">
<Documentation id="AD939260-C" name="P2"/>
  <Content>
    <Stereotypes>
       <Stereotype name="MetaData">
         <AppliesTo>
             <Apply type="Comment">
              <Property name="body" value=""/>
             </Apply>
          </AppliesTo>
      </Stereotypes>
  </Content>
</UMLProfile>
</UMLProfiles>
...

I assume that due to scoping, the MetaData cannot be found from P1. As a result, the ArchitecturalMetaData stereotype cannot be instantiated in a model once the MDG Technology is installed.

How can one make such a reference work without merging the profiles?


5
Hi there,

I am creating a MDG Technology, which contains a large profile (several hundred elements) among other things.

While I can instantiate most stereotypes when I use the MDG Technology, there are several that cannot be instantiated. Simply nothing happens if I drag the stereotype from the toolbox into a diagram, or if I try to use the Add Element wizard.

I cannot find any difference if I compare the working stereotypes and the non-working ones (e.g. both extend the same metaclass).

Any ideas?

Thanks!
Ksenia

Pages: [1]