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 - Michael Hafner

Pages: 1 [2] 3
General Board / Redefinition of UML-Attributes: How?
« on: March 25, 2010, 09:06:26 pm »
Dear all,

UML Superstructure 2.2 states that features may be redefined either "explicit[ly] with the use of a {redefines <x>} property string on the feature or implicit[ly] by having a feature with the same name as another feature in one of the owning classifier’s more general classifiers." (7.3.44)

EA: "When Enterprise Architect displays inherited features, it creates a merged list from all generalized parents and from all realized interfaces. If a child Class redefines something found in a parent, the parent feature is omitted from the Merge List."

I take it, however, that it is not possible in EA to explicitly redefine attributes? I have not found any advice on this in the documention.


General Board / Tagged Value Type RefGUID as link?
« on: March 27, 2010, 02:59:02 am »
Dear all,

EA's Tagged Value Type RefGUID provides references from one model element to another.

Unfortunately, this reference seems not to be navigable in any way,  neither within EA nor in the HTML documentation - in which the the target's GUID is replaced with its name (as a simple text string, and without any qualifier, say its namespace) - ?

Is it possible to somehow convert the reference into a link to the target's (or its owner's) page during export?


Bugs and Issues / Re: MySQL Repository: ODBC connection fails, EA cl
« on: March 04, 2011, 10:42:47 pm »
And wouldn't it be nice if EA didn't crash?
The reasons for a failed transfer may vary, but does any of them justify seppukku?   :)

Bugs and Issues / Re: MySQL Repository: ODBC connection fails, EA cl
« on: March 03, 2011, 04:36:11 am »
Check the point 6. here:

The options depends on the MySQL driver version, but on every versions they are similar...

Thou shalt read the documentation thoroughly...

Luis, if you happen to come to Bonn, don't forget to drop by for a beer. It works.

Now there remains some collation stuff to do, and some duplicate GUIDs seem to have found their way into the project (how on earth...), but I'll deal with this.

A big thank-you to Madrid!

Best regards,


Bugs and Issues / Re: MySQL Repository: ODBC connection fails, EA cl
« on: March 03, 2011, 02:14:52 am »
Have you checked the "Don't optimize column width" and "Return maching rows" at the MySql ODBC driver?

I don't see those options on the details panes (v5.1.8)...

Bugs and Issues / Re: MySQL Repository: ODBC connection fails, EA cl
« on: March 03, 2011, 01:34:50 am »
The steps are:

1. Create a empty database
2. Run the SQL script
3. TRANSFER SOMETHING (maybe a empty EAP, a template from an EAP or another database...). Use the "Tools | Data Management | Project Transfer" dialog.
4. Connect to the new Repository

The step 3 is mandatory, you must transfer at least an empty model in order to be able to connect in step 4.

Look for the entire process at: (the steps could not correspond with the steps described by me, but describes the same)


Yup. That's precisely what I'm trying to do. Dialog Project Transfer, Transfer Type EAP to DBMS. I select a source project. I then define a target project - selecting Microsoft OLE DB Provider for ODBC drivers, selecting a data source etc. on the way -, test the connection, go back to the Project Transfer dialog, click the "Transfer" button, and bada bing, bada boom, EA crashes.

Bugs and Issues / Re: MySQL Repository: ODBC connection fails, EA cl
« on: March 03, 2011, 01:02:02 am »
Have you uploaded an EAP file to MySQL? This is mandatory previusly to try to connect to it.

Hi, Luis,

thanks for the reply, but I don't get you. I have to upload an EAP file? - I want to transfer an EA project from an EAP file to a MySQL database. An EAP file is a jet database, right? Now, my documentation tells me to set up a MySQL database via Sparx's SQL script (v.s.), and to connect to it via ODBC. The transfer is (or should be) done by EA: retrieving the data from the jet db, handing them over to MySQL &c.
This is the point where the problem occurs: MySQL schema exists, ODBC driver works, EA transfer fails. Have I missed something?


Bugs and Issues / Re: MySQL Repository: ODBC connection fails, EA cl
« on: March 02, 2011, 03:35:03 am »
Just the "have you plugged in the terminal"-question: is your repository initialized with EA's resource SQL script?


Yes. I have used the script from

...without any modification. No problems of any kind.

Bugs and Issues / MySQL Repository: ODBC connection fails, EA closes
« on: March 01, 2011, 06:44:04 am »
Dear all,

v8.0: Trying to establish a connection to a MySQL repository, I encounter a problem:

1. MySQL is up an running
2. EA schema is set up in db
3. ODBC driver is installed (MySQL ODBC 5.1 Driver; TCP/IP Server, Port 3306)
4. Test of connection is succesful

5. However, when starting the project transfer, I receive the following message: "Enterprise Architect has experienced a network error and will close down". Not surprisingly, EA closes down after that...

Q #1: What may be the reason for this (and why does EA have to close down in this situation)?

Q #2: I only need to "dump" the project database into a MySQL database; is there any other way to do this (in case the network problem can't be solved)?

Thanks for any help!

Uml Process / Re: How to Model Supertypes and Subtypes?
« on: July 30, 2012, 06:56:54 pm »
A more formal approach to powertypes: "The notion of power type was inspired by the notion of power set. A power set is defined as a set whose instances are subsets. In essence, then, a power type is a class whose instances are subclasses. The powertypeExtent association relates a Classifier with a set of generalizations that a) have a common specific Classifier, and b) represent a collection of subsets for that class." (From UML Superstructure 2.3, p. 72 at

Discussion about PTs from the forum:

Uml Process / Re: EA-Connector to element feature - UML compatib
« on: February 23, 2010, 04:10:43 am »
Please, Frank, why so exited?
"Don't care if the pope...what they bloody well please" - Boy oh boy...

First of all, I do think that you should care about the specification of a standard if you decide to use it. (Submitting the matter to a pontifical commission might have its charms... :-)

Secondly, my question was not meant as a criticism of EA. - Having used another tool for some years, I am now exploring EA, and I'm flabbergasted by its functional range. I'm deeply grateful for a tool like this (TWIMC). OK?

Thirdly: If we agree it's an extension, well and good. However, while it's possible to cut out the extension and to still keep a valid model, this comes at a cost. At best it means a dumbing down of the model. At the worst it distorts the model. An association among attributes does not (onto)logically imply an association between the classes which own those attributes.

Finally: I just have to create a UML model plain and simple. No extensions. Captain's orders.


Uml Process / Re: EA-Connector to element feature - UML compatib
« on: February 20, 2010, 04:11:29 am »
Sorry and thanks Paolo,
you are right; the two statements do not mean the same. A UML:association is not a relationship among instances, it specifies a relationship among instances.

Until recently, my main source of information about UML was not the specification but Rumbaugh's, Jacobson's, and Booche's Manual (The Unified Modeling Language Reference Manual, Second Edition; "RJB"), and sometimes I have doubts whether the two documents are compatible (v.i.). OK; a manual is a manual, and the specification is the specification.

Dear all,

I am still not sure whether associations between attributes are legal in UML:


1 - A (binary) association describes a set of tuples (viz. a "relation" as a "class of ordered pairs").
2 - The values (or members) of the tuples refer to instances of a given type.
3 - An instance of the association is called a "link": Another tuple the values of which are typed instances (they do not refer instances).
4 - Attributes in a user model are instances of the metaclass "Attribute" from the user model's metamodel (M2: UML; profiles).
5 - Therefore, if there is an association in the metamodel with entTypes "Attribute" and "Attribute", there may be links among the attributes in the user model.
6 - These links connect model elements - e.g. "SomeClassA.title" and "SomeClassB.title". They do not imply associations among the model's instances - e.g. SomeInstanceA.title "Title #1" and SomeInstanceB.title "Title #2"


7 - RJB say that "an association is a relationship among two ore more specified classifiers that describes connections among their instances."
8 - Attributes are instances of a metaclass, and they have instances "out there" (RJB) in the actual system. However, they are no classifiers ("Attribute" is, attributes are not. cf. Superstructure, Annex F).
9 - If 7 and 8 are correct, an association between attributes would be difficult.

Do you agree so far? - As I understand it, JRB's statement is not covered by the definition in superstructure 2.2., but nevertheless: Is (9) really a problem? And, if not: Could any other application than EA deal with links to element features?  (By the way: The information is stored in tagged value "styleex", right?)

Sorry, I don't want to bother anybody. In fact, it would greatly facilitate my work if I could use attribute associations.


Uml Process / Re: EA-Connector to element feature - UML compatib
« on: February 02, 2010, 02:35:16 am »
Simon, Geert,
thank you very much for your prompt reply! - Would you agree that the following defintions from UML 2.2, Superstructure, cover a dependency between attributes but not an association (an association being a relationship between typed instances)?

7.3.47 Relationship
Relationship is an abstract concept that specifies some kind of relationship between elements.

7.3.12 Dependency
A dependency is a relationship that signifies that a single or a set of model elements requires other model elements for their specification or implementation.

7.3.3 Association
An association describes a set of tuples whose values refer to typed instances.

Uml Process / EA-Connector to element feature - UML compatible?
« on: January 30, 2010, 10:07:56 pm »
Dear all,

EA makes it possible to connect elements to element features - a very useful feature, but is it UML? Browsing UML 2.2, I do not find any reference to it, neither to the notation nor to the concept - ?


Dear all,

being big fans of EA as a powerful UML tool, we are considering the use of EA as an OWL modeling tool as well. Working with EA-diagrams is much quicker than with more text/dialog based tools like, say, Protegé.

Would that be a wise choice? Documentation about MDG technology ODM is sparse; will this technology be kept alive (maintained, updated)? By whom?

Thank you

Pages: 1 [2] 3