In a related posting
[size=13]Analysis vs Data Modelling Entities[/size] I bemoan the inability to correctly handle data modelling entities via stereotypes. I hint that EA need to create more element types (such as Table).
I'm trying to create some conceptual data models - so I'd like to stereotype these elements as entities (since although there is an element type called entity it's NOT a class which is what Jacobson's entity concept is...). You could view a data modelling entity as an {abstract} Table. Anyway, I'm trying to achieve my end of being able to apply data related functionality (columns, keys, indexes etc) to my elements which I'd still like to stereotype as (at least entity).
So I create a table. Maybe I can still get table functionality by making it a secondary stereotype? I make the stereotypes «entity,table». First thing that happens is that the table icon disappears. Pity, but since the whole diagram is a data modelling one, not a show stopper...
OK, open properties. There's the table detail tab... So far so good! Open the tab, and select column/attributes - the correct dialog comes up... Great! Maybe this will work!
Small show stopper - I can't assign the datatype.
As a consequence, I can't assign foreign key constraints because that dialog (correctly) requires that the datatypes be known before listing the candidate columns for the constraints.
This MUST be rectified ASAP!
On other than planet Sparx, a table is a table is table. Not, a table is sometimes a table if the developer feels like it or has a good day...
Frankly, the more I use this product, the more I'm at a loss to understand HOW it is possible to create a product that behaves this way...
At the minimum, if a stereotype affects the behaviour of the UI, IT MUST BE CONSISTENTLY APPLIED!
And before it is suggested - why don't I just mark the table as abstract... I will do so! However, I still need to stereotype the tables to indicate their different behaviour! That is the true meaning of stereotypes.
A Table is as different from a Class as a Component is. There are other non-UML elements within EA, why not make Table and View elements in their own right? This has already happened with Interface...
Consistency, Consistency, Consistency! TMPaolo
[size=10]Using EA in spite of EA, NOT because of it![/size] TM[/color]
