Path: csiph.com!x330-a1.tempe.blueboxinc.net!newsfeed.hal-mli.net!feeder3.hal-mli.net!newsfeed.hal-mli.net!feeder1.hal-mli.net!de-l.enfer-du-nord.net!feeder1.enfer-du-nord.net!eternal-september.org!feeder.eternal-september.org!.POSTED!not-for-mail From: markspace <-@.> Newsgroups: comp.lang.java.programmer Subject: Re: Preferred Way to Show Java Dependencies? Date: Fri, 18 Nov 2011 11:57:31 -0800 Organization: A noiseless patient Spider Lines: 21 Message-ID: References: Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Injection-Date: Fri, 18 Nov 2011 19:57:34 +0000 (UTC) Injection-Info: mx04.eternal-september.org; posting-host="XjIWM99mD7Ijfdu600oVPA"; logging-data="2613"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1+dYlD004uCMThQA8gpX9JXlXY2zD5E05c=" User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:8.0) Gecko/20111105 Thunderbird/8.0 In-Reply-To: Cancel-Lock: sha1:dZuACDdrGZ+YPJMjs8k9e12QzZ4= Xref: x330-a1.tempe.blueboxinc.net comp.lang.java.programmer:10054 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/