The professional, friendly Java community. 21,500 members and growing!

The Java Programming Forums are a community of Java programmers from all around the World. Our members have a wide range of skills and they all have one thing in common: A passion to learn and code Java. We invite beginner Java programmers right through to Java professionals to post here and share your knowledge. Become a part of the community, help others, expand your knowledge of Java and enjoy talking with like minded people. Registration is quick and best of all free. We look forward to meeting you.

Simplifying Uml Class Diagram For System Comprehension

(I'm not sure in which section I could post this thread)

Dear all,

I'm currently doing a survey on UML class diagrams. The survey is about how to simplify a class diagram by leaving out information that is not important. The motivation behind this survey is to understand a system (after the implementation phase) by using reverse engineered class diagrams. As we know, reverse engineered class diagrams are typically a detailed representation of the underlying source code, which makes it sometimes hard for the software engineer to understand what the key elements in the software structure are. Hence, we make this survey in order for us to identify what type of class and information that should be left out from the reverse engineered class diagram. You can find the survey at the following URL :