Book a Demo

Author Topic: Keeping an overlook in class diagrams  (Read 10648 times)

lemanchot

  • EA Novice
  • *
  • Posts: 5
  • Karma: +0/-0
    • View Profile
Keeping an overlook in class diagrams
« on: December 09, 2008, 10:28:11 pm »
Hello,

in my current project I have to build a 100% consistent uml model to the code. While modelling the class diagram I observed an increasing chaos in the overlook.
For example there is a package with 5 GUIs(written in Java) in it. When I drag the class from the EA Project Browser into the modelling window the graphic shows every attribute of the class. Since there are many components like buttons or textfields, the graphical representation of such a class is very huge. For generating as much as possible code it's necassary that I have these elements already in the EA.

Is there a possibility to have a better overlook without deleting attributes? I'm searching for a way to hide these elements from the graphical view.  

Thanks for your help.

« Last Edit: December 09, 2008, 10:30:48 pm by lemanchot »

Oliver F.

  • EA User
  • **
  • Posts: 573
  • Karma: +2/-1
  • Aren´t we all in the model business ?
    • View Profile
    • Karl Storz homepage
Re: Keeping an overlook in class diagrams
« Reply #1 on: December 10, 2008, 01:04:20 am »
Take a look at the various options- you can hide/show attributes operations, tagged values, etc. per diagram as well as per element (explicitely).

You can also show/hide connectors from a diagram, all others, etc. from each connectors context menu.

HTH

Oliver

lemanchot

  • EA Novice
  • *
  • Posts: 5
  • Karma: +0/-0
    • View Profile
Re: Keeping an overlook in class diagrams
« Reply #2 on: December 11, 2008, 09:55:47 pm »
Thank you Oliver.  You helped a lot.

When deleting connectors, EA is asking if it has to be deleted or just hidden from the view. There is also an option "visibility" in the connectors  context menu.

To hide class elements from the view, the solution isn't to search in the elements context menu, but in the class context menu (feature visibility). My mistake was to search in the options of the methods and attributes.

The problem is solved.  :)
« Last Edit: December 11, 2008, 09:57:31 pm by lemanchot »