Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > comp.lang.java.programmer > #10053 > unrolled thread

Preferred Way to Show Java Dependencies?

Started byNovice <novice@example..com>
First post2011-11-18 19:21 +0000
Last post2011-11-18 11:57 -0800
Articles 2 — 2 participants

Back to article view | Back to comp.lang.java.programmer


Contents

  Preferred Way to Show Java Dependencies? Novice <novice@example..com> - 2011-11-18 19:21 +0000
    Re: Preferred Way to Show Java Dependencies? markspace <-@.> - 2011-11-18 11:57 -0800

#10053 — Preferred Way to Show Java Dependencies?

FromNovice <novice@example..com>
Date2011-11-18 19:21 +0000
SubjectPreferred Way to Show Java Dependencies?
Message-ID<Xns9FA1921D3A95Ajpnasty@94.75.214.39>
When documenting a Java project, is it customary to create dependency 
diagrams for the programs? If so, what is the best tool or technique for 
creating these diagrams?



-- 
Novice

[toc] | [next] | [standalone]


#10054

Frommarkspace <-@.>
Date2011-11-18 11:57 -0800
Message-ID<ja6dbe$2hl$1@dont-email.me>
In reply to#10053
On 11/18/2011 11:21 AM, Novice wrote:
> When documenting a Java project, is it customary to create dependency
> diagrams for the programs? If so, what is the best tool or technique for
> creating these diagrams?


Generating generic class diagrams isn't customary for software 
engineering, ime.  It's more normal to focus on important classes, 
processes, or concepts and diagram those, rather than get out the auto 
tool and just dump a bunch of diagrams into the project documentation.

As far as tool, the NetBeans UML page refers the reader to SDE for 
NetBeans and JDeveloper.  I don't have an opinion, so I'm defering to 
theirs.

http://netbeans.org/features/uml/




[toc] | [prev] | [standalone]


Back to top | Article view | comp.lang.java.programmer


csiph-web