Book a Demo

Author Topic: Reverse engineering  (Read 2726 times)

Yoda

  • EA Novice
  • *
  • Posts: 1
  • Karma: +0/-0
  • I love YaBB 1G - SP1!
    • View Profile
Reverse engineering
« on: May 22, 2006, 09:57:41 am »
Hi,


testing the software I see a leak in the model generation. For example:

class a {
};

class b {
public:
  void test(a par);
};


The class b has a parameter of type a…but this dependency is not shown in the class diagram generated from the software.



I committed a mistake using EA or is a feature not supported?


thank you

thomaskilian

  • Guest
Re: Reverse engineering
« Reply #1 on: May 22, 2006, 11:23:02 am »
I'm not sure about that, but I think that this has been discussed here. So, AFAIK EA can't recognize these dependencies and aka does not create it in the model. I might be wrong, though.

Eve

  • EA Administrator
  • EA Guru
  • *****
  • Posts: 8110
  • Karma: +119/-20
    • View Profile
Re: Reverse engineering
« Reply #2 on: May 22, 2006, 03:33:00 pm »
Hi Yoda,

I'll confirm what Thomas is saying.  EA currently doesn't create dependency connectors in reverse engineering.

However, I'd also like to say that EA can and does recognise the relationship.  I believe that EA would have set the classifier for the parameter.  The dependencies that EA can't recognise is when a class is used inside the method bodies of a class.

The only thing that is missing is the visual indication of the dependency.

james.kinneavy

  • EA User
  • **
  • Posts: 26
  • Karma: +0/-0
    • View Profile
Re: Reverse engineering
« Reply #3 on: May 24, 2006, 09:57:10 am »
Is apply the visual indicator of a dependency in Sparx' roadmap?  I've had a number of colleagues ask me about this and were disappointed to hear that EA doesn't support it.  I know I'd like it