How to convert class objects into attribute objects?

[BCGoitcwoodard]

I have a package with many DataElement objects.  I captured them during requirements gathering.  I believe that this is a stereotype of Class.  Now I would like to treat these objects as Attributes, e.g. columns in tables.
How can I convert these objects from “class instances” to “attribute instances” which could be moved into other classes like entities or tables?

I did a lot of csv imports to establish values of important tags on the DataElements.  I would not like to lose this work.
Alternatively, can I copy the tagged values of class objects like DataElements over to become tagged values of Attributes like database columns?
Thank you,
CCW

[Geert Bellekens]

There is no simple build-in way to do something like that.

But it would not be very difficult to create a script that does this.

Geert

[Uffe]

Hello,


As Geert says there's no automation to do this for you.

But representation-wise, I think the simplest way forward is to use your DataElement classes as types for attributes in your entity/table classes. (I'm assuming you won't be using EA's built-in data[base] modelling facility as it's generally not a good idea to add your own concepts to the built-in metamodels; your additions will at best be ignored and at worst break something.)

This way, the tagged values in your DataElement classes will be shown in the attributes' properties, and accessible from the attributes as "extended" tagged values. No need to copy anything, just reference it.

HTH,


/Uffe

[BCGoitcwoodard]

Thanks for replying- sorry for taking so long to get back into the thread.  But -  I want to be sure that I get this right.  Can you explain how I would use EA to "use your DataElement classes as types for attributes in your entity/table classes".  By "type", do you mean a user-defined data type for an attribute or something else ?  Can you explain a little more how "the tagged values in your DataElement classes will be shown in the attributes' properties, and accessible from the attributes as "extended" tagged values."?
Thank you.

[Modesto Vega]

I will give a more nuanced answer. It depends on how you do your data modelling. If you use an ERD model showing entity–attribute-relationship - please see https://en.wikipedia.org/wiki/Entity–relationship_model#/media/File:ER_Diagram_MMORPG.png, all you need to do is convert the tables and attributes to nodes, and apply the ERD Profile. After that you could apply to ERD to data modelling transformation to create a proper.

[Uffe]

Hi again,


In order to use a DataElement class as an attribute type, first create the attribute and then in the Type dropdown, select Select Type... This brings up a dialog where you can browse to your class and select it. The DataElement is now the type of the attribute.

If you then select the attribute in the Features window and look at its properties (either in the Properties window or the Properties dialog), the tagged values tab ("Tagged Values" or "Tags") will show the tagged values from the DataElement.

This is in general. If you are working in ERD or a data[base] model, things are different.
ERD elements don't have UML attributes. You can add them (maybe not easily, but all elements in EA can have attributes) but then it's not an ERD model anymore so you're outside the intended way of working.
Similarly, while the columns in a data model table are implemented as attributes they've got a bunch of stuff added on top to make data modelling work, so again, going outside of that means something won't work as intended.

HTH,


/Uffe