Book a Demo

Author Topic: Why UML diagram was generated for every directory?  (Read 3602 times)

mike519

  • EA Novice
  • *
  • Posts: 3
  • Karma: +0/-0
    • View Profile
Why UML diagram was generated for every directory?
« on: January 02, 2012, 07:32:56 pm »
Using reverse engineering from java source code, I get generated UML diagram for every package (directory). However I need a total UML diagram. For sepaeated diagrams, some inherit relation of classes were lost.

Can EA provide such capability? :-[

Geert Bellekens

  • EA Guru
  • *****
  • Posts: 13523
  • Karma: +574/-33
  • Make EA work for YOU!
    • View Profile
    • Enterprise Architect Consultant and Value Added Reseller
Re: Why UML diagram was generated for every direct
« Reply #1 on: January 02, 2012, 11:20:16 pm »
Hi,

It's not because the relation is not show on a diagram that is has been lost.

In general the only usage of a class diagram that contains ALL of your classes is to use as wallpaper.

Geert

mike519

  • EA Novice
  • *
  • Posts: 3
  • Karma: +0/-0
    • View Profile
Re: Why UML diagram was generated for every direct
« Reply #2 on: January 03, 2012, 09:43:50 pm »
I just expect a total diagram for a project which discribes the total relations of all classes. Even if the diagram has to be separated to several diagrams (e.g., several tiers, like data flow diagrams) because it is too big, the relations of classes should not be lost.

Plotting classes diagram in terms of package has no much meaning for me. For example, Date in java.util has no relations with other classes in that package. While Date, Time in java.sql are inherited from it. I needs classes diagram across package.

Could you please give me some suggestions?

KP

  • EA Administrator
  • EA Expert
  • *****
  • Posts: 2919
  • Karma: +55/-3
    • View Profile
Re: Why UML diagram was generated for every direct
« Reply #3 on: January 04, 2012, 08:58:40 am »
Quote
I just expect a total diagram for a project which discribes the total relations of all classes. Even if the diagram has to be separated to several diagrams (e.g., several tiers, like data flow diagrams) because it is too big, the relations of classes should not be lost.
They aren't: relationships exist in the model even if neither related element is on a diagram.

Quote
Plotting classes diagram in terms of package has no much meaning for me. For example, Date in java.util has no relations with other classes in that package. While Date, Time in java.sql are inherited from it. I needs classes diagram across package.

Could you please give me some suggestions?
Drop a class from the Project Browser onto an empty diagram, right click the class and select Add > Related Elements.

And for that big wallpaper diagram that Geert mentioned, select all the classes in the Project Browser and drop them all onto an empty class diagram, then View > Diagram Layout.
« Last Edit: January 04, 2012, 09:01:06 am by KP »
The Sparx Team
[email protected]

mike519

  • EA Novice
  • *
  • Posts: 3
  • Karma: +0/-0
    • View Profile
Re: Why UML diagram was generated for every direct
« Reply #4 on: January 28, 2012, 04:44:41 pm »
Thank you! I tried your method. "Add > Related Elements" limits to max 5 layers for imported components. Although I can add related elements for arbitrary class to avoid the limitation, I hope EA can provide unlimited option.

For Geert's method, I don't know how to select all classes across different package.