v15.2 - DB Builder to allow EAUML::<component> as non-primary stereotype

[Paolo F Cantoni]

We're seriously looking into how to use DB Builder to model what we ACTUALLY see in our DB environment, especially under our requirement of supporting the DB R_E while allowing us to overload the rendering?  The overloading of the rendering is vital to allow enterprise wide-modelling in various viewpoints for the same object.

We have developed an environment where this is now possible and for modelling via diagrams, we can perform all the required use cases (such as managing FK Constraints etc.) while using our shapescripts for rendering.  However, this requires that the EAUML::<component> (<component> = table, view etc.) stereotype is NOT the primary.  This doesn't seem to hamper that part of EA from working as it should.

However, in classic EAUI, the DB Builder doesn't work this way.  It seems to require that the EAUML::<component> is the primary stereotype.  We feel that this is a self-inconsistent requirement!  Especially since EA allows multiple stereotypes. The positioning of stereotypes from a generated MDG can be problematic (as has been described in other posts).  Please rectify!

Thoughts?

Reported,
Paolo