Hi,
I'm currently using Topcased 3.1 to reverse engineer a rather complex
set of Java projects (Eclipse plugins) in order to document the code
using UML. Overall, I'm really satisfied with the results I'm getting,
but some particular aspects I feel are still off.
I am not sure if the issues I'm having are due to Tocased itself or to
my misuse of the tool, or my misinterpretation of the UML standard, so
any help would be appreciated.
Say I'm trying to reverse engineer package a.b.c, which may have a
number of subpackages. I followed the steps given in the tutorial. For
the examples below, assume that a.b.c.I1 is an interface and a.b.c.C1
a class.
If a class a.b.c.d.C2 extends a.b.c.C1, the model captures this but
the diagram has an extra <<data type>> C1 to which the generalization
relationship is established. Is it possible to have the tool connect
a.b.c.d.C2 to a.b.c.C1 (across package boundaries) directly? Further,
in this case, the Java package a.b.c.d imports the package a.b.c, but
no import relationship from a.b.c.d to a.b.c. is created in the class
diagram.
If class a.b.c.d.C2 implements a.b.c.I1, *the model* does not capture
this relationship at all- I must manually add the relationship to my
model/diagram.
Say a.b.c.d.C2 has a nested class a.b.c.d.C2.C3. The model does
capture this relationship, but there is no UML connector between the
two classes to indicate the nesting.
Could anyone help me out? Any help will be most appreciated. Thanks in
advance!
Demian
_______________________________________________
Topcased-users mailing list
[email protected]
http://lists.gforge.enseeiht.fr/mailman/listinfo/topcased-users
