Book a Demo

Author Topic: Analysis vs DataModelling Entities  (Read 2068 times)

Paolo F Cantoni

  • EA Guru
  • *****
  • Posts: 8626
  • Karma: +259/-129
  • Inconsistently correct systems DON'T EXIST!
    • View Profile
Analysis vs DataModelling Entities
« on: October 18, 2007, 05:12:33 pm »
Some terms in modelling are overloaded...

Entity is one of them...  However, EA only has one definition - that of a Jacobson Analysis type.  Hence if you stereotype a class «entity», you will, if the Tools|Options|Objects|[X] Classes honor analysis stereotypes is marked, get the familiar Circle and Line underneath image (Shape script?).

However, an entity is also the logical/conceptual version of a table (as in ERA - Entity Relationship Attribute modelling).

If you don't want the Analysis image, for some diagrams, but you do for others (because in your repository you have BOTH types of entities) you're stuck.

These kinds of settings need (as I have often remarked) to be at the Repository, Diagram and Element level.

As it happens, for our particular circumstance, the data modelling entity is never alone, it is always an auxiliary stereotype (because EA doesn't support Data Modleling elements as separate element types - such as Requirements, Issues,  Screen etc - but as stereotyped classes).  However, if the above checkbox is marked, the image override comes into play regardless...  However, with the «table» stereotype this is not the case!  :( EAUI!  ::)

Paolo
Consistency, Consistency, Consistency! TM
Inconsistently correct systems DON'T EXIST!
... Therefore, aim for consistency; in the expectation of achieving correctness....
-Semantica-
Helsinki Principle Rules!

Eve

  • EA Administrator
  • EA Guru
  • *****
  • Posts: 8110
  • Karma: +119/-20
    • View Profile
Re: Analysis vs DataModelling Entities
« Reply #1 on: October 18, 2007, 06:26:40 pm »
I'm not expecting this to make you remotely happy, but you can do what you're wanting.

On the user level, the 'Classes honor analysis stereotypes' option determines whether classes with analysis stereotypes should be drawn using the analysis symbol.

On the diagram level, the 'Use Stereotype Icons' option allows to show the analysis symbol for both classes and objects using those stereotypes on this diagram.

Paolo F Cantoni

  • EA Guru
  • *****
  • Posts: 8626
  • Karma: +259/-129
  • Inconsistently correct systems DON'T EXIST!
    • View Profile
Re: Analysis vs DataModelling Entities
« Reply #2 on: October 18, 2007, 07:22:57 pm »
Quote
I'm not expecting this to make you remotely happy, but you can do what you're wanting.
Simon, you're right, because you're wrong...  ;D

You're right, it doesn't make me remotely happy...  Because unmarking the check box removes ALL stereotype icons (except - for example the table one).  It doesn't do what I want... :(   The collateral damage is TOO great!

Is it any wonder my moniker is as it is?  Consistency is the ONLY way to make a product that works...
[size=10]It takes more work to make things inconsistent![/size] TM[/color]

Paolo
[size=10]Using EA in spite of EA, NOT because of it![/size] TM[/color]

Inconsistently correct systems DON'T EXIST!
... Therefore, aim for consistency; in the expectation of achieving correctness....
-Semantica-
Helsinki Principle Rules!