Book a Demo

Author Topic: Reverse engineering - and beyond...  (Read 4715 times)

Alan_Semple

  • EA Novice
  • *
  • Posts: 2
  • Karma: +0/-0
  • I love YaBB 1G - SP1!
    • View Profile
Reverse engineering - and beyond...
« on: December 17, 2004, 08:45:56 am »
I use EA - infrequently - to reverse engineer Application System Table/Attribute Structures. It imports the tables as 'Classes', but I want to use them as 'instances' of the Class I've defined: "Application System Table". Is there any way to change the Class into an Object, so that when I drop the instance of the Table into a diagram of the System, I can still maintain the view of the attributes, etc?

CJ

  • EA User
  • **
  • Posts: 288
  • Karma: +0/-0
    • View Profile
Re: Reverse engineering - and beyond...
« Reply #1 on: December 17, 2004, 08:59:29 am »
G'day,

I don't think EA can create instances of database tables.

Would it suit your needs to link your reverse-engineered tables via "Generalization" link to your "Application System Table" class?
Cheers and best regards.

Alan_Semple

  • EA Novice
  • *
  • Posts: 2
  • Karma: +0/-0
  • I love YaBB 1G - SP1!
    • View Profile
Re: Reverse engineering - and beyond...
« Reply #2 on: December 17, 2004, 09:44:41 am »
Hmmm, trying that - but keeps telling me the link is not possible cos not UML compliant.

Thanks for the reply tho' - probably down to my lack of understanding of the tool - and UML.........

airimie

  • EA Novice
  • *
  • Posts: 2
  • Karma: +0/-0
  • I love YaBB 1G - SP1!
    • View Profile
Re: Reverse engineering - and beyond...
« Reply #3 on: December 17, 2004, 10:22:56 am »
When drag/drp on diagram, keep Ctrl key pressed. It will ask you how do you want to paste the element, choose "as instance of element". EA will create the object for you.
« Last Edit: December 17, 2004, 10:23:52 am by airimie »

CJ

  • EA User
  • **
  • Posts: 288
  • Karma: +0/-0
    • View Profile
Re: Reverse engineering - and beyond...
« Reply #4 on: December 17, 2004, 11:10:33 am »
Ooops, my apologies, airmie is right, table can definitely be dropped as an instance (i.e. object).  Not quite sure I like the results.

I still think Generalization is the way to go.  I just checked, and I can draw a Generalization link between a class and a (class stereotyped as) table that I reverse-engineered.  NOTE that any attributes inherited via Generalization will not be included in DDL generation.
Cheers and best regards.